In our environment we use the Kace + Bomgar integration; i.e. kace.bomgar.com and have tied it into a custom script as well as our service desk.  The custom script is great as it will initiate a Bomgar session with a MAC or a PC when no one is present.  

Today I needed to do this and started up Bomgar representative client, which needed to do an update.  The update seems to have redone the GUI; looks great, didn't think much of it.  

When I run my script it seems to error out, which is really odd as we haven't touched it; it worked prior to today.  

Here is the Kace side output of our script:

Output Log

Directory does not exist: c:\PRogram Files
Directory DOES exist: /usr/bin
Archive:  <numbers go here>.zip
creating: Bomgar/
creating: Bomgar/.dmg/
extracting: Bomgar/.dmg/<numbers go here>.dmg
creating: Bomgar/Double-Click To Start Support Session.app/
creating: Bomgar/Double-Click To Start Support Session.app/Contents/
creating: Bomgar/Double-Click To Start Support Session.app/Contents/_CodeSignature/
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/_CodeSignature/CodeDirectory
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/_CodeSignature/CodeSignature
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/_CodeSignature/CodeRequirements
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/_CodeSignature/CodeResources
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/Info.plist
creating: Bomgar/Double-Click To Start Support Session.app/Contents/Resources/
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/Resources/appicon.icns
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/Resources/<numbers go here>
creating: Bomgar/Double-Click To Start Support Session.app/Contents/MacOS/
extracting: Bomgar/Double-Click To Start Support Session.app/Contents/MacOS/mount_dmg_and_exec_bundle.sh
ProcessOps_LaunchProgram: Launch failed: 1 exitCode=126

Status Log

Detecting operating system
Verified /usr/bin folder exists - this is a MAC system

Activity Log

Checking if directory exists: c:\PRogram Files
Checking if directory exists: /usr/bin
Launching program: '/Library/Application Support/Dell/KACE/data//kbots_cache/packages/kbots/695/InitiateBomgarSession.sh' 'https://kace-integration.bomgar.com/api/start_session.ns?customer_id=<numbers go here>' wait='true'

Not a ton of information there, so I started to mess with the files themselves to see if I can figure anything out.  

The way it works is you have an InitiateBomgarSession.sh file that basically downloads and unzips a file.  
Then it executes a shell script within the App that it downloaded.  

Here is the script within the .app

# determine the temp dir

TMPDIR=${TMPDIR:-/tmp}


# move the bundle out to a temporary location since we're going to clean up the wrapper bundle momentarily

orig_dmg=$(ls ../../../.dmg/*.dmg)

dmg=$TMPDIR/$(basename "$orig_dmg")

mv "$orig_dmg" "$dmg"


# mount the image silently

hdiutil attach -quiet -noverify -kernel -noautoopen -nobrowse -mountpoint "$mountpoint" "$dmg"


# find the first bundle in the mountpoint

bundle=$(find "$mountpoint" -maxdepth 1 -name '*.app' | head -n 1)


# bail if bundle wasn't found

test -n "$bundle"


# lookup the bundle's binary (as indicated by the bundle's plist)

bin=$(defaults read "$bundle/Contents/Info" CFBundleExecutable)


# bail if bin wasn't specified in plist

test -n "$bin"


# clean up this ziplock

wrapperBundle=$(cd ../../ && pwd)

topFolder=$(cd ../../.. && pwd)

#   test that we're really running from a ziplock wrapper bundle

if [[ -f "$wrapperBundle/Contents/Resources/69073801-d756-4e93-85ce-76bab30d3aa0" ]]; then

        cd ../../../../

        rm -r "$topFolder"                                       

fi


# execute it with any arguments passed to the bash script

exec "$bundle/Contents/MacOS/$bin" "$@"


When I run the Initiate Manually with the correct URL variable I kept on getting this error:

override r-xr-xr-x  ME/DREXEL\Domain Users for /Users/ME/Desktop/Bomgar/Double-Click To Start Support Session.app/Contents/MacOS/mount_dmg_and_exec_bundle.sh?

I thought this was odd so I started to dig into the script above and found if I kill this "   rm -r "$topFolder"    " everything works well.  

I have confirmed this issue on 10.8.x and 10.9.x clients.  

Anyone else running into this issue?  I have not contacted Bomgar yet regarding this but will.  

Is the override issue = ProcessOps_LaunchProgram: Launch failed: 1 exitCode=126






1 Comment   [ + ] Show Comment

Comments

  • Is anyone else using the free licenses from Bomgar with their Kace box?
Please log in to comment

Answers

1
I think this problem was supposed to be fixed in Bomgar 14.2.3.
Answered 12/03/2014 by: Dietrich
Senior White Belt

  • Do you have any details you can provide?
    • There was a version or two where Safari would download a .dmg version of the Customer Client instead of a .zip version; however, this was fixed in 14.2.3. The problem here appears to be that the *new* zip version isn't structured quite the same way such that rm -r "$topFolder" is no longer required. I think you should check with Bomgar Support to see if they can check this fix and roll it out in an updated script.
  • I'm having this same issue with 14.3.1 (script running on an OSX 10.10.5).
    • Sorry to hear that. When I contacted BomGar (back then) they indicated the hosted version is unsupported so they will not fix the issue despite the fact that the integration document states it works for MAC and PCs. We are moving to an internal Bomgar appliance, so I am looking forward to having this capability restored for our MAC deployment (which is about 80% here).
Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share