I can not get MoveSecurityAttributes (See: KB310316) to work underWindows 7. I have also read that others could no longer get this towork running Server 2008 R2.Is there a new registry setting for this or perhaps a hotfix that willallow moving files on the same volume WITHOUT copying the securityattributes?
Best regards, FlyingHorse
The article is for Windows Server 2003 and Windows XP. The function will not work in other systems.
In Windows Server 2008 R2 and Windows 7, in order to copy the directory to the destination path by conserving the security settings( ACL with all ACEs), you may consider using the Robocopy utility as what Cory mentioned.
robocopy <Source> <Destination> /e /sec
Ex. robocopy c:\home E:\home /e /sec
/e: Copies subdirectories. Note that this option includes empty directories.
/sec: by using this option, we can copies files with their security.
You can also try RichCopy.
If you have any feedback on our support, please contact email@example.com.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
Anyone have an update on this? This is a major roadblock for us migrating to Windows 7. Without the MoveSecurityAttributes registry key, users are able to move folders/files from one folder to another and cause security breaches since the original permissions are kept which can include users/groups that should not have access in the new destination..
I dont understand that MoveSecurityAttributes is a must when sharing files. Those that are not using it must have a nightmare trying to maintain coherent permissions on the file servers.. or havent realize that end-users moving document on the same file share are also copying the original permissions.
The suggested answer has nothing to do with the original problem
In order to use MoveSecurityAttributes as you were able in Windows XP/Windows Server 2003, you will need to install the following hotfix:
Hope this helps!