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? No problem, you can still share your ideas with us. You can also 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.


32 VOTE

Generic customer client that can be permanently installed on clients

Bomgar Client or Bomgar button should be permanently installed on clients with no need for extraction in temp folder.

For customers with restrictive security policies like app white listing it is forbidden to dynamically run software from any directory. So Bomgar Client should be able to be installed permanently into a specified directory.

  • Maxim Kushnir
  • Feb 27 2018
  • Future consideration
Submitter Name Maxim Kushnir
Bomgar Version 16.1
  • Attach files
  • Helmut Funk commented
    16 Apr 08:18

    A generic Bomgar client, that can be used for attended connections, without the need to replace it with each Bomgar update (only major ones)  would help us a lot. The higher the security requirements of our HealthCare customers become, the more we need such a generic Bomgar client. The percentage of our customers that is not allowed to download any software grows month by month. Actually this missing piece prevents us to fully move to Bomgar for remote support.

  • Jeff Roback commented
    07 Jun 00:32

    I'm not sure if this is realistic... when the version changes there is going to be new code, so the hash of the binary will change, so I'm not sure this avoidable unless you just don't upgrade Bomgar.  And given the march forward of windows 10 updates, I'm not sure that'd be possible either.

  • Eric Wünsche commented
    18 Jul 10:16

    Hi, this is very interesting for us! Additionally to the permanent installation it is more important to have an automation possibility (e.g. provide session key as parameter).

    The following Idea was actually more precise about this issue, but is marked as already exists:

    https://ideas.bomgar.com/ideas/A01-I-1746

  • Helmut Funk commented
    28 Aug 08:51

    A "Pre-installed customer remote support client" is no option for us neither, since we can not deploy Bomgar clients in our customer environments(Hospitals) on each PC. We have permanent connections to the servers and have to check user PC's only on occasion.

    Anyway we need a generic client, or at least the option to generate session keys which are valid for 3 month, instead of 4 weeks.

  • Admin
    Jonas Outlaw commented
    26 Oct 20:17

    Have you tried using the install directory parameter for Bomgar Buttons? 

    https://www.bomgar.com/docs/remote-support/getting-started/admin/bomgar-button.htm


    If this parameter is used, it should let you define where the Bomgar Button is installed. When sessions are started, a temporary directory is created within that defined directory instead of the Windows temp directory.



  • Eric Wünsche commented
    26 Oct 20:47

     Hi Jonas, the directory parameter won't solve our situation, as this will still create an executable with a generated session identifier in its name, am I right? So, no whitelisting of the filename/location is possible.

    Additionally, writing to Program Files Directory (where the permanent client should reside) is also prohibited in the user context - therefore no extracting/copying into there is possible.

    The extraction to and running from the temp folder is actually okay, but we would still need the permanent part of the client. -This could potentially be the Bomgar Button, but it is lacking the feature of being triggered with parameters (e.g. session key to join). If this was possible, we could deploy the Bomgar Button to the clients and use a custom protocol handler to start it with a given session key.

    In this way the (internal)customer would only have to do one click on a URL and everything will be established without dealing with various browser and download issues.

  • Eric Wünsche commented
    11 Dec 10:02

    Hello we would also need such permanent client in a deployable way for Mac and Linux with the same automation possibilities.