We are pleased to announce x360Sync v2.7.0 build .1371, our latest release of x360Sync, which includes important improvements in handling Windows ACLs on desktop devices with File Server Enablement (FSE) mapping. 

Note: With the release of x360Sync v.2.7.0, the desktop client no longer supports outdated Operating Systems, like Windows Vista, Mavericks v.10.9, and Yosemite v.10.10.

Updates

The handling of the Windows Access Control List (ACL) has changed.

x360Sync v2.7.0 introduced the concept of the Team Share permissions role: An administrator can now assign a role to a Team Share subscriber to allow a set of permitted operations.

Synced Tool uses Windows ACL to provide educational messages when a user attempts to perform changes which are not permitted. This functionality required Synced Tool to change the Windows ACL to keep aligned with the permissions provided by the selected Team Share Permission Role.

In the case of File Server Enablement (FSE) mappings, the content that is mapped using FSE is often also shared with a file server, and Windows ACLs are used to control the direct access of users to that content. 

In order to keep the configured Windows ACL intact and to avoid accidental exposure of file server content, a special treatment of Windows ACL has been implemented for FSE mappings.

With 2.7.0.1371, Windows Desktop Synced Tool will make the following changes in Windows ACL:

For FSE mapped content:

• No Windows ACL changes will be made regardless of the Team Share permissions role
• For locked content,  a “Deny Everyone” configuration has been added. (This will not apply to content synced by the lock owner.)
• Once a lock is removed, the “Deny Everyone” configuration is removed.

For regular Synced Folder content:

• Windows ACL will be changed in alignment with the assigned Team Share permissions role, and will be updated in the case of role changes.  Please find more information in this article: Desktop Client 2.7.0.1366 for Windows and the Access Control List (ACL) 
• For locked content, a configuration of  “Deny Everyone” will be added. (This will not apply to content synced by the lock owner.)
• Once a lock is removed, the “Deny Everyone” configuration is removed.