NTFS security - fail to update on rescans

[Guest]

Hi,

I've searched the forum for this issue, but not being able to really find this exact case, so therefore I ask the question:

It seems that when setting up a job in VV (and specifying that NTFS security are to be processed), the NTFS security is ONLY considered during the COPY process. When running a compare after the copy, NTFS security changes are not considered.

I'm about to move a fileshare (some 165.000 files), and VV keeps good track of the files themselves. But, if users using these files edit rights to folders/files, but DOES NOT edit the file itself => VV will not detect this.

I've looked for some settings in VV to detect this, but not found. Am I looking too bad, or are there simply no way to use VV for this use case?

[Alice]

'When running a compare after the copy, NTFS security changes are not considered. '


In my experience there has to be a change in the file system, ie files added/modified/deleted to 'trigger' VV to replicate NTFS permissions once again for the associated files/folders.

I use VV to replicate NTFS permissions initially ie for the first ever copy to the Destination, then just in case there's been changes in the folder/file permissions (but not the actual files) I use ICACLS to backup the permissions in the Source, then restore them to the Destination eg :

Backup :