Activating certain browser policies interferes with Native Messaging and prevents UFO and AFO from functioning. For example, if Native Messaging is blocked by browser policies, communication between the extension and Sync Client is prevented. In this case, the status window indicates that the Sync Client is not installed even when it has been installed.
Below is a list of the relevant policies.
On Chrome (UFO/AFO):
- https://chromeenterprise.google/policies/#NativeMessagingAllowlist
- https://chromeenterprise.google/policies/#NativeMessagingBlocklist
- https://chromeenterprise.google/policies/#NativeMessagingUserLevelHosts
On Edge (AFO):
- https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies#nativemessagingallowlist
- https://learn.microsoft.com/en-us/deployedge/microsoft-edge- policies#nativemessagingblocklist
- https://learn.microsoft.com/en-us/deployedge/microsoft-edge- policies#nativemessaginguserlevelhosts
When NativeMessagingUserLevelHosts is turned on, the single-user Sync Client is blocked unless you add the native host to theNativeMessagingAllowlist.
Note: The domain wide installation works as expected.
When NativeMessagingBlocklist is set to *, all Native Messaging is blocked. In this case, you must explicitly allowlist UFO or AFO in the NativeMessagingAllowlist.
To add the UFO and AFO native hosts in NativeMessagingAllowlist, add the following entries to the allowlist:
- to allowlist UFO:
com.aodocs.syncclient - to allowlist AFO:
com.aodocs.syncclient.oss