Devolutions Password Manager pre-configuration quick start

Windows

Learn how to quickly deploy Devolutions Password Manager with pre-configured workspaces and settings across across across Windows endpoints.

See Devolutions Password Manager pre-configuration for more detailed instructions, troubleshooting, and advanced scenarios.

What is pre-configuration

Pre-configuration allows you to deploy Devolutions Password Manager Windows app with:

• Workspaces already configured (Devolutions Server, Devolutions Cloud)
• Application settings pre-applied (language, security, locking options)
• Zero user setup required; users launch and are immediately productive

Quick start: choose your method

For enterprise deployment (Intune/SCCM)

• Use DEPLOY_CONFIG for automated deployments: Recommended for Intune, SCCM, silent installs

msiexec /i Devolutions.PasswordManager.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

Where to get Config.cfg?

• Create using UI Configuration Tool (Tools – Custom Installation in Devolutions Password Manager)
• Or manually create a .cfg file

For Simple deployments

• Use inline MSI parameters for quick deployments

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

Quick examples

Example 1: Deploy Devolutions Server with settings

msiexec /i Devolutions.PasswordManager.msi /qn ^
  DVLS_SERVER_URL="https://devolutions-server.company.com" ^
  LOCKING_OPTION="windowsCredentials" ^
  LANGUAGE="en-US"

Example 2: Deploy Devolutions Cloud

# With Organization ID
msiexec /i Devolutions.PasswordManager.msi /qn ^
  HUB_NAME="mycompany" ^
  ORGANIZATION_ID="12345678-1234-1234-1234-123456789abc" ^
  REDUCE_TO_TRAY_ON_CLOSE="true"

# Without Organization ID (if not required by your Devolutions Cloud)
msiexec /i Devolutions.PasswordManager.msi /qn ^
  HUB_NAME="mycompany" ^
  REDUCE_TO_TRAY_ON_CLOSE="true"

Example 3: Deploy using config file

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

Configuration file format

Configuration files (.cfg) use JSON format:

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

• Multiple servers: Add more objects to the dvls array.

Microsoft Intune deployment

Quick steps

1. Prepare files:

• Devolutions.PasswordManager.msi
• config.cfg
• Install-Devolutions.PasswordManager.ps1 (see below)

1. PowerShell script (Install-Devolutions.PasswordManager.ps1):

$ConfigSource = "$PSScriptRoot\config.cfg"
$ConfigTarget = "C:\Program Files\config.cfg"
$MsiPath = "$PSScriptRoot\Devolutions.PasswordManager.msi"

# Copy config.cfg to Program Files
try {
    Copy-Item -Path $ConfigSource -Destination $ConfigTarget -Force
} catch {
    Write-Host "Error copying config file: $($_.Exception.Message)"
    exit 1
}

# Install MSI silently with DEPLOY_CONFIG parameter
$Arguments = "/i `"$MsiPath`" /qn /norestart DEPLOY_CONFIG=`"C:\Program Files\config.cfg`""
$Process = Start-Process "msiexec.exe" -ArgumentList $Arguments -Wait -PassThru
exit $Process.ExitCode

1. Create .intunewin package:

IntuneWinAppUtil.exe -c C:\IntuneApps\Devolutions Password Manager -s Install-Devolutions.PasswordManager.ps1 -o C:\Output

1. Configure in Intune:

