On Thu, Sep 8, 2011 at 21:04, Lists - Level Five <[email protected]> wrote: > Im migrating via robocopy and using the /SEC but noticing the permissions > aren’t coming over .. > > I have a \\server\users folder share that i am copying to \\server2\c$\users > . The copy is going fine using the /MIR option as we prep for migration. I > started poking around and noticed that all the perms are security default > from the top folder. Do I need to shut that off in order for perms to come > over correctly? > > The actual command: robocopy \\server\users\ \\server2\users\ /MIR /SEC /R:5 > /W:3 > > Im going to run it with the /SECFIX or maybe use the /COPY:DATSOU flags > instead?
o- What are the NTFS permissions on the root of the drive containing the target share vs. the permissions on the root of the drive containing the source share? Probably best if you match them. o- Do the NTFS permissions on the the source share directory contain any blocked inheritances? Personally, I start off with the root of any given data drive (not the OS partition) having only System and the local Administrators group listed, and give them Full Control permissions. Then, at any given share point on the drive I start adding in NTFS permissions as needed, and never block inheritance. Then, I enforce that no permissions get applied more then two levels below a share. Keeps things neat and simple, and tends to flatten the directory structure, which IME makes things easier to find. Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
