Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.


10 Vote

Update old Jump Client installation files AFTER install

In bomgar jump client installation files can be downloaded from bomgar when deploying jump clients to system. After bomgar application update, installation files are expired and cannot be used for installation.

This is causing lot of problems when using miradore to deploy. Packages must be regenerated every time when update.

We would be very pleased if you could investigate is there any way to change this behavior. It should be like button installation where old installation files can be used and button updates it self when starting.

  • Guest
  • Aug 17 2016
  • Unlikely to implement
  • Attach files
  • Guest commented
    5 Apr, 2019 02:26pm

    Installed Jump Clients receive a token from the appliance, which allows them to still communicate and self update after an appliance update. Why can't the same token concept be baked into a Jump Client installer (.MSI or .EXE) when initially created? That would solve the issue and save everyone a lot of time from having to remake images and rebuild packages simply to accommodate a new Jump Client installer every single time the appliance runs an update. 

  • Guest commented
    1 Jun, 2018 07:55pm

    "Having a system where it is possible to use an existing jump client MSI, and then have that client update itself after install..." Exactly what Chris said!

  • Guest commented
    8 May, 2018 01:57pm

    I've just had a support chat session with Bomgar asking why our Jump Client MSI expires in the event of an appliance update.  This is causing lots of extra work in updating our software deployment packages and scripts for the jump client in our environment whenever we update the appliance.  Having a system where it is possible to use an existing jump client MSI, and then have that client update itself after install would be much better.  When will this feature be available?

  • Guest commented
    17 Aug, 2016 10:34pm

    We're looking at improvements to the installers for several areas, including this one.