- #What is bomgar jump client install#
- #What is bomgar jump client software#
- #What is bomgar jump client windows 7#
- #What is bomgar jump client zip#
If the folder exists it presumes that Bomgar was or is installed and needs to check before continuingģ. Looks for a specific directory in C:\ProgramData\Ģ. Same directory so it is ok if i need to call multiple dependencies or scripts as they will be working from the same local directory, i am also using nested IF statements and labels i can also call a vbscript or another batch file etc.ġ.
#What is bomgar jump client zip#
So far i have written a batch file that does the following, also i am using basic DOS commands, but per Dell KACE i can zip up all files and scripts and KACE will download them all to the I will post my script as soon as i am done with most of it.
Under a different URL now we have an appliance that has a different URL which generates new session ID's different from the old ones. The reason their are other clients out there is we were using a hosted version
#What is bomgar jump client install#
If previous version detected else if it finds current version script will exit otherwise it will continue and install the most current version of the Bomgar Jump client. Need a command to check the registry or something, i need an alternate way to identify if a different version is installed or if the most current version is installed, as i have created a snippet that will perform a silent uninstall Keep in mind users don't have install rights.ģ. Is somewhat dynamic as it uses a dynamic folder, only constant is that the uninstall file is the same just parts of the folder its in are dynamic. If Bomgar is already installed some machines may error out saying "Please uninstall any previous versions of Bomgar before installing this version" being that the unique session ID gets tied to the installed programs list uninstall command
#What is bomgar jump client software#
Name in the installed programs is not consistent as KACE is looking for an exact match to see how many users have the software installed so its confused and just keeps trying to push the software.Ģ.
KACE could / is supposed to accomplish most of the deployment on it's own and if it see's the program in the installed inventory list and it is supposed to skip over the machine and go to the next machine, however Bomgar uses many dynamic links and the i have tested most of the functions and they seem to work, please see below for a description of the problems i have found so far.ġ. Keep in mind i am also writing this for 32-Bit and 64-Bit O/s. My script in word until i am ready to put it all together. I am at odds because either way you look at it their is a problem at every corner, please any feed back or help with my script would be great, right now it is in pieces as i am testing commands individually at the command prompt and writing
#What is bomgar jump client windows 7#
Bomgar also ties its name and folder structure back to a unique session id that is appended to almost everything so i am having to go beyond KACE and use what's built-in to Windows 7 and KACE will be Already tried through KACE directly, but one slight problem the Bomgar package is separated Our concern is deploying software to several hundred remote users. We have our KACE appliance on the internet so we can reach both internal and external users. We are currently trying to deploy our Bomgar Support client to all of our machines, we could use a GPO as suggested by the vendor however Just let me know if you need it.First let me says that we are using a Dell KACE appliance to manage our users along with Active Directory. I can provide you what I have as far as the scripting goes. We have a canned script that our help desk agents will run after they have used the "Jump to" button to install the client on the machine using the process I mentioned at the beginning. Bomgar is really odd with its installer in that it often has to be attempted twice for it to actually work.įor this reason, we don't generally attempt to install on machines already out in the field, we have it installed during the imaging process only. It then attempts to run the MSI install, waits about 15 seconds, and then checks for the uninstall batch again, if its there the batch closes, if it is not, it runs the MSI install again and closes out the batch.Īgain, I know the process is bad, but its the only way I have had any success. I have the batch look for the uninstall batch file, if it's there it runs that uninstall, and then removes the install folder. Basically I run the MSI install starting with a batch file. For the MSI, I have always had to run a very crude install.