Deploying via Command Line Last updated June 2, 2026 · Desktop Connect

Command line deployment is useful for scripting, remote deployment via RMM tools, or one-off installations. Desktop Connect uses standard MSIEXEC or EXE installer commands.

Windows MSI Installation

Basic Silent Install:

MSIEXEC /i MyZenV2.msi -Quiet

Silent Uninstall:

MSIEXEC /x MyZenV2.msi -Quiet

Install with Logging (Troubleshooting):

MSIEXEC /i MyZenV2.msi -Quiet /l*v %TEMP%\\atinstall.log

The log file will be created at C:\\Users\[YourUsername]\\AppData\\Local\\Temp\\atinstall.log. Review this log if installation fails.

Key Flags Explained

  • /i — Install (for EXE: install mode)
  • /x — Uninstall
  • -Quiet — Silent mode (no user prompts or UI)
  • -Q or /Q — Quiet (alternative syntax, some installers use this)
  • -QN or /QN — Quiet, no restart (suppresses automatic reboot)
  • /l*v — Log all messages to a verbose log file

Compatibility with MDM Tools

Different MDM tools expect different quiet flags. Consult your MDM documentation for the proper syntax:

  • Microsoft Intune: Typically expects /exenoui /qn for EXE and /qn for MSI
  • Jamf (Windows): Supports -Quiet and /Q
  • Workspace One: Typically uses /Quiet
  • Altiris: Check your deployment template — varies by configuration

Deploying via RMM Tools

If using an RMM tool with Remote Command Line Access (like ConnectWise Manage, SolarWinds RMM, etc.):

1 Download the MyZen installer to your local computer

2 In your RMM tool, create a command deployment task

3 Use the silent install command (MSI or EXE depending on your installer type)

4 Deploy to your target device(s)

5 Monitor the deployment result and log for any errors

Important: Do Not Rename the Installer

Critical: Do not rename the installer file before executing it. The filename contains your account's unique license token. If you rename it, installation will fail with a license error.

Exit Codes

The installer returns the following exit codes:

  • 0 — Success
  • 1603 — Installation failure (check log file for details)
  • 1618 — Another installation is in progress (wait and retry)
  • 1642 — Invalid transform (MSI syntax error — contact support)

If installation fails with exit code 1603, attach the log file from the command above (%TEMP%\\atinstall.log) when contacting Prodoscore support.

Tip: Test the command on a single machine first before mass deployment. This helps catch any issues before rolling out to 100+ machines.