#Bomgar jump client documentation install#
#Bomgar jump client documentation windows#

The end user must be present for the session. The entry is automatically marked uninstalled or deleted, depending on your Jump Client Settings.Р”Р‡or information about Jump Client settings, please see Configure Jump Client Settings.IT staff using Bomgar will be granted access privileges appropriate for their role. This will leave an entry in the Representative Console interface. Jump Clients can be removed from a device using a script. 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. To uninstall a Jump Client, remove it from the Representative Console.

/quiet is used for the MSI version in place of -silent in the EXE version.Р”Р„ Jump Client can also be installed in service mode.

installdir has a dash in the EXE version (-install-dir) but no dashes in the MSI version (installdir).

Add a space between the parameter and the value instead of an equal signР”В®XE Example: bomgar-scc-.exe -jc-jump-group jumpgroup:servers -jc-tag servers.

When deploying an EXE installer, the above parameters can be specified by: MSI Example: msiexec /i bomgar-scc-win32.msi KEY_INFO=w0dc3056g7ff8d1j68ee6wi6dhwzfefggyezh7c40jc90 jc_jump_group=jumpgroup:server_support jc_tag=servers

Assigning a value using an equal sign (=).Converting remaining dashes to underscores (_).

#Bomgar jump client documentation windows#

When deploying an MSI installer on Windows using an msiexec command, the above parameters can be specified by: If -silent is selected, run as Administrator must be used, otherwise the installation will fail as a prompt during installation does not display. If included, the installer shows no windows, spinners, errors, or other visible alerts. If override is allowed, this command line parameter sets the Jump Client's comments. If override is allowed, this command line parameter sets the Jump Client's tag. If override is allowed, this command line parameter sets the Jump Policy that controls how users are allowed to Jump to the Jump Client. 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.

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. If no public portal has the given host name as a site address, then the Jump Client reverts to using the default public site. 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 override is allowed, this command line parameter overrides the Jump Group specified in the Mass Deployment Wizard. If override is allowed, this command line parameter sets the Jump Client's name.

#Bomgar jump client documentation install#

When defining a custom install directory, ensure that the directory you are creating does not already exist and is in a location that can be written to. Specifies a new writable directory under which to install the Jump Client. It is common to receive an error message during the install, regarding a layout or appearance issue. If the installation fails, view the operating system event log for installation errors. Note that if a parameter is passed on the command line but not marked for override in the /login administrative interface, the installation fails. 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. Installation parameters can be specified for both the MSI and the EXE installers using a systems administration tool or the command line interface. Install a Jump Client on a Windows System