Problem:
When will Windows ACLs work and when will it not work?
Solution:
The current version is capable of transferring ACLs when both source and destination servers are running a Windows operating system based on the NTFS file system (FAT file systems do not support ACLs). When replicating files from NTFS to FAT, the file and directories will be replicated, however the ACLs can not be applied to the FAT file system. When replicating from FAT to NTFS, the files and directories that are delivered to the NTFS file system inherit the ACLs from their new parent directories.
Another thing to note regarding ACLs is that Windows user accounts on the source server may not exist on the target server. FRP does not replicate Windows user accounts. In this case the ACLs applied on the target may contain invalid entries. FRP will write a Warning message to its log file and an administrator can manually fix the target ACLs. This is not a problem when using a Windows domain to share Windows accounts across servers.
Another approach is to not replicate ACLs. If the source and target server use different Windows accounts, you might consider disabling ACLs replication. In this case, the ACLs are inherited from the directories on the target. In the current version, ACL replication is enabled or disabled using a global application parameter which applies to all replication jobs. By default, ACL replication for Windows is enabled. If you choose to disable this feature, edit the file libs2s.properties and set the value of "s2s.acl" to false.
Also see ACLs not updated