ACLs not being updated can be due to one of the following conditions.
1. In the console server list, select each one of your servers in turn and edit the advanced features. Look for the two items below in the options and make sure the checkbox by each of them is checked. Save the page and then repeat on each server.
- Access control list (ACL) replication
- Allow ACL changes to trigger a real-time replication
When done editing these items restart the job.**
2. ACL changes are not detected in a directory walk of the files, ACL changes are only detected in real-time changes of the ACL or if the time/date stamp of the file is changed.
The only way to force an update on existing files is by setting your job to a copy job (to prevent losing your source files if you have a two way job set up) then delete the files that need to be updated on the destination and restart the job. This will cause a new replication of the files with the up to date permissions and ownership.
**NOTICE: Whether the above-mentioned ACL toggle was set or not, Items already replicated with the incorrect ACL information will not be updated until a change is made to the file. If you do nothing further the ACLs will not change until the next time the file is updated.