Skip to main content

I’m in the process of re-doing some Jump Client installers (previously team configured it all) and I’ve got some questions burning a hole in my brain.

  1. What are the primary benefits / drawbacks of using a Windows MSI vs EXE installer for persistent connections? In my testing, I’ve had far more install success with EXE’s than MSI’s in Configuration Manager deployments.
  2. Are the Jump Client installers tied to the user that created it in any way? We seem to run into weird issues with clients failing to install when the user that created it has left the organization. As a result, a BT support rep suggested creating the Jump Clients as the local admin.
  3. Is there any way, whatsoever, to view/edit all the settings created for a Jump Client after hitting Create? All I can see is Delete/Extend/Download.
  4. Do you have any reasons for using installation Overrides in your organization?
  5. Do you have any other useful nuggets of wisdom around Jump Client installers?

Again, I’ve gone through all the documentation and BT University, but there are still some big knowledge gaps I have. Any help would be greatly appreciated.

We have a big effort ahead of us to remove expired/dead Jump Clients (see #2) and install new ones.

  1. I can’t talk much on the intricacies of each, but we haven’t had issues using the .msi installer
  2. Yes - Could be related to the issues you were experiencing with MSI. In my scenario I had created the jump client installer, then revoked permissions for that user, and the jump client would then install on the endpoint > connect to the appliance > see the user who made the jump client no longer has permissions to create jump clients > auto-uninstall
  3. Not to my knowledge. Maybe you could do this with the API?
  4. We don’t do overrides during the installation, but I have heard others adding specific info to the name/comments so you can more easily search in the representative console. We use the API to update the comment field after installation to contain who the computer is assigned to, their department, the computer model, etc.
  5. I don’t believe this is supported, but we change the service start mode to be “auto” instead of delayed. This makes the jump client show online much quicker in the representative console

Removing expired/dead jump clients - You probably know this but thought I’d mention just in case - you could lower your setting “Number of days before Jump Clients that have not connected are automatically deleted”. Some code examples might also help cleaning up duplicate records if you run into that - Easy way to find and remove duplicate clients in Admin console. | Community

Reply


Badge Earners

  • BCA: Password Safe
    SFAhas earned the badge BCA: Password Safe
  • BCIE: Endpoint Privilege Management - Windows
    Abuhas earned the badge BCIE: Endpoint Privilege Management - Windows
  • BCIE: Password Safe
    Abuhas earned the badge BCIE: Password Safe
  • BCIE: Password Safe
    Charulatha Shas earned the badge BCIE: Password Safe
  • BCA: Privileged Remote Access
    Peruhas earned the badge BCA: Privileged Remote Access
Show all badges
Terms & ConditionsCookie settings