Install a Jump Client on a Mac System

You can override certain installation parameters specific to your needs. These parameters can be specified using a systems administration tool or the command line interface. When you mark specific installation options for override during installation, you can use the following optional parameters to modify the Jump Client installer for individual installations. Note that if a parameter is passed on the command line but not marked for override in the /login administrative interface, the installation fails. If the installation fails, view the operating system event log for installation errors.

It is common to receive an error message during the install, regarding a layout or appearance issue. This can be disregarded.

Command Line Parameter Value Description
--jc-name <name...> If override is allowed, this command line parameter sets the Jump Client's name.
--jc-jump-group

user:<username>
jumpgroup:<jumpgroup-code-name>

If override is allowed, this command line parameter overrides the Jump Group specified in the Mass Deployment Wizard.

--jc-public-site-address <public-site-address-hostname>

If override is allowed, this command line parameter associates the Jump Client with the public portal which has the given host name as a site address. If no public portal has the given host name as a site address, then the Jump Client reverts to using the default public site.

--jc-session-policy-present <session-policy-code-name>

If override is allowed, this command line parameter sets the Jump Client's session policy that controls the permission policy during a support session if the customer is present at the console.

--jc-session-policy-not-present <session-policy-code-name>

If override is allowed, this command line parameter sets the Jump Client's session policy that controls the permission policy during a support session if the customer is not present at the console.

--jc-jump-policy <jump-policy-code-name>

If override is allowed, this command line parameter sets the Jump Policy that controls how users are allowed to Jump to the Jump Client.

--jc-tag <tag-name>

If override is allowed, this command line parameter sets the Jump Client's tag.

--jc-comments <comments ... >

If override is allowed, this command line parameter sets the Jump Client's comments.

--silent  

If included, the installer shows no windows, spinners, errors, or other visible alerts.

If --silent is selected, sudo must be used, otherwise the installation will fail as a prompt during installation does not display.

A Jump Client can also be installed in service mode.

Jump Client Mass Deployment Wizard

Option to download the Jump Client Mass Deployment Wizard, with MacOS (for Programmatic Installation) selected.

For mass deployment, you can download the programmatic installation, mount the .dmg file, and run the commands from there. The programmatic installation is not notarized, but better suited for installation using MDM tools.

Uninstall a Jump Client

To uninstall a Jump Client, remove it from the Representative Console.

If the client is not connected when it is removed from the console, the files are removed next time the client authorizes with the server.

Jump Clients can be removed from a device using a script. This will leave an entry in the Representative Console interface. The entry is automatically marked uninstalled or deleted, depending on your Jump Client Settings.

For information about Jump Client settings, please see Configure Jump Client Settings.