Scripting Question

Best way to update/deploy new Mac agent?

03/09/2015 2537 views
We will be upgrading our K1000 to 6.2 shortly and I've built a Mac OS installer package that deletes earlier K-agent versions and installs the new one with an amp.conf file that points to our server. I've also managed to create a custom inventory item that queries the plist I found in /var/db/receipts. This is a fairly basic question, but I'd like to know what the best way is to get this out to our Macs? 

runkbot 5 0 would have been a lot easier, but it looks like it's Windows-only. Is there something equally simple I'm missing or do I need to go ahead and build a scripted or managed install to push this out like any other app?

Answer Summary:
2 Comments   [ + ] Show comments


  • We tried this when we went from 5.4 to 5.5, but still have just over 100 Macs that seem to be stuck at 5.4. Our tests with a 6.2 server is showing that this is still a problem with clients not updating.
  • SMal, jknox,
    Thanks! This actually worked better in the 6.2 update than it did with previous upgrades. Nearly all our Macs responded to the advertisement. I built a fairly nice customized install package (all humility aside), but it wasn't needed. It will serve as a good standalone installer.

All Answers

I just use the built in update in provisioning and have had great success with it for both windows and macs

Answered 03/10/2015 by: SMal.tmcc
Red Belt

SMal is correct.  The recommended way is to use the built in update process.  However, you can update manually from terminal on a client machine using: sudo /Library/Application\ Support/Dell/KACE/bin/runkbot 7 0
Answered 03/12/2015 by: jknox
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