Using File Sync Policies

Overview

File sync policies allow you to exchange and synchronize files between your devices and a server. File sync policies are not bi-directional; you need two separate file sync policies to upload and download files between your devices and SOTI MobiControl. Files synchronize automatically according to a schedule. You can choose to use the device update schedule or specify your own.

When setting up the file sync policy, the deployment server must have permission to read and write to the specified server location. SOTI recommends using a UNC path and that the deployment server run under its own Active Directory user profile. You can use a local path if only one deployment server is being used, and the local path points to a location on the computer running the deployment server.

File sync policies are available on Android, Apple (macOS and iOS), Linux, Windows Desktop Classic, Windows Mobile/CE, and Windows Modern platforms.

Note: On the Apple platform, files synced to iOS devices are also placed in the Content Library. However, content library policies will not apply to these files.

This section contains the following topics:

File Sync Scripts

Use scripts to add automatic processes to the file sync. You may perform these processes on the device (before or after file synchronization).

Important: From SOTI MobiControl 15.7.0 onward, server-side scripts are not supported. See File Sync Rule Server Actions Deprecation for more information.

SOTI MobiControl provides several utilities for managing devices on the deployment server, including one for moving devices. If you run a device move utility before file synchronization, you can ensure that all devices are in the proper location before exchanging any files. Contact SOTI Support for help using this utility.

For information on device-side scripts, see Using Script Commands.

You cannot use file sync scripts on iOS devices.