Running inventory+managed installations completely as part of SDA system deployment


I am having issues getting "runkbot 4 0" followed by a "runkbot 6 0" command to run and fully install all Managed installation software from SMA during SDA deployment. There is a task during SDA that installs the KACE client agent to the computer. After agent is installed, sometimes "runkbot 4 0" is successful and uploads the inventory data to SMA. Other times, the command window flashes onscreen quickly and disappears, not waiting for the "runkbot 4 0" process to fully complete.

The end result is that the computer finishes deployment without any of the managed installation software installed. I would like to have command prompt wait until all managed installation software is installed before SDA deployment is complete. 

The image I am deploying is generic in that I do not want to list specific software that always get installed during SDA deployment, but, rather let SMA install software based on labels through "runkbot 4 0" and "runkbot 6 0" commands before SDA deployment reaches the cleanup step. 

Is there a best practice to accomplish this? 

0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: Nico_K 1 year ago
Red Belt

Rule of thumb:
Never ever run kbots "manually" or as a part of a script.

Best practices are:
install the agent and all scripts which need to be done right now.

Setup a label with new machines
Bind all SMA installs and probably also the update to this label.

Before the MI starts it needs to download all installer files to the client which needs its time. This time blocks the SDA for other tasks.

Yes, you can run the MI/Scripts by running the usual kbots, but this can cause strange side effects as you reported. 

  • Thank you for pointing this out. I was not aware that running kbots "manually" was against best practices. I rather follow best practices and use the Post install tasks to get the apps in the image because I want predictable behavior. Thank you Nico_K and Channeler - Steve2 1 year ago
Posted by: Channeler 1 year ago
Red Belt
that's why the KACE SDA has Post Install tasks, to AVOID relying on the SMA to add\install additional software. Besides, running kbots scripts manually it's against best practices. Also the KACE SDA has a wizard, where if it's able to pull KACE SMA Managed Installs into the KACE SDA Post Install tasks. (Just managed installs, not scripts).

  • Hi there. I wasn't aware that running kbots scripts manually is against best practices. I do not want to break the best practices, so I will use the KACE SDA built-in managed install wizard and have it in the Post Install tasks. Thank you for pointing this out. - Steve2 1 year ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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