Skip to main content
Solved

Updating the Jump Client

  • October 14, 2024
  • 4 replies
  • 1370 views
M
Forum|alt.badge.img+1

Is there a command line we can run on machines to prompt them to update the jump client? i.e.: Simulate right clicking on a jump client in the representative console and clicking update? 

 

We just updated our site software, and I am wondering about the best way to slowly rollout the jump client updates. Generally, the process we take would be updating the IT department, the business pilot, then start staging it out to production. We deploy our jump client via the generic .msi install. There are a couple methods that I can think of, but each has their downsides. 

  1. Selecting jump items through the console and clicking “Update”. Downsides: This would take forever to manually do for a few hundred pilot machines
  2. Deploying via the Jump Client Auto Update settings. Downsides: No control over who gets the updates
  3. Deploying via the .msi installer. Downsides: You must uninstall the old version, then install the new version (This resets all of the audit history for that jump client instance ID)

What does everyone else do? Is there a command line I can run on machines to kick off the auto update process to get the best of both worlds? 

Best answer by PhillC

Is there a command line we can run on machines to prompt them to update the jump client? i.e.: Simulate right clicking on a jump client in the representative console and clicking update? 

 

We just updated our site software, and I am wondering about the best way to slowly rollout the jump client updates. Generally, the process we take would be updating the IT department, the business pilot, then start staging it out to production. We deploy our jump client via the generic .msi install. There are a couple methods that I can think of, but each has their downsides. 

  1. Selecting jump items through the console and clicking “Update”. Downsides: This would take forever to manually do for a few hundred pilot machines
  2. Deploying via the Jump Client Auto Update settings. Downsides: No control over who gets the updates
  3. Deploying via the .msi installer. Downsides: You must uninstall the old version, then install the new version (This resets all of the audit history for that jump client instance ID)

What does everyone else do? Is there a command line I can run on machines to kick off the auto update process to get the best of both worlds? 

Hello Mjhall,

Just to confirm, there is no API or Client side command which can be run to trigger an update of a Jump Client.

Generally speaking, from your list, options 2 and 3 is what I’ve seen most customers do. The Jump Clients all need to be updated in order to be operational anyway, and we have an automatic update process which allows this.

Depending on your estate type (most servers vs most desktops), you can plan to do the appliance update and let the auto-upgrade process run during less busy tims or just overnight, and the same goes for the MSI update process, it just needs to be run during less busy times.

      4 replies

      P
      BeyondTrust Employee
      Forum|alt.badge.img+1
      • PhillC
      • BeyondTrust Employee
      • Answer
      • October 15, 2024

      Is there a command line we can run on machines to prompt them to update the jump client? i.e.: Simulate right clicking on a jump client in the representative console and clicking update? 

       

      We just updated our site software, and I am wondering about the best way to slowly rollout the jump client updates. Generally, the process we take would be updating the IT department, the business pilot, then start staging it out to production. We deploy our jump client via the generic .msi install. There are a couple methods that I can think of, but each has their downsides. 

      1. Selecting jump items through the console and clicking “Update”. Downsides: This would take forever to manually do for a few hundred pilot machines
      2. Deploying via the Jump Client Auto Update settings. Downsides: No control over who gets the updates
      3. Deploying via the .msi installer. Downsides: You must uninstall the old version, then install the new version (This resets all of the audit history for that jump client instance ID)

      What does everyone else do? Is there a command line I can run on machines to kick off the auto update process to get the best of both worlds? 

      Hello Mjhall,

      Just to confirm, there is no API or Client side command which can be run to trigger an update of a Jump Client.

      Generally speaking, from your list, options 2 and 3 is what I’ve seen most customers do. The Jump Clients all need to be updated in order to be operational anyway, and we have an automatic update process which allows this.

      Depending on your estate type (most servers vs most desktops), you can plan to do the appliance update and let the auto-upgrade process run during less busy tims or just overnight, and the same goes for the MSI update process, it just needs to be run during less busy times.

        L
        Forum|alt.badge.img+6
        • LeeAtkinson
        • Rising Star
        • October 23, 2024

        For all of my deployments, I let them update automatically. They have to be updated anyway, as PhilC has said, so much more manageable to let them update automatically when it detects the appliance has been updated. I don’t any reason why you wouldn’t want to update them as soon as possible.

        M
        BeyondTrust Employee
        Forum|alt.badge.img
        • MikeM
        • BeyondTrust Employee
        • October 23, 2024

        Hello!

         

        I thought it’s also worth mentioning that there is also an option to prohibit Jump Clients from updating automatically by modifying the ‘Automatic Jump Client Upgrades’ setting within /login → Jump → Jump Clients. Use the radio buttons below to control automatic Jump Client upgrades. You can:

        • Permanently disable Jump Client upgrades.
        • Temporarily enable Jump Client upgrades for the current upgrade cycle.
        • Permanently enable Jump Client upgrades.

         

        When either Temporarily or Permamently Disabled, you then can go into the Access Console and manually upgrade clients. It’s worth keeping in mind however that if the PRA Software has been upgraded, clients will be inaccessible until they have been upgraded - however this is often a good method of controlling the Jump Client upgrades in case an upgrade fails.

         

        For more information, please check PRA Administration: Jump Clients for Endpoint Access.

          T
          • Tina_K
          • Trailblazer
          • April 15, 2025

          Hello! 

          I would like to add a question to this topic. 

          We also have updated our site software and we are using the auto-update feature (number 2). It seems to work mostly fine - but there is an issue with a lot of clients (about 2500) that just won’t update. 
          They appear as “Active [Upgrade pending]” in the console. 

          It is like this for three days now - we increased the number of simultaneous upgrades to 500 clients and gave it more bandwith but I think those clients are just stuck, because the number didn’t change much for the last two days. 

           

          I learned from the Knowledge base (https://beyondtrustcorp.service-now.com/csm?id=kb_article&sys_id=3f2be4d5474e12d0b77b3ddbd36d439d&table=kb_knowledge)

          that the appliance puts a .msi in this path 

          C:\ProgramData\bomgar-au

          and tries to run it with system rights. 

           

          Is there a way to trigger this from remote somehow? Because the clients have the .msi - they just won’t start it. Not all of those clients can be rebootet at any time and the issue with windows locking the services.exe is not the case here.

           

          Any ideas?

           

          Badge Earners

          • BCA: Password Safe
            harshadrhas earned the badge BCA: Password Safe
          • BCA: Endpoint Privilege Management - Windows
            Enrique Gonzalezhas earned the badge BCA: Endpoint Privilege Management - Windows
          • BCA: Remote Support
            Fasi Ur Rehmanhas earned the badge BCA: Remote Support
          • BCA: Password Safe
            vnmkhas earned the badge BCA: Password Safe
          • 1 Courses Completed - Entitle
            AdrianRhas earned the badge 1 Courses Completed - Entitle
          Show all badges
          Terms & ConditionsCookie settingsAccessibility statement