Large Scale Deployments
Automated installation of the Files.com Desktop App for large number of users can be performed by your IT administrators using SCCM (System Center Configuration Manager) or MDM (Mobile Device Management) tools such as Microsoft Intune, Microsoft GPO, Munki, jamf, or others.
Deploying the desktop app through these endpoint management tools can minimize user errors and support calls, while also eliminating extra steps for IT admins and end users, such as IT administrator having to log in as an administrator on each individual user's machine to install the desktop app. This method also helps in ensuring consistency across multiple systems. After installation, users will still need to log in to the Files.com Desktop App to transfer files using the app or to access and manage files on their locally mounted volume.
Silent Installations for Unattended Windows Deployments
For large scale or unattended deployments across multiple Windows devices, use the EXE installer provided by Files.com. The EXE binary supports silent installation and is designed for use with deployment and device management tools such as SCCM, Group Policy (GPO), PDQ Deploy, or ManageEngine Endpoint Central. This allows automated, scripted installations and is ideal for environments where manual installation is impractical or where IT teams need centralized control over application delivery.
The EXE installer supports standard silent installation switches such as /S, /quiet, /passive, /s /v/qn /norestart.
The following command performs a fully silent installation without a restart. This setup is ideal for unattended deployments managed by IT administrators.
"Files.com Desktop v6.exe" /s /norestart /v/qn
The quoted file name is required because it contains spaces. The /s option runs the EXE installer silently, /v/qn suppresses the installer user interface in the embedded MSI, and /norestart prevents the system from rebooting after the installation.
For Microsoft Intune, we provide a separate pre-packaged .intunewin binary file and instructions specifically designed for the Windows app (Win32) deployment model.
Silent Installations for Unattended macOS Deployments
For large scale or unattended deployments across multiple devices, use the PKG installer provided by Files.com. PKG files are designed for use with deployment and device management tools such as Munki, Jamf, SimpleMDM, Mosyle, Addigy, or Microsoft Intune. This format supports automated, scripted installations and is preferred for any environments where manual installation is impractical or where IT teams need to centrally manage application delivery.
Refer to Apple’s documentation for guidance on deploying PKG files using your organization’s management platform.
Configuration Parameters for Large Scale Deployments
For large scale deployments, configuration parameters (also referred to as a configuration profile or setup configuration) can be distributed to ensure systems are configured consistently and predictably.
These configuration parameters need to be updated in the file named desktopv6.ini, located at C:\Users\<username>\AppData\Roaming\Files.com\desktopv6.ini on Windows and /Users/<username>/.config/Files.com/desktopv6.ini on macOS. Below are the configuration parameters you can update in the desktopv6.ini file.
| Parameter | Details |
|---|---|
startup_launch_on_login | Determines if the application is launched on login. This is either "true" or "false". Default is "true". |
logging_level | The verbosity of the logging output. This can be "DEBUG", "INFO", "WARNING", or "ERROR". Default is "INFO". |
logging_show | Determines whether the logging text output is shown in the main window. This is either "true" or "false". Default is "true". |
automatic_retry_option | Determines whether to retry on a transfer failure. This is either "On" or "Off". Default is "true". This does not apply to transfers made through a mounted volume in File Explorer or Finder. |
upload_overwrite_action | The action to always take during an upload when a file already exists in the remote. This is either "Ask for action" or "Overwrite file". Default is "Ask for action". This does not apply to transfers made through a mounted volume in File Explorer or Finder. |
download_overwrite_action | The action to always take during a download when a file already exists in the local path. This is either "Ask for action" or "Overwrite file". Default is "Ask for action". This does not apply to transfers made through a mounted volume in File Explorer or Finder. |
SAVED_LOCAL_PATH | The folder to open in the local pane on application launch. This applies to the Application UI only. |
connection_native_browser | This parameter applies to macOS only. Determines if the native browser is used for connection authentication or the embedded browser. This is necessary when a hardware key is used for two factory authentication. This is either "true" or "false". Default is "true". |
On Windows, connection settings (including the API key) are securely stored in the Windows Credential Manager. On macOS, they are securely stored in the macOS Keychain.