Jump Client shows Installed on some but ...

Are you able to remote in (I know, ironic) and see if it’s actually installed?  Or at the very least, remote powershell in and browse their computer for evidence of an install?

Haven’t tried powershell. Why would the local device “company portal” show installed if it isn’t installed though?

I mean, how does the company portal know if something actually installed?  Does it just execute the EXE, and just assume it worked?  Does it do any checks?  Does it keep any logs you could look through?  Maybe it deployed the EXE, but there are networking complications that prevent the device from hitting the internet?

I think, overall, this is a common line of questioning with any software system that deploys other software.  My advice would be to powershell into one of the “problem” computers and take a peak at the logs to see if you can find anything out of the ordinary.

If you can find an endpoint that says successfully installed in Intune but does not have the jump client installed, attempt a reboot of the device first. I found some don’t launch the process “bomgar-scc.exe” until reboot.

In our case, after using process monitor on a machine that installed successfully (but did not have the client running) we found that the MSI is installing the app and then immediately uninstalling itself. In C:\ProgramData you may be in the same boat if you find folders named bomgar-scc-0x###### with ONLY a “remove.exe” inside.

Currently have a ticket open. Let me know if you’re in the same boat and I can relay what our solution is.

I have that folder with the “remove.exe” on my machine but it is working fine

Sorry about that! I meant to say ONLY a “remove.exe” inside. On a successful install you should have many other files including “bomgar-scc.exe”

Did we validate the JumpClient actually got installed while the JumpClient deployed was valid?
I know screen shot is from PRA, but RS would be similar.

Then for mass deployments, I would always recommend using MSI’s

@Jens Hansen Yes at the time of install the JumpClient was valid and we used the MSI.

@Chris M When I looked at my co-workers machine that shows an “install” but isnt showing up anywhere, they don’t even have a bomgar folder in C:\ProgramData

Can I ask if these machines had a Jump Client installed on them previously? If so, was that installed via the MSI Installer previously?

Overall, the best course of action is to try to deploy the Jump Client again to a known problem machine and ensure the ‘blog.ini’ logging enabling file in placed in the root of C:\. This should then generate a Jump Client installer log we (well, the Support Team) can review to advise why it failed. If you need a copy of the ‘blog.ini’, you’ll need to log a Support Case to get a copy of that.