The appliance will attempt to auto update the clients for you, but often fails to do so. With every software update to the appliance, you also have to update the client on the local machines. ALWAYS use the command line switch to specify an install directory. If you do not specify a folder, you can actually end up with multiple client installs on a single machine, each of which consume one a client connection. This was ultimately what led me down the 6 month road of wrangling with bomgar support. If you reach that client max, you will start to have performance issues with your bomgar appliance. To complicate matters, you pay for a maximum client connection count with your licensing. NEVER use the msi installer, always use the exe installer.Īs others have said, the client installs to a random folder unless you specify the install directory in the command line for the installer. This makes accurate reporting in your environment impossible, and SCCM deployments will give tons of false positives where it shows as installed but actually isn't.
If you use the msi installer this means that the client will be deleted from the machine, but the msi database on the local machine will still show that the client as installed. A few key points from my experience:īomgar clearly designed this product with the intention that there should not be permanent clients installed on the machine, but then they were probably forced to do that by their customers, and just hacked their temporary client to be permanent.Īs as result, if you install a permanent client on the machine, the bomgar appliance can and will still delete the client from the machine. I banged my head on the wall with bomgar support for upwards of 6 months on their client. There's a few really weird quirks with this software. If anyone runs into this and is curious how I handled the uninstall using the PSADT, this is how I did it. Opening it reveals that the bat executes the bomgar-scc.exe from the very same folder with these parameters: -uninstall silentThat does the trick. In that folder, there is a uninstall.bat. NOTE: the installDir changes after every reinstall for some stupid reason, it's never the same. Looking in the registry with a powershell command (Get-InstalledApplication "jump client"), this command is from the PowerShell App Deployment Toolkit, you can get the install Location for the Jump client. On the vendor's website there is no information about a silent uninstall, only install. The vendor offers an MSI for this, but you might have a case where you need to achieve something and you need the EXE for that (2 jump groups for instance - the MSI is unable to do that).įound this post, however, this doesn't work, or no longer works.
0 kommentar(er)
