Quick start to deploy Workspace desktop app

Auf dieser Seite

Deploy Workspace desktop app with pre-configured data sources and settings across your organization. View the complete documentation for detailed instructions, troubleshooting, and advanced scenarios.

What is pre-configuration

Pre-configuration allows you to deploy Workspace desktop app with:

  • Data sources already configured (Devolutions Server, Devolutions Hub Business).

  • Application settings pre-applied (language, security, locking options).

  • Zero user setup required; users launch and are immediately productive.

Choose your method

Enterprise deployment

Use DEPLOY_CONFIG for Intune/SCCM, as it is recommended for automated deployments.

msiexec /i Workspace.msi /qn DEPLOY_CONFIG="C:\path\to\Config.cfg"

Why DEPLOY_CONFIG

  • Works reliably in automated/silent installs.

  • Applies to all users on the machine.

  • No user context issues.

  • Automatically cleans up source config file after successful deployment.

Where to get Config.cfg

  • Create using the UI Configuration Tool (Tools – Custom installation in Workspace desktop app).

  • Or manually create a .cfg file.

Microsoft Intune Deployment

Option 2: Inline MSI Parameters (Simple Deployments)

msiexec /i Workspace.msi /qn ^
  DVLS_SERVER_URL="https://dvls.company.com" ^
  HUB_NAME="mycompany" ^
  ORGANIZATION_ID="your-org-guid" ^
  LANGUAGE="en-US"

Full Windows Instructions | All MSI Parameters

MDM managed

Use Jamf Pro or Intune MDM profiles since it is recommended for enterprise macOS deployments.

  1. Download the Jamf schema: net.devolutions.authenticator.json.

  2. In Jamf Pro: Computers – Configuration Profiles – Application & Custom Settings.

  3. Upload the JSON schema and configure settings via GUI.

  4. Scope to target computers.

Preference Domain: net.devolutions.authenticator

Full MDM Instructions

Quick Examples

Example 1: Deploy Devolutions Server with settings

msiexec /i Workspace.msi /qn ^
  DVLS_SERVER_URL="https://dvls.company.com" ^
  LANGUAGE="fr"

Example 2: Deploy Devolutions Hub Business with settings

msiexec /i Workspace.msi /qn ^
  HUB_NAME="mycompany" ^
  ORGANIZATION_ID="12345678-1234-1234-1234-123456789abc" ^
  LANGUAGE="en-US" ^
  REDUCE_TO_TRAY_ON_CLOSE="true"

Example 3: Deploy using config file

msiexec /i Workspace.msi /qn DEPLOY_CONFIG="C:\path\to\Config.cfg"

Or from network share:

msiexec /i Workspace.msi /qn DEPLOY_CONFIG="\\server\share\Config.cfg"

Configuration file format

Configuration files (.cfg) use .JSON format:

{
  "dvls": [
    {
      "name": "Production Server",
      "serverUrl": "https://dvls.company.com"
    }
  ],
  "hubs": [
    {
      "url": "https://mycompany.devolutions.app",
      "organizationId": "your-org-guid-here"
    }
  ],
  "configs": {
    "language": "en-US",
    "lockingOption": "biometric",
    "clearClipboardSensitiveData": true,
    "clipboardTimer": 60
  }
}

Add more objects to the dvls array if you have multiple servers.

Complete Configuration Reference | All Available Settings

Create config files visually

Use the built-in Configuration Creator tool:

  1. Open Workspace app.

  2. Go to: Tools – Custom installation.

  3. Select data sources and settings.

  4. Export as .cfg file or copy MSI command.

Configuration creator guide

File locations

  • System-wide (all users): %ProgramData%\net.devolutions\Workspace\DefaultConfig.cfg

  • Per-user: %APPDATA%\net.devolutions\Workspace\Config.cfg

  • Note: System-wide requires config.ready indicator file in same directory

  • System-wide: /Library/Application Support/Devolutions/Workspace/DefaultConfig.cfg

  • Per-user: ~/Library/Application Support/Workspace/Config.cfg

  • MDM (highest priority): net.devolutions.authenticator preference domain

Detailed Location Information

Common Scenarios

Scenario Solution
Intune/SCCM deployment Use DEPLOY_CONFIG parameter with .cfg file
Jamf Pro (macOS) Upload .JSON schema to Configuration Profiles
Multiple Devolutions Server Create .cfg file with multiple entries in dvls array
Security compliance Set locking, clipboard, and inactivity settings in config
Multi-language org Create regional .cfg files with different language settings

Decision tree

Is this macOS?
├─ YES → MDM managed?
│         ├─ YES → Use Jamf/Intune MDM profiles (Method 3)
│         └─ NO  → Use config file deployment
│
└─ NO (Windows) → Enterprise deployment?
          ├─ YES → Use DEPLOY_CONFIG with .cfg file
          ├─ Simple setup → Use inline MSI parameters
          └─ Complex setup → Create .cfg with UI tool first

Complete decision matrix

Troubleshooting quick fixes

Config not applied

  • Windows: Check if config.ready file exists next to DefaultConfig.cfg

  • Validate .JSON syntax (no trailing commas)

  • Check file permissions

Intune deployment failing

  • Use DEPLOY_CONFIG (not USER_CONFIG)

  • Package both MSI and .cfg together

  • Use /l*v install.log to capture detailed logs

macOS settings not applying

  • Verify preference domain: net.devolutions.authenticator

  • Check MDM profile is deployed and installed

  • MDM overrides file-based configs

Complete troubleshooting guide

Support & resources

Devolutions Forum logo Share your feedback