SBS Connect Computer Wizard issue.

I have been recently installing a brand new SBS domain. It is a 20 workstation environment. The workstations were on a hodgepodge of a network that included 3 different workgroups and an old defunct domain. Some clients were on each of the different segments.

To make a long story short, I noticed several of the machines were returning an error that stated the profile I was attempting to migrate was a private profile and I needed to visit the permissions on the profile (right click on the systemroot/documents and settings/username folder) and remove the checkmark from the "Make Folder Private" checkbox. Of course, there was no checkmark there. Par for the course. So I put a checkmark in the box hit "ok" and let it set the permissions. Once the folder was made private I then proceeded to remove the checkmark and hit "ok" again, removing the private settings from the folders.

At this point I ran the sbsserver/connectclient wizard again and it worked like clockwork...

This worked for the majority of clients. However, a handfull of clients were holdouts from a long deceased domain. These had the full permissions page rather than the simple "make folder private checkbox." I gave the administrater full control. Ran the wizard... Nope, didn't work. I then took ownership of the profile, and ran the wizard... Huh uh, that didn't work either. Flummoxed, I began to look around... Here is how I finally solved it.

1.) Go to systemroot/program files/Microsoft Windows Small Business Server/Clients/SBSNetSetup.log

2.) Once open, hit ctrl+f and find the line that says: CProfileList::FindPrivateDir() - returning true

3.) Next to that statement will be a filename. This file is the culprit. Delete this file. There may be more than one line here, so look at the following lines. Delete all of them.

4.) Rerun the wizard and you should be good to go!

Good Luck. As always, the information provided here is for informtional purposes only. I assume no responsibility for anything resulting from it. Use it at your own risk...