Roaming profile when we don't do Roaming Profiles?!?
Posted on 2010-11-30
I have ONE SPECIFIC user (for this case and for user distinction, we'll call him "Curly") unable to reliably log in and create a local profile for himself. He has done this on two completely different systems (a desktop system I use for testing purposes, and the laptop I've deployed for him).
His first-ever login on his credentials was successful, but subsequent login attempts turn into a "Roaming profile" when we don't use them. This was performed on a "Guest" system I maintain for employee training.
I have logged in under my Domain Admin creds, my standard user creds, and I've even gone so far as to have another standard user log ("Shemp") in, all of which have been successful.
Some items of note:
1. Curly's account was copied from the individual he replaced ("Joe"), so the credentials are identical, other than Joe's account being disabled.
2. I've verified the accounts (Both System and User) are in the proper OUs for our AD.
3. The system Curly's using was Joe's, but the system has been re-imaged completely with WinXP SP3 with full updates applied.
4. I have removed the system from the domain (2x, now) and rejoined after a restart, but the issue remains persistent...for ths ONE user.
5. I have run the UPHClean Tool, but the issue remains persistent.
6. Joe had no issues with this system nor connecting to the domain while he was here.
7. I have verified connectivity via the onboard NIC, and have disengaged the Wireless NIC for good measure.
After Curly attempts to login, he sees the following dialogue:
"Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator."
Any help or suggestions would be appreciated.