asked on

Profiles .V2

We use Windows Server 2003 and active Directory in our school domain. For this school year I created a new OU for the students called Students 2011-2012. I then moved all the old student profiles from the previous OU to the new one. I then added new students and deleted the old. I created folders with the school's default profile for each new student and set their profile path the same as all the other students (except using their username). We upgraded all of our clients to Windows 7 Pro 32 bit. After a couple of days of school I looked at the directory where all the profiles are stored and I saw that every student who has logged in so far now has two folders. One is the shared folder I created and the other is a non-shared folder with the same username but with the .V2 file extension. The second one does not have any permissions set and I have to take ownership of it in order to access the contents. Please explain what happened and what I need to do to repair this problem. It has also happened with staff members who have not been moved to a new OU.

Thank you!

Robert

Jim-R

Preparing for migration of roaming profiles with computers that run Windows Vista and Windows 7

In Windows Vista, a change was made to profiles that made them incompatible with previous versions of Windows. To differentiate the new profiles, a .V2 extension was added to all roaming profiles for users on computers running Windows Vista and later.

The location of a roaming profile for the same user RoamUserX for a computer that runs Windows Vista or Windows 7 is:

\\host.name.fqdn\ProfileShare\RoamUserX.V2

This version can co-exist with a roaming profile for an earlier version of Windows.

Only ADMT v3.2 distinguishes the two different profile folder names. Earlier versions of ADMT only look for the folder called <profilename> and do not try to locate a V2 profile if it exists. Therefore, earlier versions of ADMT do not migrate roaming profiles for computers running Windows Vista and Windows 7.

In order to migrate a roaming profile folder using ADMT v3.2, the default access control list of the folder needs to be modified. By default, when a user logs on and the roaming profile folder and contents are created, the <profilename> or <profilename>.V2 folders are given the following ACLs:

* SYSTEM – Full Control

* user_name - Full Control

* Owner = user_name

Therefore, only the owner of the profile, and the local system on which the share resides, are able to access the <profilename> or <profilename>.V2 folder. When the folder is assigned those default permissions, ADMT cannot access the folder for security translation.

Robert Ehinger

ASKER

OK, so I understand where these folders came from so I guess I need them. Should I, ad administrator, take ownership of these profiles and move the contents from the old folder to the new?

ASKER CERTIFIED SOLUTION

Jim-R

membership

This solution is only available to members.

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

Start Free Trial

Robert Ehinger

ASKER

Is this the same in Server 2003?

SOLUTION

Jim-R

membership