Discussion Locked

Roaming Profiles Between XP and NT?

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

Working on a project at my company where we are trying to migrate to an XP client environment from NT4 cllients. We have Win2003 servers and Active Directory running on the back-end.

The concern we have now is tat during our migration to XP, there will be a period of time (3 months or so) where users will be forced to switch from one client to another - NT to XP and vice versa. In our testing, we're seeing NT classic settings coming into XP and menu picks for applications in NT and vice versa.

Has anyone had any experience with this and can offer any tips, tricks or things to avoid in doing this?

6 replies

by p.j.hutchison

We have had this problem before and the solution is to turn OFF roaming profiles until the old clients have been removed. NT /XP profiles are NOT compatible and you end up with corrupted or useless profiles.

by p.j.hutchison

There is the ADSI client to allow NT4 work in Active Directory. Roaming profiles can be set on the Profile tab of each user in AD Users and Computers - this doesn`t solve problem with mixing profiles with NT4 and XP - the registry sets are different!

by modster

If the solution is to disable roaming profiles, what alternatives have you or your company developed? Like folder redirection, alternate profile locations, etc...

by koke

I thought there was a downlaod from MS to allow NT workstations to utilize Active Directories, which allows the roaming profiles...

Koke

This discussion is closed to new replies.