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. In the command above, I'm letting SCCM handle the '/qn' switch. msi KEY_INFO = redacted jc_jump_group = jumpgroup : redacted
#BOMGAR JUMP CLIENT LOGS INSTALL#
How the hell do I remove that product code so msiexec will at least attempt to install the app?
#BOMGAR JUMP CLIENT LOGS 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. 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. It offers an amazing range of features for the price and should be a serious contender for those businesses where security is paramount.So I put together an SCCM deployment for Bomgar jump clients using the app model. It took a while to get to grips with the myriad security policies but, once we were over this hurdle, we found that BomgarCloud for Remote Support wasthe best at putting teamwork into support services. At this point Bomgar will present them with a survey to gauge their satisfaction with the support session, which is a neat touch.
If permitted, users can end support sessions at any time simply by closing the client's message window. Meanwhile, sessions can be recorded, transferred to other representatives or shared with them, and presentations can run to multiple users through screen sharing. The console can have open connections to multiple systems,and we found swapping between them easy. This includes a screen view and access to other tools, including a command shell, Registry editor and power or reboot controls. All remote connections are encrypted with 256-bit AESand the console loads a new tab for the remote system.
#BOMGAR JUMP CLIENT LOGS FULL#
Policy settings control whetherthe remote user must permit the connection request, which can also be set for file transfer, screen sharing and full control. Systems with Jump Clients installed are displayed in the support portal, where support representatives can initiate a remote session by clicking them. Users aren't required to configure the Jump Client, which will only connect to the appliance URL provided when the installation file was created. Custom clients are created from the appliance's admin console and available for all versions of Windows, OS X (including El Capitan) and Linux. At the end of a session, the Jump Client is completely removed from the remote machine, but you can install it permanently if you want to maintain persistent connections to the support console.
0 kommentar(er)
