Roaming Profiles basics:
You can use roaming profiles (desktop icons, settings, my documents folder, start menu shortcuts, etc will be preserved no matter the client computer logged into. Create a network shared folder (must be available to network from the computer you create it on) with default share permissions (example: call it user$ on server1). In NTFS permissions (security tab), use the advanced button in NTFS permission and highlight everyone. Click the view/edit button and change the permissions to "List folder/read data" and "create folders/append data" only. In active directory users and computers, go to the profile tab for your users and set the profile path to \\server1\user$\%username% for each user you wish to use roaming profiles. When a user logs on, it will use the roaming profile. A folder will be created for each roaming user in \\server1\user$ by the system and will give each user exclusive rights only to their profile folder.
You also can redirect local paths for them as well using the same technique.
Notice that I used a dollar sign in the share. That makes it a hidden share and it won't be visible in my network places/network neighborhood but it is there. (do start>run>\\server1\share$ and you will see it).
Profiles are stored in the share and then cached to the client when they log in. When the client logs off, the profile is supposed to be synchronized back to the share.
Since you are storing all the profiles in one location, you may wish to institute quotas on the drive they are stored to keep users from filling it up with meaningless junk. Quotas must be in place on the drive before any users write to it or you will have to manually add users to the quota list that already have files written to the drive.
