![]() Customer presence is detected when the Jump Client session starts. The way customer presence is determined is set by the Use screen state to detect Customer Presence Jump Client setting. Otherwise, the Customer Not Present Session Policy applies. The Customer Present Session Policy applies when the end user is determined to be present. Session policies assigned to this Jump Client have the highest priority when setting session permissions. Customer Present Session Policy and Customer Not Present Session PolicyĬhoose session policies to assign to this Jump Client. If no Jump Policy is applied, this Jump Client can be accessed at any time. Jump Policies are configured on the Jump > Jump Policies page and determine the times during which a user can access this Jump Client. You can apply a Jump Policy to this Jump Client. TagĪdding a Tag helps to organize your Jump Clients into categories within the representative console. 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. CommentsĪdd Comments, which can be helpful in searching for and identifying remote computers. This string has a maximum of 128 characters. This name identifies the item in the session tabs. If a session policy is assigned to this public portal, that policy may affect the permissions allowed in sessions started through this item. Select the public portal through which this item should connect for a support session. 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 logged-in admin user with appropriate permissions, 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. Some Mass Deployment Wizard settings allow override, enabling you to use the command line to set parameters that are specific to your deployment, prior to installation. 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 (and higher ranking roles on your team, such as Team Lead and Team Manager if you are a Team Member, and Team Manager if you are a Team Lead) can access this remote computer through this Jump Client. Jump Groupįrom 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. The Mass Deployment Wizard enables administrators and privileged users to deploy Jump Clients to one or more remote computers for later unattended access.įor more information, please see Remote Support Jump Client Guide: Unattended Access to Systems in Any Network. ![]() To access the Jump Client Mass Deployment Wizard, click Add at the top of the Jump Client Installer List. When prompted, copy the Jump Client-specific key to complete the installation. To use the generic Jump Client installer, select your desired platform, and click Download. Generic installers can be used for automated or ephemeral deployments on VM images, and do not require authenticating and downloading the Jump Client or Jumpoint-specific installer once deployed. The generic installer allows you to create Jump Client and Jumpoint installers that are not tied to a specific Jump Client or Jumpoint. Click Dismiss to remove the warning message. In the Representative Console you may use the copy action on a Jump Client to apply different policies to the same endpoint. Administrators and privileged users can view, download, delete, orĪ warning message appears at the top of the list: Installing more than one Jump Client as the same user or more than one Jump Client as a service on the same system is being phased out in a future release. This list shows all previously installed active Jump Client installers. Jump Jump Clients: Manage Settings and Install Jump Clients for Unattended Access ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |