Windows roaming profiles not updating
DAT on the profile share and gets back the return code ERROR_SHARING_VIOLATION (which is equivalent to “The process cannot access the file because it is being used by another process.”).
Interestingly, that one attempt to open the file takes approximately 35 seconds! Here is my working theory: it seems, somehow handles to the user profile files and folders on the file server are left open when the machine is rebooted.
Unfortunately the App Data folder still points there.
Redirection of the App Data folder is done via group policy, not by specifying a roaming profile.
How can I tell to the clients that they need to keep the profile on the local computer?
I hope I've explained the problem in a clearly way. Matteo EDIT I didn't mention that there was a policy which redirected the App Data onto a shared folders, but now it's disabled (checked through gpresult on the client).
This is a very complex subject, for which we can only offer some beginning pointers at this time.
After every user login onto workstation a message appears, saying that "the workstation can not synchronize with roaming profile and will use local copy of it instead" - no other messages in any log.
So I took a boot trace in Sysinternals Process Monitor – once I figured out how you need to tweak it to get that to work.
The result was interesting: As you can see, the User Profile Service tries to open NTUSER.
You don't mention removing or reverting this group policy setting, so I'm guessing that's the problem.
Use gpresult to check whether there is still a policy in place.
Search for windows roaming profiles not updating:
Helge applied his extensive knowledge in IT infrastructure projects and architected the user profile management product whose successor is now available as Citrix Profile Management.