- #Bomgar create bomgar jump client installer how to
- #Bomgar create bomgar jump client installer .exe
- #Bomgar create bomgar jump client installer install
![bomgar create bomgar jump client installer bomgar create bomgar jump client installer](https://www.itninja.com/uploads/images/63550/p4D9hT.png)
I may actually just stick to the exe, in my testing so far it has proven far more reliable. Trouble is making sure what originally happened here doesn't happen again.
#Bomgar create bomgar jump client installer .exe
exe installer for our evaluation/pilot, clean uninstall at the end, and try the MSI installer again for prod deployment. Interestingly, running the exe installer (there are multiple choices available) works, and then uninstalling afterward removes all trace allowing the MSI to work. I can't for the life of me figure out where that's being stored. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ĭeleting the key(s -there are two that get made actually) does not remove the product code. I'm presuming the MSI has only added an entry in the registry and nothing else (key below), can you manually delete this and then run the installer again? I haven't packaged for a few years so a little rusty.
![bomgar create bomgar jump client installer bomgar create bomgar jump client installer](https://image.slidesharecdn.com/supportingyourremoteclientswithbomgar-111020125548-phpapp02/85/supporting-your-remote-clients-with-bomgar-15-320.jpg)
In the command above, I'm letting SCCM handle the '/qn' switch. msi KEY_INFO = redacted jc_jump_group = jumpgroup : redacted
#Bomgar create bomgar jump client installer install
How the hell do I remove that product code so msiexec will at least attempt to install the app?
#Bomgar create bomgar jump client installer how to
I've been here for 3 hours now trying to figure out how to clear this mess up so I can push the fixed deployment. Running /f through msiexec on this package results in the 'help' window popping up, ditto running the product code through msiexec /x. Now, when I re-run msiexec with the corrected command, I again immediately get a code 0, and the event logs state the application was reconfigured. The original process resulted in code 0, and the MSI product codes were stored as if nothing had gone wrong.
![bomgar create bomgar jump client installer bomgar create bomgar jump client installer](https://www.beyondtrust.com/docs/remote-support/resources/images/admin/ent/jumpoint-installer-4_21-3.png)
The problem now, is I have ~20 pilot machines without a jump client but msiexec-and by extension, SCCM-thinks they do, and so I cannot install. I was able to successfully install the app by removing that duplication. Odd.įast forward to working with a Bomgar engineer and discovering that having "/quiet /qn" at the end of the command for this particular MSI would result in a code 0, but no application installed. Except, there were no jump clients reporting. Overnight, the deployment went off without a hitch, no errors to speak of. What happened next, I have never seen before. I put /quiet at the end of the program string, but I also set User Experience to 'Hidden.' I didn't realize this would set a second /qn switch. So I put together an SCCM deployment for Bomgar jump clients using the app model.