Desktop Configurations provide a centralized way to manage how Desktop App Drives are deployed and controlled across user devices within the organization. This feature allows administrators to define which drives appear on user systems, which folders are synced or backed up, and how those drives behave.
This overview outlines the essential steps required to create and deploy a working configuration. For advanced use cases and full technical explanations, refer to the Product Guide.
What It Does
- Centrally defines drive mappings, Offline folders, and Connected folders
- Supports both Windows and macOS (Core version only)
- Assigns configurations to specific user Groups
- Enforces read-only behavior on managed drives and folders – users cannot modify, remove, or override
- Applies updates after restart to avoid interrupting users with active files
How It Works
- When the first drive is added (manually by user, via script or installation command), Desktop App checks for configurations defined in WebUI and applies them immediately instead of adding a default drive.
- The Desktop App regularly checks for new or updated configurations while running.
- If a change is detected, the user will be notified that it will be applied after restarting the app.
- Later changes (for example, drive path or letter updates) are applied after the next restart.
Desktop App Compatibility
This functionality will be respected by following Desktop App versions:
- Desktop App for Windows - version 3.28.0 or higher
- Desktop App Core for Mac - version 1.10.0 or higher (not supported on legacy Desktop App version)
Basic Setup Steps
-
Access Configuration Panel
- Navigate to: Settings → Devices → Desktop Configurations
- Click Add Configuration
-
Define General Information
- Enter a unique Configuration name
- Optionally, provide a description for internal use
-
Choose Target Operating Systems
- Select Windows, macOS, or both
- macOS support applies only to the Desktop App Core
-
Adjust General Settings (per OS)
- Optionally disable Allow user to add drives (enabled by default)
- Optionally disable Send notifications about the available upgrade (enabled by default)
-
Add Drives
- Specify a drive label and on Windows a drive letter
- Optionally define:
- Cloud Start Path – the folder where the drive opens
- Offline Folders – folders always available offline
-
Connected Folders – sync users’ local folders (Desktop, Documents, Downloads) to the cloud
-
Assign to Groups
- Add one or more user groups to determine who receives this configuration. Users outside these groups will not be affected
- Add one or more user groups to determine who receives this configuration. Users outside these groups will not be affected
-
Save or Activate the Configuration
- Click Save configuration in save it in Inactive mode or click Activate to activate the configuration. Inactive configurations can be activated from the configuration list
- Activation requires at least one OS, one drive, and one assigned group
Key Points to Remember
- Managed drives and folders are read-only for users – cannot be remove or modified
- Each connected folder (for example, Desktop, Documents) can be assigned to only one drive per OS configuration
- If a drive letter defined in the configuration is already used on the system (for example, by USB devices), the drive will not mount
- When users belong to multiple groups with different configurations, non-conflicting drives are merged automatically; conflicting ones are resolved based on configuration priority
Best Practice: Basic Configuration Example
A recommended starting setup for many organizations:
- One configuration assigned to all users (for example, All Power Users)
- Drive Z selected to avoid conflicts with commonly used system or device letters
- Connected folders: Desktop and Documents enabled for regular backup of frequently used files
Common Issues and Troubleshooting Tips
| Issue | Cause | Resolution |
| Drive not appearing after configuration is assigned | User has not restarted the Desktop App | Ask the user to restart the app. Configuration changes are applied on restart to prevent disruption. |
| Drive not mounting | Drive letter is already in use by the OS or other software | Edit the configuration and select a different letter (e.g., Z). Validate which letters are unused on target machines. |
| User does not receive any configuration | User is not a member of any assigned group | Verify group membership in the admin panel. Ensure the user is part of at least one group mapped to a configuration. |
| MDM-configured drives are overwritten | Web configuration is applied on top of MDM config | Set enableWebConfigLookup=false in the MDM file to prevent cloud-based configuration from overriding. |
| Offline folders not syncing | Path entered incorrectly or user lacks permission | Double-check cloud path format (e.g., /Shared/Folder) and verify user has access. |
| Connected folders fail to sync | Path mismatch or duplication across drives | Ensure the same connected folder is not assigned to multiple drives in the same configuration. |
Known Limitations
Multiple Domain Support
Receiving configurations from multiple domains is functional but not officially supported. Conflicts may occur and are not resolved automatically.
Multiple Users on a Shared Machine
If more than one user uses centrally managed configurations on the same machine, behavior may be unpredictable. Only one user's configuration should be managed via the system in this scenario.
Drive Letter Conflicts Are Not Auto-Resolved
The system does not detect or resolve local drive letter conflicts. Manual assignment and testing is required to avoid collision.
No Live Drive Switching During Active Sessions
Changes to configurations are only applied after the next app restart. This is by design to avoid interrupting open files and active sessions.
No Support for Overlapping Connected Folders
The same local folder (e.g., Desktop) cannot be mapped to multiple drives within a single OS configuration. The system enforces this through validation.
Legacy macOS Desktop App Is Not Supported
Desktop Configurations for Mac apply only to the current Desktop App Core. Legacy Desktop App for Mac versions are not compatible.
For Full Technical Coverage
This overview is intended for quick onboarding and reference. The Product Guide includes advanced topics such as:
- Conflict resolution between overlapping configurations
- Multi-domain deployment and edge-case behavior
- Mobile Device Management systems integration and web configuration overrides
- Offline folder syncing behavior
- Migration from legacy setups
- Real-world examples and best practices for enterprise rollout
Refer to the product guide whenever planning advanced deployments, working across domains, or troubleshooting complex behavior.