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. 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.į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.
BOMGAR JUMP CLIENT 13.1.3 INSTALL
* An action is automatically added to the History tab in the Incident form.ĭiscussion between the Service Desk technician and the user during the Bomgar session via chat and file transfer.Īt the end of the Bomgar session, session data is sent to the technical support agent by email. * If Java is not installed or does not work on the workstation, users may be required to download and run an executable file for the session duration. The Bomgar session is initialized by the user, who enters the session key in the Bomgar portal, usually accessible via the portal or the corporate portal, or via the copy of the launch URL in a Web browser. The Service Desk technician sends the Bomgar session key or URL to launch the Bomgar session to the user, usually by email to avoid data entry errors. * The Bomgar console generates a session key and a URL for starting the Bomgar session and displays this information to the technician in a pop-up. Service Desk technicians request a Bomgar remote support session to access the user workstation via, for example, a hyperlink inserted in the Quick Call or the opened incident form. In, a new incident is created or an existing incident is reopened by the Service Desk. This may include URL links to the Bomgar console with the content of the discussion via a chat with the files exchanged during the session.Ĭall from a user to the Service Desk to report an incident. For incidents, all information is stored in the form at the end of the session.see Different remote support configurations A Bomgar session can be opened from any form (e.g.You can use this integration for both remote support during sessions with a user and during sessions with Jump Clients. It enables Service Desk technicians to perform an accurate diagnosis or to access a user workstation through a remote connection in order to solve IT-related problems or to provide assistance in performing tasks.
Integration Summaryīomgar is a secure remote support solution that allows remote access to workstations, servers, point-of-sale systems or mobile devices.
BOMGAR JUMP CLIENT 13.1.3 PROFESSIONAL
scripts to be used), please contact the Consulting & Professional Services team, the Support team, or your service provider and integrator. To find out more about this integration (e.g. This document describes an integration process that has already been implemented in a customer context. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service. You can integrate third-party systems with in many ways.
0 kommentar(er)
