#Bomgar jump client spy software#

#Bomgar jump client spy 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 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 First let me says that we are using a Dell KACE appliance to manage our users along with Active Directory.