Profile.V2 - Cannot access

Question

I'm sure this is a simple one:
I'm using Folder Redirection and Roaming Profiles.
In Active Directory I have set the users profile path as
\\servername\users$\students\%username%\profile Although the user's base folder exists it contains no subfolders whatsoever. When the user logs on for the first time folders such as AppData, Documents, Music, Pictures and Videos are created and so
is a Profile.V2 folder. However I (as the administrator) cannot access the contents of the Profile.V2 folder.
In Group Policy I have enabled the setting...
Computer Confiiguration\Policies\Administrative Templates\System/User Profiles\Add Administrators security group to roaming user profiles
...but I still cannot access this direcotry without taking ownership.
Do I need to create the Profile.V2 folder myself? I have Full permissions on the user's base folder and I can access all the other folders (AppData, Documents etc...) without problems.
Am I missing something here?
Matt Courtman, Network Manager, Cromwell Community College, UK

Answer 1

You cannot access other users’ profiles because of permission problems. Therefore you cannot use any of other users’ profiles.
This statement just states the original issue..and is by no means an answer or even an attempt at an answer.
We are experiencing the same issue.
Please forgive me if I'm repeating what has already been stated.
The condition occurs when the Profile.v2 folder on the file server is first propagated by the Windows 7 machine. eg. as the user logs off the profile.v2 folder is written to by as the profile is written back to the file server, the redirected folders
policy dictates what is written.. This works fine. The issue is that the folders and files which are generated by this process are owned by the user who is logged on to the Windows 7 OS. This user has ownership and full control of the folders and file. Administrators
or users defined in the root folder can not access the Folders and Files.
Taking ownership of the file structure and assigning the correct permissions to the structure, then reassigning the user ownership again resolves the issue. BUT this is a very inconvenient and labour intensive routine to have to undertake for each user post
their first logon.
Without performing the above action the users profile is not backed up or replicated at a file level to the DR site.
What I'm after is a supported Microsoft routine to rectify this issue. Ideally via group policy. To have to do this via a script is an ardouis task and presents the issue of how can we get the HelpDesk to perform this action. They are not domain admins nor
can they take control of the data structure in question.