asked on

Roaming profile question

We run Windows Server 2003 and us roaming profiles. We just had to upgrade our Terminal Server and that is running Server 2008. In testing, I see that when a user logs onto the new remote server, a new profile is created, the username with a v2 on the end. I am trying to get my mind around how this is all going to work when they log back onto their work PC, will XP know to go to the new profile? It looks like I'll have to copy the old profile to the new one for it to be the same?

Any help with this whole concept would be greatly appreciated. And, please, no lectures about not using roaming profiles, I know redirected folders would elimnate this, but for now we can't go there, so please, just answers pertaining tomy current situation.

Thanks!

Hypercat (Deb)

The V2 profile folder is a Vista/Windows 7/Server 2008 compatible profile. Profiles for these OS's are quite different from profiles for the Windows 2003/XP generation of systems, thus the need to create a new profile structure. They are not compatible with each other. When the user logs on to an XP machine, it will use the XP-compatible profile. So, any changes a user makes to a V2 profiles while logged on to your terminal server will not be reflected when they log back on to their XP workstation. I recommend using different roaming profiles for terminal server logins anyway, as the user may not have all of the same applications available on the TS.

tmckinney01

ASKER

Oh boy, this looks like its going to be a mess. Should I just tell people to make sure to save all their work on accessable network drives? I see an issue coming up where something gets changed on either the users PC or the terminal server but not on the other. This will create a tom of problem calls.

ASKER CERTIFIED SOLUTION

Hypercat (Deb)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tmckinney01

ASKER

Thanks, your answer was perfect.