Question Locked

Workstation Roaming Profiles not updated

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have recently upgraded the domain server to Windows Server 2008 from SBS 2003 and now I am having more and more problems with the roaming profiles for Windows XP workstation users. It appears that the profiles are being correctly updated on the server, but not on the workstation. The result is that icons on the desktop which are deleted or updated are overwritten by those stored on the workstation, but new items are stored to the server correctly.

I have looked at the permissions on the workstation and the user has full control of the folders in use.

It still seems to be a permission problem on the workstation, by I cannot see where.

Any suggestions or pointers would be appreciated.

Andrew

8 replies

by billmlod

You may want to try this on 1 workstation first, remove it from the domain & then add it back, that should sync with the new server. Just a thought.

Good luck

by andrew.myers

but it did not seem to help. Might give it another go though.

Andrew

by seanferd

Check event logs on XP stations, and the server as well.

One problem with applying policies is due to the user profile not unloading (for whatever reason). If you see this in the logs, download & install UPHClean from MS. Runs as a service and makes sure the user profile unloads properly at logoff/shutdown.

by andrew.myers

along the lines of not unloading profiles due to a process not completing. I have downloaded the UPHClean programme, but have not used it yet. I will give this a try and let you know.

Andrew

by andrew.myers

I have been through everything I can think of including the suggestions above with no result. I believe it to be a problem between the Windows Server 2008R2 64bit and the XP workstations. The profiles update on the server as they are changed, but the workstations are not updated in real time, or when the user logs off. UPHClean makes no difference. The only other possibility I can think of is some group policy that I am not aware of.

Andrew

This discussion is closed to new replies.