If you deploy UFO/AFO to your domain, you can configure these features for your entire domain:

• Default lock duration for files opened with UFO/AFO

By default, when users open or save files with UFO/AFO, files are locked for one hour.
Learn more: UFO/AFO: Manage locked files.

You can configure a different lock duration for all users on your domain.

• Maximum number of files in users' cache (currently available for UFO only)

By default, users can store a maximum of 100 files in their cache.
Learn more: Manage cached files in the UFO status dialog.

You can change the default maximum number of files users can store in their cache.

Important:
– If the UFO/AFO extension is already installed, you must disable and re-enable it or quit and relaunch Chrome to access these features.
– To deploy these features to your domain, you must use Apple Remote Desktop (ARD) for macOS or Group Policy Object (GPO) for Windows.

The configuration is the same for both features: create a new registry key (in Windows) or add a new setting in the config.toml file (on macOS).

Automatically generated table of contents

Configure domain-wide UFO/AFO features in Windows

Configure the domain-wide UFO/AFO features in the Windows Registry.

• For all users on the machine:
  • 32 bits:
    • UFO lock duration:
      HKEY_LOCAL_MACHINE\SOFTWARE\AODocs\UFO\LockDurationSeconds
    • AFO lock duration:
      HKEY_LOCAL_MACHINE\SOFTWARE\AODocs\AFO\LockDurationSeconds
    • maximum number of files in cache for UFO:
      HKEY_LOCAL_MACHINE\SOFTWARE\AODocs\UFO\CacheFilesMax
  • 64 bits:
    • UFO lock duration:
      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AODocs\UFO\LockDurationSeconds
    • AFO lock duration:
      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AODocs\AFO\LockDurationSeconds
    • maximum number of files in cache for UFO: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AODocs\UFO\CacheFilesMax

• For the current user:
  • UFO lock duration:
    HKEY_CURRENT_USER\Software\AODocs\UFO\LockDurationSeconds
  • AFO lock duration:
    HKEY_CURRENT_USER\Software\AODocs\AFO\LockDurationSeconds
  • maximum number of files in cache for UFO: HKEY_CURRENT_USER\Software\AODocs\UFO\CacheFilesMax

Notes:
– The value for the lock duration must be defined in seconds.
– The value for the maximum number of files in cache must be an integer.

To configure the domain-wide UFO/AFO features in Windows:

1. Open the Registry Editor.

2. Expand:

• HKEY_CURRENT_USER\Software (for the current user)
• HKEY_LOCAL_MACHINE \ SOFTWARE (for all users)

3. Right-click New > Key and name the key AODocs.

4. Right-click New > Key and name the key UFO or AFO.

Note: If you've already configured a UFO/AFO domain-wide feature, the AODocs and UFO or AFO keys already exist, so you can skip steps 3 and 4.

5. Right-click UFO or AFO and select New > QWORD (64-bit) Value.

6. Name the value LockDurationSeconds or CacheFilesMax, depending on which feature you want to configure.

7. Double-click the value.

8. Under Base, choose Decimal.

9. Under Value data, enter the required value:

• for LockDurationSeconds, enter the required lock duration in sections, for example, enter 1800 to set a lock duration of 30 minutes
• for CacheFilesMax, enter the required maximum number of files that users can have in their cache

10. Click OK.

Configure domain-wide UFO/AFO features on macOS

Configure the domain-wide UFO/AFO features for the current user in a TOML file in the sync client's hidden directory.

Notes:
– You can't set the domain-wide UFO/AFO features for all users on macOS.
– The value for the lock duration must be defined in seconds.
– The value for the maximum number of files in cache must be an integer.

To configure the domain-wide UFO/AFO features on macOS:

1. Create a plain text file called config.toml or open it if it exists already. This file must be located in the:

• $HOME/.syncclient folder for UFO
• $HOME/.syncclient-oss folder for AFO

2. Add a new setting and the required value in the config.toml file:

• for a lock duration of 30 minutes: lock_duration_seconds = 1800
• for a maximum of 500 files in cache: cache_files_max = 500