Roaming Profile not updating

[Jordan]

I have been setting up and configuring Roaming Profiles for the past couple
of months for all my users. All has been going well so far. Now I am
enabling my own and for some reason, it won't replicate to the server.

I first thougtht it might be a space issue because my Outlook.ost is huge,
but I removed it from my local settings (which don't replicate anyway) and
it still did not even create a single file on the server where my profile
should be. This share is the same share every other profile is using and
security is the same. Since I am a Domain Admin security should not be an
issue.

I then though I would see if I could at least download a profile so:

1. I copied my profile manually to the share
2. Rebooted the computer
3. Logged in with another Admin account
4. Deleted my profile on the computer.
5. Logged in as myself.

When I did this I got my profile from the server. I then tried something
simple like adding another file to my desktop and restarting, but that file
did not replicate to the server. Just to be sure I could still download an
updated profile on the server, from another computer I added a file to the
Desktop folder of my profile on the server share. When I logged in again,
that new file was on my computer's desktop, but still the file I added on
the computer client did not replicate up to the server.

There appears to be gigs and gigs of disk space available on the server and
it seems every other profile is updating for all the other users. I am just
not sure what could be causing this to be a one way replication.

 

[JakeSpleen]

Since you can download your profile it is either:

You do not have update permissions to your server share, even though you're
admin it might be worth removign and re-applying the permissions.

We had to log a call with MS recently as this was effecting a lot of users
on my contract that I support. It was manifesting itself with desktop icons
and internet favourites. When users deleted them they would re-appear after a
reboot. It was ok if they simply logged off and then back on.

See http://support.microsoft.com/kb/819536/en-us

And

http://support.microsoft.com/kb/836051/

Once we installed the hotfix from http://support.microsoft.com/kb/819536/en-us

it all worked