Roaming Profile.v2 folder copying

We have a Windows Server 2008 R2 AD Domain Infrastructure with Roaming profiles through Group Policy. The permissions for the user folders where the profile.v2 folder resides is not owned by the users for replication/backup reasons. However whenever we run a Robocopy on the users directory share we cannot copy the profile.v2 folders.
We'll be moving all of our shares including the roaming profiles over to a SAN device later this year; so I'll need to know how to resolve this issue. Not sure if I need to take ownership of this folder as I do not want to break permissions on the user's end.

Does anyone know of a way to effectively copy/backup the profile.v2 folder?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you tried adding the account the backup runs under to the "Backup Operators" user group? That should give it the required permissions.
nti1999Author Commented:

Yes the account we're using for the backups/robocopy is a member of the Backup Operators group.
Does the system account have permissions on the user folders? If so, the easiest solution's probably to run a script using the SYSTEM account that adds permissions for the backup user to each folder. There's a GPO setting that will add the adminstrator to the ACLs for any new roaming profiles, but it won't help with the existing ones.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

nti1999Author Commented:
A workaround that I've been able to come up with is to have the owner of the profile.v2 folder in each user profile give full control to the Domain Admins group which the backup account is also a member of. This has effectively resolved the issue; but there's got to be a more central way of achieving this solution.
nti1999Author Commented:

I'll attempt adding the SYSTEM account to the ACL in the GPO: but I don't have much experience with a script that'll make the change for existing accounts. Do you know of any tutorials that I could use to accomplish/try this?
Hi nti1999,

I had one open earlier, I'm not at my normal PC right now but when I'm back there I'll find the link for you - off the top of my head I'd create a schedule task, running under the SYSTEM account, that does
icacls [your roaming profile root folder]  /grant [your backup user/group]:RX /T

Open in new window


icacls E:\profiles\ /grant backupuser:RX /T

Open in new window

The /T should make it recurse through subfolders, and grant the backup user read and traverse access.
The alternative, if the SYSTEM user doesn't have the right permissions to make the changes, would be to add a startup script for all your users that runs the ICACLS command under their account when they log on and adds the permissions we need.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Once you're done, it's probably also worth applying the Group Policy setting "Add the Administrator security group to the roaming user profile share" as described here: - this will mean new users get suitable permissions applied when their profiles are created.
nti1999Author Commented:
Thanks for the info and assist. I'll try these options on Monday morning and let you know if it resolves the issue. I did run the poershell ICACLS script on the users directory including the profile folders. It ran and processed for the root share (users) and 10 sub folders in that directory. It didn't apply to all sub folders; unless it just lists 10 at a time.
nti1999Author Commented:

Is the syntax the same for the log on script as it is in the powershell script? If it is...then I can just add the line to their existing logon script batch files. They each have a mapping to their user directories which includes their profile.v2 folder; so I am guessing the script will look something like this:
net use P: /delete /Y
net use T: /delete /Y
net use N: /delete /Y
net use K: /delete /Y
net use U: /delete /Y
net use P: \\fileserver\Public /persistent:yes
net use T: \\fileserver\IT /persistent:yes
net use N: \\fileserver\besr_images
net use U: \\fileserver\users$\%username%
icacls U:\profile.V2\ /grant backupuser:RX /T

Hi mti1999,

That looks good to me, although obviously once it's run once for all your users I'd take it back out as it'll slow down the logon a bit.

Let me know how you get on.


nti1999Author Commented:

Going to test this tomorrow morning. Will let you know if it resolves the issue.

nti1999Author Commented:
Deployed the new log on script today and it ran w/o issue. I'll be running my RoboCopy task tonight and will let you know if the problems have been resolved.

Thanks for your patience in working through this with me.

nti1999Author Commented:

My apologies for taking longer than expected to provide the status update on this issue.

The log on script seems to have worked and the RoboCopy is now able to backup the profile.v2 folders of the users' profiles w/o issue.

Thank you once again for the assist as well as the patience while I worked through this issue.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.