BatchFile (13th May 2009)
One of our members of staff has a problem with her roaming profile, in that it doesn'twork
(Server 2003 network and Vista Business laptop)
I've taken ownership of and moved the folder off the profile share on the server and moved c:\users\%username% on the c: drive to no avail. the exact sequence of events when the user logs in is as follows:
User enters username and password
Folder named %username%.v2 is created on the roaming profile share on the server
Folder named TEMP is created in c:\users on the local disk
The "your profile was not loaded correctly and changes will be lost when you log off" message is displayed
I tried changing the user profile name in "Active Directory users and computers", now the folder created on the server has the new name but apart from that nothing's changed.
Any ideas anyone?![]()
Last edited by BatchFile; 13th May 2009 at 02:07 PM. Reason: forgot to put Server and WS OS in original post
Were running the same setup fine.
Roaming profiles for XP work ok? (if not check permissions for creator owner on creation of subfolders)
Check that the profile is coming up as Roaming in the User Profiles (Advanced Settings on System) with the correct username.
Other than that no ideas yet.
BatchFile (13th May 2009)
I had this problem, when vista came out. I ended up re-installing.
But i had it again recently and found that you can no longer just delete their local profile in Vista, you also need to remove the users profile from the registry...
Computer\HKey_local_machine\Software\Microsoft\Win dows NT\CurrentVersion\ProfileList
You have to match your SID, but if you click through them you can easily see who`s is whos
There is now an M$ article somewhere if i can find it
Good luck
Last edited by burgemaster; 29th June 2009 at 11:24 AM.
BatchFile (30th June 2009)
burgemaster is correct, that is the only way to resolve these niggly profile issues on vista, a bit of a headache sometimes but it works
I solved this problem this morning!
It's something to do with the TCPIP stack.
Run the command prompt (as an administrator) and enter
netsh int tcp set global autotuninglevel=disabled
and then reboot the computer.
I've also read about the nVidia display driver service affecting it as well, so you could also try disabling that.
There are currently 1 users browsing this thread. (0 members and 1 guests)