• Install command: `powershell.exe -ExecutionPolicy Bypass -File .\Install-Devolutions.PasswordManager.ps1
• Uninstall command: msiexec.exe /x {PRODUCT-CODE-GUID} /qn /norestart
• Install behavior: System
• Detection rule: MSI (Intune auto-detects the product code)
• What happens on the endpoint: Intune runs the script, which copies config.cfg to C:\Program Files\ and installs the MSI with DEPLOY_CONFIG. The MSI applies the configuration, and users get a fully configured app on first launch

File locations

• System-wide (all users): %ProgramData%\net.devolutions\Devolutions Password Manager\DefaultConfig.cfg
• Per-user: %APPDATA%\net.devolutions\Devolutions Password Manager\Config.cfg
• Note: System-wide requires config.ready indicator file in same directory

Common settings

Security settings

{
  "language": "en-US",
  "reduceToTrayOnClose": true,
  "useFavicon": true,
  "useEntriesSyncOnDatasourceAccess": true
}

Locking options

• password - Master password
• biometric - Fingerprint/Face ID
• windowsCredentials - Windows Hello

Language codes

en-US, fr, de, es, cs, hu, it, nl, pl, ru, sv, tr, uk, zh-CHS, zh-TW

Troubleshooting quick fixes

Config not applied

• Check if the 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

Settings not persisting

• System configuration only applies if user configuration doesn't exist
• Once user modifies settings, they are saved to user config and override system defaults.

Decision tree

Enterprise deployment?
├─ YES → Use DEPLOY_CONFIG with .cfg file
│        (Intune, SCCM, silent installs)
│
├─ Simple setup → Use inline MSI parameters
│                 (Quick, one Devolutions Server)
│
└─ Complex setup → Create .cfg with UI tool first
                   (Multiple servers, many settings)

Support & Resources

• Full documentation
• MSI parameters reference
• Configuration Settings
• [e-mail]
• Forum

macOS

Learn how to quickly deploy Devolutions Password Manager with pre-configured workspaces and settings across across macOS endpoints.

See Devolutions Password Manager pre-configuration for more detailed instructions, troubleshooting, and advanced scenarios.

What is pre-configuration

Pre-configuration lets you deploy Devolutions Password Manager macOS app with:

• Workspaces already configured Devolutions Server, Devolutions Cloud
• Application settings pre-applied (language, security, locking options)
• Zero user setup required; users launch and are immediately productive

For MDM-managed Macs (recommended)

Use Jamf Pro or Intune MDM profiles - Enterprise standard for managed fleets.

1. Download the Jamf schema: Jamf Pro JSON Schema.
2. In Jamf Pro, go to Computers – Configuration Profiles – Application & Custom Settings.
3. Upload the JSON schema and configure settings in the GUI.
4. Scope the profile to target computers.

Preference domain: net.devolutions.authenticator

Why use MDM

• Centralized management from the MDM console
• Highest priority (overrides file-based configuration)
• Policy enforcement capabilities
• Enterprise-standard approach

For non-MDM environments

Use configuration files for scripted deployments or environments without MDM.

System-wide deployment

sudo cp config.cfg "/Library/Application Support/Devolutions/Devolutions Password Manager/DefaultConfig.cfg"

Examples

Example 1: Configure a Devolutions Server with Jamf Pro

Using the Jamf JSON schema (GUI):

1. Upload the schema to a Jamf Pro configuration profile
2. Configure settings, for example:

   • Devolutions Server: Add a server with URL https://devolutions-server.company.com
   • Locking method: Biometric (Touch ID)
   • Lock when backgrounded: Enabled
3. Scope and deploy

Example 2: Create a manual configuration profile (plist)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadType</key>
            <string>net.devolutions.authenticator</string>
            <key>PayloadIdentifier</key>
            <string>net.devolutions.authenticator.config</string>
            <key>PayloadDisplayName</key>
            <string>Devolutions Password Manager Configuration</string>
            <key>language</key>
            <string>en-US</string>
            <key>lockingOption</key>
            <string>biometric</string>
        </dict>
    </array>
</dict>
</plist>

Example 3: defaults command (Testing)

# Configure settings
defaults write net.devolutions.authenticator language -string "en-US"
defaults write net.devolutions.authenticator lockingOption -string "biometric"
defaults write net.devolutions.authenticator useBackgroundLock -bool true

Configuration file format

Configuration files (.cfg) use JSON format:

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

Multiple servers Add more objects to the dvls array.

File locations

• System-wide: /Library/Application Support/Devolutions/Devolutions Password Manager/DefaultConfig.cfg
• Per-user: ~/Library/Application Support/Devolutions Password Manager/Config.cfg
• MDM (highest priority): net.devolutions.authenticator preference domain

Priority order

1. MDM Managed Preferences (highest priority)
2. User Configuration File
3. System Configuration File

Common settings

Security settings

{
  "language": "en-US",
  "reduceToTrayOnClose": true,
  "useFavicon": true,
  "useEntriesSyncOnDatasourceAccess": true
}

Locking options

• password - Master password
• biometric - Touch ID

Language codes

en-US, fr, de, es, cs, hu, it, nl, pl, ru, sv, tr, uk, zh-CHS, zh-TW

Troubleshooting quick fixes

MDM config not applied

• Verify preference domain: net.devolutions.authenticator
• Check profile status: System Preferences – Profiles
• Force refresh: sudo profiles renew -type enrollment

Config file not loaded

• Check file location and permissions (chmod 644)
• Validate JSON syntax (no trailing commas)
• Delete user config to allow system config to apply

Touch ID not working

• Verify Mac has Touch ID hardware
• Ensure Touch ID is configured in System Preferences
• Falls back to password if unavailable

Decision tree

Is this a managed Mac?
├─ YES (Jamf/Intune) – Use MDM profiles
│                      (Highest priority, centralized)
│
└─ NO – Use config files
        - System-wide: /Library/Application Support/...
        - Per-user: ~/Library/Application Support/...

Verify configuration

Check MDM settings:

defaults read net.devolutions.authenticator

Check specific setting:

defaults read net.devolutions.authenticator language

Support & resources

• Full documentation
• Configuration settings
• Download schema
• [e-mail]
• Forum

iOS

Learn how to quickly deploy Devolutions Password Manager with pre-configured workspaces and settings across iOS devices.

See Devolutions Password Manager pre-configuration for more detailed instructions, troubleshooting, and advanced scenarios.

What is MDM pre-configuration

MDM pre-configuration allows you to deploy Devolutions Password Manager with:

• Workspaces already configured (Devolutions Server, Devolutions Cloud)
• Application settings pre-applied (security, locking options)
• Zero user setup required; users launch and are immediately productive

Prerequisites

• Jamf Pro server or Apple MDM solution
• Devolutions Password Manager deployed via MDM
• iOS 13.0+ on managed devices
• Devices enrolled in MDM

Quick Start: Jamf pro deployment

Option 1: Using AppConfig specfile (recommended)

1. Download the AppConfig specfile.
2. Upload to the Jamf AppConfig Generator and configure settings via the GUI form.
3. Download the generated plist.
4. In Jamf Pro, navigate to Mobile Device Apps – Devolutions Password Manager – App Configuration.
5. Paste the generated plist.
6. Scope to target devices.
7. Deploy.

Option 2: Direct plist configuration

If not using the specfile, enter configuration directly as a plist dictionary in Jamf Pro's App Configuration field. Use the flat key format (the app auto-transforms it):

{
  "dvls": [
    {
      "name": "Production DVLS",
      "serverUrl": "https://devolutions-server.company.com",
      "serverVersion": "2024.1"
    }
  ],
  "hubs": [
    {
      "url": "https://password-manager.devolutions.app",
      "organizationId": "your-org-id",
      "type": "business",
      "version": "2020"
    }
  ],
  "configs": {
    "lockingOption": "biometric",
    "useBackgroundLock": true,
    "backgroundLockDelay": 0,
    "useLockWhenInactive": true,
    "lockInactivityDelay": 300
  }

Configuration examples

Devolutions Server only

{
  "dvls": [
    {
      "name": "Corporate DVLS",
      "serverUrl": "https://devolutions-server.company.com"
    }
  ]
}

Devolutions Cloud with security

{
  "hubs": [
    {
      "url": "https://password-manager.devolutions.app",
      "organizationId": "",
      "type": "business",
      "version": "2020"
    }
  ],
  "configs": {
    "lockingOption": "biometric",
    "useBackgroundLock": true,
    "backgroundLockDelay": 0
  }
}

Multiple workspaces

{
  "dvls": [
    {
      "name": "Production Devolutions Server",
      "serverUrl": "https://devolutions-server-prod.company.com"
    },
    {
      "name": "Test Devolutions Server",
      "serverUrl": "https://devolutions-server-test.company.com"
    }
  ],
  "hubs": [
    {
      "url": "https://password-manager.devolutions.app",
      "organizationId": "org-abc123",
      "type": "business",
      "version": "2020"
    }
  ]
}

Security settings

Setting	Values	Description
lockingOption	"", "biometric"	App locking method.
useBackgroundLock	true, false	Lock when backgrounded.
backgroundLockDelay	0, 60, 300, 900, 1800, 3600	Delay before locking (seconds).
useLockWhenInactive	true, false	Auto-lock after inactivity.
lockInactivityDelay	30, 60, 120, 180, 240, 300	Inactivity timeout (seconds).

General settings

Setting	Values	Description
useFavicon	true, false	Download website favicons.
autoSearch	true, false	Enable auto-search in vault.
useHubEmbeddedBrowser	true, false	Use embedded browser for Devolutions Cloud.
highlightSpecialCharacters	true, false	Highlight special characters.
shareUsageData	true, false	Share anonymous analytics.

Troubleshooting quick fixes

Config not applied

• Verify device: Settings – General – VPN & Device Management
• Check app is MDM-managed (deployed via MDM, not App Store)
• Validate JSON syntax (use jsonlint.com)
• Delete and reinstall app

Users can't delete pending workspaces

• New in 2025.3.2: Users can now delete pending workspaces
• Long-press workspace – Select Remove

Face ID/Touch ID not working

• Verify device has biometric hardware
• Ensure Face ID/Touch ID is set up in Settings
• Falls back to passcode if unavailable

Best practices

Recommended security settings

{
  "lockingOption": "biometric",
  "useBackgroundLock": true,
  "backgroundLockDelay": 0,
  "useLockWhenInactive": true,
  "lockInactivityDelay": 300,
}

Why

• Enforces Face ID/Touch ID
• Locks immediately when backgrounded
• Auto-locks after 5 minutes of inactivity

URL Format requirements

• Include protocol (https://)
• Be valid, accessible URLs
• No trailing slash

Examples:

• https://devolutions-server.company.com
• devolutions-server.company.com (missing https://)

Deployment steps summary

1. Download the AppConfig specfile.
2. Upload to the Jamf AppConfig Generator.
3. Configure settings via GUI form.
4. Download the generated plist.
5. In Jamf Pro: Mobile Device Apps – Devolutions Password Manager – App Configuration.
6. Paste plist, scope to target devices, deploy.
7. Verify on test device.

Support & resources

• Full Documentation
• AppConfig Specfile
• Configuration examples
• [e-mail]
• Jamf support

AppConfig Specfile

Below is the AppConfig spec file in .xml format.

<?xml version="1.0" encoding="UTF-8"?>
<managedAppConfiguration>
  <version>1</version>
  <bundleId>net.devolutions.workspace.mobile</bundleId>

  <dict>
    <!-- DVLS configuration -->
    <string keyName="dvls_serverUrl"></string>

    <!-- Devolutions Cloud configuration -->
    <string keyName="hub_url"></string>
    <string keyName="hub_organizationId"></string>

    <!-- Security settings -->
    <string keyName="language">en-US</string>
    <string keyName="lockingOption"></string>
    <boolean keyName="useBackgroundLock">false</boolean>
    <integer keyName="backgroundLockDelay">0</integer>
    <boolean keyName="useLockWhenInactive">false</boolean>
    <integer keyName="lockInactivityDelay">30</integer>

    <!-- General settings -->
    <boolean keyName="shareUsageData">false</boolean>
    <boolean keyName="useFavicon">false</boolean>
    <boolean keyName="autoSearch">false</boolean>
    <boolean keyName="useHubEmbeddedBrowser">true</boolean>
    <boolean keyName="highlightSpecialCharacters">false</boolean>
  </dict>

  <presentation defaultLocale="en-US">
    <!-- Devolutions Server URL -->
    <field keyName="dvls_serverUrl" type="input">
      <label>
        <language value="en-US">Devolutions Server URL</language>
      </label>
      <description>
        <language value="en-US">Full URL to the Devolutions Server including https:// (e.g., https://devolutions-server.company.com)</language>
      </description>
    </field>

    <!-- Devolutions Cloud URL -->
    <field keyName="hub_url" type="input">
      <label>
        <language value="en-US">Devolutions Cloud URL</language>
      </label>
      <description>
        <language value="en-US">Full Devolutions Cloud URL including https:// (e.g., https://yourcompany.devolutions.app)</language>
      </description>
    </field>

    <!-- Devolutions Cloud organization ID -->
    <field keyName="hub_organizationId" type="input">
      <label>
        <language value="en-US">Devolutions Cloud Organization ID</language>
      </label>
      <description>
        <language value="en-US">Organization identifier for Devolutions Cloud (optional)</language>
      </description>
    </field>

    <!-- Language -->
    <field keyName="language" type="select">
      <label>
        <language value="en-US">Language</language>
      </label>
      <description>
        <language value="en-US">App display language</language>
      </description>
      <options>
        <option value="en-US">
          <language value="en-US">English (US)</language>
        </option>
        <option value="fr">
          <language value="en-US">French</language>
        </option>
        <option value="de">
          <language value="en-US">German</language>
        </option>
        <option value="es">
          <language value="en-US">Spanish</language>
        </option>
        <option value="cs">
          <language value="en-US">Czech</language>
        </option>
        <option value="hu">
          <language value="en-US">Hungarian</language>
        </option>
        <option value="it">
          <language value="en-US">Italian</language>
        </option>
        <option value="nl">
          <language value="en-US">Dutch</language>
        </option>
        <option value="pl">
          <language value="en-US">Polish</language>
        </option>
        <option value="ru">
          <language value="en-US">Russian</language>
        </option>
        <option value="sv">
          <language value="en-US">Swedish</language>
        </option>
        <option value="tr">
          <language value="en-US">Turkish</language>
        </option>
        <option value="uk">
          <language value="en-US">Ukrainian</language>
        </option>
        <option value="zh-CHS">
          <language value="en-US">Chinese (Simplified)</language>
        </option>
        <option value="zh-TW">
          <language value="en-US">Chinese (Traditional)</language>
        </option>
      </options>
    </field>

    <!-- Locking option -->
    <field keyName="lockingOption" type="select">
      <label>
        <language value="en-US">Locking Method</language>
      </label>
      <description>
        <language value="en-US">Authentication method for app locking</language>
      </description>
      <options>
        <option value="">
          <language value="en-US">None</language>
        </option>
        <option value="biometric">
          <language value="en-US">Biometric (Touch ID/Face ID)</language>
        </option>
      </options>
    </field>

    <!-- Lock when backgrounded -->
    <field keyName="useBackgroundLock" type="checkbox">
      <label>
        <language value="en-US">Lock When Backgrounded</language>
      </label>
      <description>
        <language value="en-US">Lock app when it goes to background</language>
      </description>
    </field>

    <!-- Background lock delay -->
    <field keyName="backgroundLockDelay" type="select">
      <label>
        <language value="en-US">Background Lock Delay</language>
      </label>
      <description>
        <language value="en-US">Time to wait before locking when backgrounded</language>
      </description>
      <options>
        <option value="0">
          <language value="en-US">Immediately</language>
        </option>
        <option value="60">
          <language value="en-US">1 minute</language>
        </option>
        <option value="300">
          <language value="en-US">5 minutes</language>
        </option>
        <option value="900">
          <language value="en-US">15 minutes</language>
        </option>
        <option value="1800">
          <language value="en-US">30 minutes</language>
        </option>
        <option value="3600">
          <language value="en-US">1 hour</language>
        </option>
      </options>
    </field>

    <!-- Auto-lock when inactive -->
    <field keyName="useLockWhenInactive" type="checkbox">
      <label>
        <language value="en-US">Auto-Lock When Inactive</language>
      </label>
      <description>
        <language value="en-US">Lock after period of inactivity</language>
      </description>
    </field>

    <!-- Inactivity lock delay -->
    <field keyName="lockInactivityDelay" type="select">
      <label>
        <language value="en-US">Inactivity Lock Delay</language>
      </label>
      <description>
        <language value="en-US">Time before locking due to inactivity</language>
      </description>
      <options>
        <option value="30">
          <language value="en-US">30 seconds</language>
        </option>
        <option value="60">
          <language value="en-US">1 minute</language>
        </option>
        <option value="120">
          <language value="en-US">2 minutes</language>
        </option>
        <option value="180">
          <language value="en-US">3 minutes</language>
        </option>
        <option value="240">
          <language value="en-US">4 minutes</language>
        </option>
        <option value="300">
          <language value="en-US">5 minutes</language>
        </option>
      </options>
    </field>

    <!-- Share usage data -->
    <field keyName="shareUsageData" type="checkbox">
      <label>
        <language value="en-US">Share Usage Data</language>
      </label>
      <description>
        <language value="en-US">Share anonymous usage analytics</language>
      </description>
    </field>

    <!-- Use favicons -->
    <field keyName="useFavicon" type="checkbox">
      <label>
        <language value="en-US">Use Favicons</language>
      </label>
      <description>
        <language value="en-US">Download and display website favicons for entries</language>
      </description>
    </field>

    <!-- Auto search -->
    <field keyName="autoSearch" type="checkbox">
      <label>
        <language value="en-US">Auto Search</language>
      </label>
      <description>
        <language value="en-US">Enable auto-search in vaults</language>
      </description>
    </field>

    <!-- Use Devolutions Cloud embedded browser -->
    <field keyName="useHubEmbeddedBrowser" type="checkbox">
      <label>
        <language value="en-US">Use Devolutions Cloud Embedded Browser</language>
      </label>
      <description>
        <language value="en-US">Open Devolutions Cloud connections in embedded browser</language>
      </description>
    </field>

    <!-- Highlight special characters -->
    <field keyName="highlightSpecialCharacters" type="checkbox">
      <label>
        <language value="en-US">Highlight Special Characters</language>
      </label>
      <description>
        <language value="en-US">Highlight special characters in passwords</language>
      </description>
    </field>
  </presentation>
</managedAppConfiguration>
```</div></div>