Permissions incorrectly ordered message after Robocopy

[Guest Aaron]

I recently used Robocopy to migrate a number of file shares from one

file server to another. The files were copies from a Windows 2003 SP1

server to a Windows 2003 R2 SP2 server using the /COPYALL command.

Everything appeared to go rather smoothly and so far everything

appears to be working just fine.

 

However, I've noticed that if you create a NEW subfolder within any of

the folders that were copied over, and then use the GUI to view the

security settings for that folder, you get a warning pop up saying

that the permission entries are incorrectly ordered. If I click Ok,

everything looks fine. If, after clicking OK on that new folder I

then create a subfolder within THAT one, then look at IT's security

settings, no error results. All the subfolders that were copies over

do not show any such errors, but creating new sub-folders at any level

in the folder hierarchy (except for the disk root, but that wasn't

copies via robocopy obviously) will result in this odd error.

 

THoughts on how to correct this?

[Guest Aaron]

Re: Permissions incorrectly ordered message after Robocopy

 

On Apr 4, 2:44 pm, Aaron <Aaron.Sm...@kzoo.edu> wrote:

> I recently used Robocopy to migrate a number of file shares from one

> file server to another. The files were copies from a Windows 2003 SP1

> server to a Windows 2003 R2 SP2 server using the /COPYALL command.

> Everything appeared to go rather smoothly and so far everything

> appears to be working just fine.

>

> However, I've noticed that if you create a NEW subfolder within any of

> the folders that were copied over, and then use the GUI to view the

> security settings for that folder, you get a warning pop up saying

> that the permission entries are incorrectly ordered. If I click Ok,

> everything looks fine. If, after clicking OK on that new folder I

> then create a subfolder within THAT one, then look at IT's security

> settings, no error results. All the subfolders that were copies over

> do not show any such errors, but creating new sub-folders at any level

> in the folder hierarchy (except for the disk root, but that wasn't

> copies via robocopy obviously) will result in this odd error.

>

> THoughts on how to correct this?

 

Working with a couple of smaller, less used directories, I've found a

way to make the error go away. I think the problem is stemming from

the fact that Robocopy copies inherited permissions along with

everything else. The old server was a cluster so there was a

permission added at the "disk" level for the cluster admin account

which got inherited to everything below it. Robocopy copied that over

AS an inherited permission even though on the NEW system, it wasn't

inherited. But I couldn't just remove it because it thought it WAS

inherited. What I did on the small directories was pull up the

security properties of the root share directory (so like G:

\FileShare), turn OFF inheritance, let it copy the ACL's, delete the

cluster admin acl, and apply the changes. Then turn inheritance back

ON, delete the extra ACL's (the copied ones that are now inherited)

and do apply again. After doing that, I can create folders in any

subfolder, and then pull up the security information for that new

folder without any "Out of Order" errors.