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.

39 Vote

Same installer package between versions

The customer does not want to have to re create a new SCCM package every time the Bomgar appliance is updated for new jump client installers.

Customer would like to see the key info field stay the same between versions as it creates a lot of work to rebuild the installer packages after each update

  • Guest
  • Dec 9 2016
  • Under evaluation
  • Attach files
  • Guest commented
    5 Apr, 2019 02:33pm

    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
    24 Aug, 2018 07:15pm

    New application each time is indeed the only problem I have with this application, that and I had to write a script to clean up the old install folders, as each install leaves a folder.

  • Guest commented
    27 Apr, 2018 03:18am

    I can't believe this isn't a bigger complaint. Having to rebuild the install packages every upgrade gets old real quick.