Skip to content

Deploy Connect to many computers#

Mass deployment is a silent installation of Connect from a deployment tool, script, or remote shell that adds each computer to your team or account during installation. It removes the need to install Connect and sign in manually on each computer, for example when deploying Connect across an office.

Applies to#

  • Hosts running Windows (EXE or MSI installer), macOS (PKG installer), or Linux Alpha (jump-connect package). For supported Linux distributions, see Install Jump Desktop Connect.

Choose how to enroll#

Method Platforms Use it when
Pre-configured installer Windows, macOS Deploying to a team. The Connect Code is embedded in the installer file name.
Standard installer plus a Connect Code Windows, macOS, Linux Alpha Deploying to Linux, when your tool renames installer files, or when Connect is already installed.

For a team, obtain either one in the Teams dashboard under Add Computers. See Add and manage computers. Every computer enrolled this way receives the installer's remote access permissions and Connect Configuration. Attributed installers require a sign-in, so do not use them for mass deployment.

The Teams dashboard displays Connect Codes with spaces, such as 123 456 789. Remove the spaces on the command line: 123456789.

Deploy a pre-configured installer#

  1. In Add Computers, open the installer and copy the Windows (EXE), Windows (MSI), or Mac OS (PKG) link.
  2. Download the file without renaming it; Connect reads the Connect Code from the file name, JumpDesktopConnect.CC<code>.DoNotRename.<ext>. With curl, use -O to preserve the file name.
  3. Install the file silently:

Run the following command from an elevated prompt:

msiexec /i "C:\Deploy\JumpDesktopConnect.CC<code>.DoNotRename.msi" /qn

For the EXE, pass the same option: JumpDesktopConnect.CC<code>.DoNotRename.exe /qn.

sudo installer -pkg "/tmp/JumpDesktopConnect.CC<code>.DoNotRename.pkg" -target /

The host joins the team when the installer finishes.

Deploy with a Connect Code#

Download the EXE or MSI installer and pass the code in CONNECTCODE:

msiexec /i "C:\Deploy\JumpDesktopConnect.msi" /qn CONNECTCODE=123456789
JumpDesktopConnect.exe /qn CONNECTCODE=123456789

Optional installer variables:

Variable Effect
RDPENABLED=true Turns on RDP tunneling. false turns it off.
FLUIDENABLED=true Turns on Fluid. false turns it off.

If Connect 10.12.15 or later is already installed, run JumpConnectCli.exe --connectcode. JumpConnectCli.exe is the command-line version of Connect; it is located in the same folder as JumpConnect.exe (the ConnectPath value under HKEY_LOCAL_MACHINE\SOFTWARE\Jump Desktop\Connect\Shared). It prints Success! when the code is applied. In 64-bit PowerShell:

$connect = (Get-ItemProperty "HKLM:\SOFTWARE\Jump Desktop\Connect\Shared").ConnectPath
$cli = Join-Path (Split-Path $connect) "JumpConnectCli.exe"
& $cli --connectcode 123456789

On older versions, run JumpConnect.exe instead. Because it prints nothing to the console, wait for it to finish:

Start-Process -FilePath $connect -ArgumentList "--connectcode 123456789" -Wait

Download the PKG installer, install it, and then apply the code:

sudo installer -pkg /tmp/JumpDesktopConnect.pkg -target /
"/Applications/Jump Desktop Connect.app/Contents/MacOS/JumpConnect" --connectcode 123456789

Connect prints Success! when the code is applied.

Alpha: not for production use

Jump Desktop Connect for Linux is in alpha and is intended for testing. Do not install it on production systems.

The install script adds the package repository, installs Connect, and applies the code:

curl -fsSL https://jumpdesktop.com/downloads/install.sh | sh -s -- --component connect --connectcode 123456789

The script uses sudo for steps that require root privileges. --component connect prevents the script from prompting.

If Connect is already installed, apply the code directly (no root privileges required):

/usr/libexec/jump/jumpconnect --connectcode 123456789

Set Connect settings from the command line#

Run Connect with --serverconfig NAME=VALUE, repeating the option as needed. For example, to name a host before enrolling it:

Run JumpConnectCli.exe from the Connect installation folder (Connect 10.12.15 or later; see Deploy with a Connect Code). In 64-bit PowerShell:

$connect = (Get-ItemProperty "HKLM:\SOFTWARE\Jump Desktop\Connect\Shared").ConnectPath
$cli = Join-Path (Split-Path $connect) "JumpConnectCli.exe"
& $cli --serverconfig ComputerName=Office-PC-01
& $cli --connectcode 123456789

"/Applications/Jump Desktop Connect.app/Contents/MacOS/JumpConnect" --serverconfig ComputerName=Office-Mac-01
"/Applications/Jump Desktop Connect.app/Contents/MacOS/JumpConnect" --connectcode 123456789

/usr/libexec/jump/jumpconnect --serverconfig ComputerName=Office-Linux-01
/usr/libexec/jump/jumpconnect --connectcode 123456789

Set ComputerName before --connectcode, because the name is sent when the code is applied. To manage team settings centrally, use Connect Configurations.

Result#

The host appears under Computers in the Teams dashboard, or in the account that issued the Connect Code. Connect on the host lists the team or account as a remote access user.

Limitations#

  • Any user with a pre-configured installer link or its Connect Code can add a computer to your team. Revoke an installer in Add Computers when it is no longer needed.
  • On Windows, and with a pre-configured macOS installer, the installation succeeds even if the Connect Code cannot be applied (for example, because the code is invalid or the computer is offline). Verify that each computer was added as described in Result.
  • On macOS, a user at each Mac must grant Connect the Screen Recording, Accessibility, and Remote Desktop (macOS 14 and later) permissions. See Grant macOS permissions to Connect.