SAV Corp V.10 and user profiles.

[jrjuiliano]

Anyone else have a problem with SAV 10 and roaming profiles?

Installed version 10 over 9.x and these are the problems I've had so far:

Roaming user profiles are not being updated to the server because a registry key involving RTVScan (I don't have the full key here, as I was trying to find other issues) hangs and times out.

userenv errors (event id 1000): Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.
DETAIL - Access is denied. , Build number ((2195)). This is related to the registry key hanging.

Now I'm having issues with w32time but that might be unrelated.

I had one case where I had a bunch of network drives that were created, which pointed to a valid share, but were not mapped by me or by any script. Couldn't delete them using the GUI or "net use" commands because they were not technically mapped network drives.

So far downgrading to SAV 9.x client has resolved all these issues, but wanted to see if anyone else had these or similar issues, and if there are any fixes available.

 

[jrjuiliano]

Update.

Downgrading to SAV 9 worked. I'm not installing 10 until something is updated or I figure out what the deal is.

 

[PoliMalaka]

There are a tremendous number of problems with v10.
I'd say hold off installing enterprise wide until your test machines are running more stable.

 

[tony72000]

Try downloading and running this service from Microsoft:

http://www.microsoft.com/downloads/...6d-8912-4e18-b570-42470e2f3582&displaylang=en

It is a registry hive clean-up program that will force RTVScan to let go sections of registry it is using, so the profile can be updated.

This runs as a small service in the background.

 

[jrjuiliano]

tony7200,

I did download and install that on one of my machines. It DID show that it unloaded the RTVScan entry in the registry but it did not fix the issue of creating ghost network drives and even profile sync-ing.

I think my best bet is to wait until an update is available through Symantec, or try it again and contact Symantec when the issue comes up.

 

[bettyb]

Have you tried loading the registry hive cleanup on a Windows2003 server? Why I am asking: I've been running Sav10 for about a month. all of a sudden I am having a terrible time on my primary server with rtvscan service crashing - - and I am wondering if the registry issue is related. I am a little hesitant to try it on a server. Works wonderfully on W2K and WinXP clients.

 

[jrjuiliano]

bettyb, I don't use Win2k3 server yet, but maybe someone else can chime in if they use it.

J.R.

 

[Ih8tComputers]

Same problems here, slow shutdowns do to the registry hanging, phantom drives on a few machines, and general slow performance on the workstations!

I'm not experienceing this on any XP or 2003 boxs only the W2K machines, which unfortunatley are the bulk of our PCs.

How could Symantec let a product out the door with these many issues!!

Anyone be able to drag a fix out of Symantec yet?

 

[tony72000]

Windows 2000:
The system attempts to unload the profile 60 times at 1 second intervals. This retry logic rarely helps so in most cases after 60 seconds of the user waiting at the Saving Settings message box the system gives up and roaming profiles are not reconciled. The number of retries can be changed to allow the user to log off faster (this can be done using the policy under Computer Configuration, Administrative Template, System, User Profiles, Maximum retries to unload and update user profile)

Windows XP and 2003:
The profile is reconciled using a copy of the contents of the registry. The user is not made to wait as in Windows 2000. The problem left is that the computer cannot recover the memory the profile uses until it can be unloaded.

 

[ScDavis]

JrJuliano,

No offense - I've been a field hands-on Win admin for 12 years. Unless you're admining either a Citrix/TermServ farm OR Homogenous (identical, IDENTICAL) hardware/software environment -- roaming profiles are just asking for trouble.

I can't comment towards your original post -- but I wanted to suggest that if your environment allows, you lose the roaming profiles ..

Best,
-- Scott.

 

[tony72000]

I Quite agree…

Roaming profiles are so much trouble, especially on small networks with only one or two servers.

I gave up using roaming profiles years ago.

 

[jrjuiliano]

Right now roaming profiles work pretty well for me with under 20 clients. They don't tend to "roam" around very much unless they are taking the front desk for phone calls, so at this point it's just a matter of having a good backup for them every night.

But since I'm here to learn something, what do you guys do for small networks and making sure that users have a good backup of their profiles (note we have a "public" folder for all users, but for some reason they don't use it as much as I'd like them to; I can only get them so far before having to star t over again with the training! ;-) )? It's my responsibility to make sure these files are backed up, and roaming profiles saved me from having to go to each machine and do a backup.

Is this what folder redirection would be used for?

 

[tony72000]

I tend to use folder re-direction in group policy.

Re-direct the 'My Documents' folder to a share on the file server. They are non-the-wiser and I can back this up every night.

As most of my users are lap-tops with docking stations, the 'My Documents' folder is made available off-line and is synchronised when the user logs-on and off.