Users logging on with local profile instead of roaming profile

I had a situation where users who should be logging on with roaming profiles loaded from a DFS share, were getting logged on with a local profile.
After browsing the logs, we could see that the profile wouldn’t get loaded because of a slow network link.
roam1

Which could be the case since users switch offices all the time.
The default policy is to check wether a slow link exists (500kb by default) and if so, windows will log you on with a local or cached profile.

To disable the slow link detection, you need to edit/create a gpo , Computer settings\Policies\Administrative Templates\System\Group Policy
roam2 
Now you need to enable the policy and set it to “0” to disable detection,or define a speed you like.
roam3

Now when this is done, you also need to modify another policy under the user profile section (Computer settings\Policies\Administrative Templates\System\User Profiles)
You only need to enable the 2 marked in the screenshot, the other ones I enabled are not for this issue.

roam4

V-79-57344-34108 – An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.

Last week I had another interesting issue with backup exec.
As you can see from the title the job ended with a :

V-79-57344-34108 – An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.

and another :

V-79-57344-65033 – Directory not found. Cannot backup directory D:\HOMEDIRS\BLA\Desktop and its subdirectories.

Needless to say that the directory ofcourse was available and backup ran fine like forever until then…

But first a little scenario of the problem:

-ESX 4 Host
-Windows 2008 R2 SP1 with shares on drive “D:”
-Backup of C: has no problem what so ever
-VSS errors filling up event log during backup of D:

So to isolate the problem I had checked every goddamn Symantec KB, every MS KB… But all to no avail.
When checking out the VCenter , nothing unusual!

But then when I went clueless, and just for the fun of it connected directly to the ESX Host instead of Vcenter, I saw a Snapshot task of the said VM running and hung at 95% for like 1 week already!!(from the backup exec VMWare backup)

So I cancelled this snapshot, but still not any luck with my D: Disk.

Then my collegue spotted something I didn’t see, for some reason we had 2 VSS providers:
-Backup Exec VSS Provider
-BEVSS Provider

As it turns out, when making backups of whole VMs, Backup exec generates an extra VSS Provider (BEVSS Provider) in the services console of windows, and when backups are complete removes it again. But because the snapshot hung, the service didn’t get removed and somehow backupexec messed up!

Now to solve this:

There is a script that get’s called after a VM Backup Job ( Post-Thawte-script.bat)
located in “c:\windows”

Run this script manually and reboot, this should fix the issue and remove the extra VSS Provider!!

more info here: http://www.symantec.com/connect/forums/backupexec-2010-bevss-provider-installs-inself