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 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

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 Workspace.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 Workspace.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 Workspace.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 Workspace.msi /qn ^
  HUB_NAME="mycompany" ^
  REDUCE_TO_TRAY_ON_CLOSE="true"

Example 3: Deploy using config file

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://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:

• Workspace.msi

• config.cfg

• Install-Workspace.ps1 (see below)

1. PowerShell script (Install-Workspace.ps1):

$ConfigSource = "$PSScriptRoot\config.cfg"
$ConfigTarget = "C:\Program Files\config.cfg"
$MsiPath = "$PSScriptRoot\Workspace.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\Workspace -s Install-Workspace.ps1 -o C:\Output

1. Configure in Intune:

• Install command: `powershell.exe -ExecutionPolicy Bypass -File .\Install-Workspace.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\Workspace\DefaultConfig.cfg

• Per-user: %APPDATA%\net.devolutions\Workspace\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

iOS