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.
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.
Attachments Open full size
"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!
Attachments Open full size
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?
Attachments Open full size
We're looking at improvements to the installers for several areas, including this one.
Attachments Open full size