I mistyped the bit about permissions. What I am saying is that the folders copied over all have the correct permissions. The files, however, have some sort of default/base permissions. At the source, the files are set to inherit permissions, but that is not being copied over.
I did some more research on this, and I think my problem relates to the version of RoboCopy I am using. I have a couple different versions floating around, and it seems that this behavior is "by design" according to http://blogs.technet.com/filecab/archive/2008/07/31/robocopy-mir-switch- mirroring-file-permissions.aspx. It is however, different from what I have experienced using an older version of RoboCopy in the past. Basically all I want is to mirror the directory structure over, maintaining all the security/owner information. Since I didn't discover the permissions issue until after the (very large) initial mirror had completed, I just want to go back and fix the permissions on the already copied files. The options indicated in the above article for doing this did not work for me, but I *think* I have found the right command-line combo to do that with: /E /IS /IT /COPY:ATSO I am doing regular mirrors up until a certain time when I will cut over to the new location, so having to do the 2 different runs for file copies and permissions is not a great solution. Anybody that has any further insight or suggestions, I am happy to hear it. Bill Mayo -----Original Message----- From: Joseph L. Casale [mailto:[email protected]] Sent: Tuesday, March 09, 2010 8:46 PM To: NT System Admin Issues Subject: RE: Robocopy question The "D" flag copies data, so omit that I presume. Your problem stems from the fact that the Local Users on the target Server don't exist on the dest server, but you should get an orphaned sid in its place. I'm not sure what you mean anyway, folders inheriting permissions from files? -----Original Message----- From: Mayo, Bill [mailto:[email protected]] Sent: Tuesday, March 09, 2010 2:59 PM To: NT System Admin Issues Subject: Robocopy question Does anybody know if using Robocopy with the "/B" option would have the effect of adjusting permissions on the files (not folders) to some sort of base/standard? I am migrating some files and had decided to try this option to get around "access denied" errors for things where folks had changed the default permissions or whatnot. I thought it was going swimmingly until I discovered that the files are not getting the permissions from the originals, although I had the "/COPY:DATSO" attribute there (even tried with "/COPYALL"). The *folders* have got the right permissions, they just are not inheriting the permissions from the files. The files are basically set to Administrators and System having full control and Users having read only. Additionally, the owner all show as the local administrator. Here is the command I was using: ROBOCOPY \\server\share E:\dir\subdir\ /B /MIR /COPY:DATSO /R:0 /NDL /LOG+:"c:\path\robolog.txt" /TEE If "/B" is what invoked it, is there any easy way to send a new command that would just go and mirror the permissions/owner? Bill Mayo ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
