![]() ![]() ![]() This option does not apply to headless Linux Jump Clients or Raspberry Pi Jump Clients. In contrast, a Jump Client pinned in service mode, with elevated rights, allows that system to always be available, regardless of which user is logged in. This option applies only to Windows and Mac operating systems.Ī Jump Client pinned in user mode is available only when that user is logged in. If the elevated installation attempt is unsuccessful or if this option is deselected, the installer runs with user rights, installing the Jump Client as an application. If Attempt an Elevated Install if the Client Supports It is selected, the installer attempts to run with administrative rights, installing the Jump Client as a system service.A user cannot remove a Jump Client unless the user is given appropriate permissions by their admin from the /login interface. It can also be uninstalled, or extended, from the Jump Client Installer List. Once a Jump Client has been installed, it remains online and active until it is uninstalled from the local system either by a user from the Jump interface or by an uninstall script. This time does NOT affect how long the Jump Client remains active. The validity time can be set for anywhere from 10 minutes to 1 year. Additionally, if the installer is run within the allotted time but the Jump Client is unable to connect to the B Series Appliance within that time, the Jump Client uninstalls, and a new installer must be deployed. If someone should attempt to run the Jump Client installer after this time, installation fails, and a new Jump Client installer must be created. Be sure to leave adequate time for installation. The installer remains usable only as long as specified by the This Installer is Valid For dropdown.Note that all Jump Clients deployed via this installer have the same comments set initially, unless you check Allow Override During Installation and use the available parameters to modify the installer for individual installations. Add Comments, which can be helpful in searching for and identifying remote computers.The Jump Clients must be installed on the same network as the Jumpoint selected to proxy the connections. That way, if these Jump Clients are installed on computers without native internet connections, they can use the Jumpoint to connect back to your B Series Appliance. If you have one or more Jumpoints set up as proxies, you can select a Jumpoint to proxy these Jump Client connections.An active Jump Client maintains a persistent connection to the B Series Appliance, while a passive Jump Client instead listens for connection requests. Set the Connection Type to Active or Passive for the Jump Clients being deployed.A session policy assigned to this Jump Client has the highest priority when setting session permissions. Session policies are configured on the Users & Security > Session Policies page. You may choose a Session Policy to assign to this Jump Client.If no Jump Policy is applied, this Jump Client can be accessed without restriction. A Jump Policy can also send a notification when it is accessed or can require approval to be accessed. Jump Policies are configured on the Jump > Jump Policies page and determine the times during which a user can access this Jump Client. You may apply a Jump Policy to this Jump Client.Pinning to a shared Jump Group makes this Jump Client available to all members of that Jump Group. Pinning to your personal list of Jump Items means that only you can access this remote computer through this Jump Client. From the Jump Group dropdown, select whether to pin the Jump Client to your personal list of Jump Items or to a Jump Group shared by other users.At the top of the Jump Client Installer List, click Add.From the /login administrative interface, go to Jump > Jump Clients.Administrators and privileged users can view, download, delete, or extend Jump Client installers. This list shows all previously installed active Jump Client installers. You can easily manage active installers from the Jump Client Installer list. This allows you to create custom mass deployment scripts to pull in variables from other sources and use the variables to modify the Jump Client parameters at install time. The Jump Client command line installer has switches that allow a script to modify a variety of Jump Client parameters when executed. You can easily automate the mass deployment of your Jump Client network by allowing customization during installation. ![]() This method of installation may be applied to one system or multiple systems simultaneously. Jump Clients can be preinstalled on remote computers in anticipation of the need for remote access. ![]() Deploy Jump Clients from the Administrative Interface ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |