![bomgar jump client not installing bomgar jump client not installing](https://www.file.net/img/screenshot/taskman-bomgar-scc-exe.png)
This level of access allows the TSP to begin a Bomgar support session without any involvement by the end user. After unpinning, the mini-client will be automatically uninstalled when the support session ends. The Jump client stays pinned until the TSP "unpins" it. In all other ways, the support session is exactly like the Basic session described above.
#BOMGAR JUMP CLIENT NOT INSTALLING DOWNLOAD#
A TSP with these rights can start a new Bomgar support session with a pinned client without the client needing to download and run the mini-client again. A pinned mini-client is called a Jump client. This level of access allows a TSP to work on a workstation in attended (interactive) mode as described above. It also permits the TSP to request permission to "pin" the mini-client to the user's computer. As the session progresses, each time the TSP requires a different type of access (screen sharing, file transfer, system information, elevation of privileges, etc.) the end user will need to click on a prompt saying that they agree to this access. This is a customer-driven approach that involves the end user in the process of allowing a TSP control of the computer for troubleshooting. Support providers in CIT who are supporting end users outside of CIT will only use this type of access. When the session ends, the mini-client is automatically uninstalled. A "mini-client" is downloaded and run by the end user.
![bomgar jump client not installing bomgar jump client not installing](https://content.spiceworksstatic.com/service.marketplace-api/uploaded_contents/79c7cc071dbe86ff53291914cba9579f.png)
To begin a session, the TSP sends an invitation (via email link or by sending the user to a URL and giving them a Session Key). The end user must be present for the session. IT staff using Bomgar will be granted access privileges appropriate for their role.