Mandatory roaming profiles work fine with XP clients. We now have some new Windows 7 machines that need mandatory profiles for their desktops. I have copied a Win 7 profile to the server. Win XP profile at \\[servername]\profiles\mandatory and Win 7 at \\[servername]\profiles\mandatory.v2 The user profiles are set to \profiles\mandatory and what SHOULD happen is that Win 7 clients should automatically pick up the .v2 version. When I log on to a Win 7 machine as a non-admin user, the unexpected happens. The client creates a directory .v2 WITHIN the directory for XP i.e: the path is profiles\mandatory\.v2, ignoring the profile set up for it. The user logging in becomes the owner of that directory and if other users try to log in from XP machines, their profile fails to load. Maybe I am too dull to work this out or is there something obvious I am doing wrong?

Hi, When you say users profiles are "set to \profiles\mandatory" are you talking about the ad user attribute or group policy? Are there any group polices in effect on the computers in relation to profile location? Windows 7 and XP don't share the same profile you should have two profiles of each user ie .. XP = \profiles\mandatory\user 7 = \profiles\mandatory\user.v2 Kind Regards, John

Thanks for your reply. It's an ad user attribute. Everyone (except network admin) should get the same profile for their desktop. There are no GPs relating to profile location. Works Ok for the XP machines. Locations set as you show above.

Do not direct the profile to \\[servername]\profiles\mandatory.v2. Please direct to \\[servername]\profiles\mandatory and the *.v2 folder will be automatically created.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How do you have copy your Win 7 profile on the server ? because for me the "copy to" button is grey out ! Thanks Mat