I experienced this same issue with XCACLS when I was planning our file migration to our filers (from NetWare) about a year ago. XCACLS just doesn't do the job, so I used a utility called REACL.EXE to set the permissions instead. Highly recommended!

-----Original Message----- From: Hight, Steve - Perot [mailto:SHight@chw.edu] Sent: Monday, January 27, 2003 11:35 AM To: 'toasters@mathworks.com' Subject: Permissions on Folder are incorrectly ordered error

After migrating a lot of data I used xcacls.exe on a CIFS only filer to recursively set the permissions on a huge volume of home directories.

I am now having the symptoms described in MS article http://support.microsoft.com/default.aspx?scid=kb;en-us;296865 http://support.microsoft.com/default.aspx?scid=kb;en-us;296865 .

When I view the permissions, I get the following error: The permissions on xxxx are incorrectly ordered, which may cause some entries to be ineffective. Click OK to continue and sort the permission correctly, or press CANCEL to reset the permissions. Microsoft Says: This problem can occur because Windows 2000 has introduced a new inheritance model in which directly applied access control entries (ACEs) have precedence over inherited ACEs. The computer implements this precedence by placing directly applied ACEs ahead of inherited ACEs in a discretionary access control list (DACL). Earlier versions of Microsoft Windows NT did not distinguish between inherited and directly applied ACEs.

When you use Subinacl to set the permission to grant full permission, the ACE is put at the end of the access control list (ACL). Because the ACE is directly applied, when you view the permission in Registry Editor, you can receive an error message as the ACE must be placed ahead of the other inherited ACEs. Subinacl does not arrange the ACEs properly.

Any ideas?

Thank you,

Steve Hight perotsystems