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.

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
Now you need to enable the policy and set it to “0” to disable detection,or define a speed you like.

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.


Bootmgr is missing

When you come across the error “Bootmgr is missing” in windows 7/Server 2008.
the answer is:
Load a windows cd(7/2008) for the apropriate OS and boot it, then choose “reapair my computer” , then choose command promt.(in case of HW raid, load the proper drivers first)
Type: cd recovery
Then type: startrep.exe
If you’re lucky this will solve your problems automaticaly.

In my case it didn’t so i had to do it manually, first of all when in the commandpromt enter:
bootrec /fixmbr
if this doesn’t resolve it, make sure the right partition/disk is set as “Active”.
it has to be the small partition that goes before your main drive(C:)

go back to the command prompt and enter diskpart
now enter list volume
look for the said volume (it’s about 100mb)
select volume
type: Active

then make sure none of the others are marked active, select them by using
select volume “.
Then type: Inactive

now you shoud be able to boot without problems.

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:

WSUS broken after SP2 update on SBS 2008

The title says it all.
As it turns out i’m not the only one and google is scattered with people having the same issue.

I had a client who had upgraded his WSUS sp1 on a SBS 2008 box to SP2, without reading the preresuisites (found here:

So it messed up WSUS beyond repair.

I first tried the basics, uninstalling WSUS sp2 , delete all the files in the WSUS directory etc and then reinstall the original WSUS from the 2nd DVD of SBS 2008.

The install completed successfully however WSUS was still broken, and would throw erros like:

The SimpleAuth Webservice is not working 
The ClientWebservice is not working 

WSUS administration console was unable to connect to the server using the remote API

System.IO.IOException — De handshake is mislukt als gevolg van een onverwachte pakketgrootte.
Stack Trace:
bij System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
bij System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)

Last one is in dutch because I’m too lazy to translate and the client installed the SBS in dutch O_O

As I said I tried uninstall and reinstall, but didn’t do the trick. Then I noticed that the WSUS administration console site would not get removed from IIS sites, even though WSUS was uninstalled. So:

1 Uninstall WSUS , go to control panel –> Programs and Features –> Windows updates services –> remove –> check all the boxes to remove all of the files.

2 Delete the contents of the WSUS folder , usually located under c: , don’t delete the folder itself.

3 Delete the WSUS administration Site under IIS –> Administrative Tools –> IIS Manager –> In the left pane there should be a site called ‘WSUS ADMINISTRATION’ –> right click –> Delete

4 Install the report viewer as specified in the requirements mentioned earlier (if not done so already)

5 Download the WSUS SP2 Installer from the link specified earlier.

6 Right click installer and run as admin.

7 Now WSUS should work as before and you’ll be running SP2 , but unfortunately you’ll need to configure WSUS from scratch.