Post Install Tasks seem to be clashing and causing failures
I've had a lot of failed post install tasks, and based on return codes a consistent issue seems to be that installers are trying to run at the same time.
I know on the K1000, there is a function in scripting that asks to wait for this task to finish before moving onto the next, is there any way to do this with SDA Post Install tasks? Thank you for your time!
Answers (2)
Top Answer
iNSTALLERS ON THE SDA would not run at the same time. The tasks are sequential as you can tell from the task list.
An install task should not start until the previous setup is complete.
What software is getting the error codes and what type of codes are you getting?
Comments:
-
One in particular is Carbon Black Protect, it has recently given me a return error code of 1618, which according to a KB article on their site, refers to "Sensor upgrade/install is running at the same time as another installation."
I've moved installs around in the task order to resolve this in the past with other installations, but this one continues to be a problem. The good news is that just re-running the task seems to solve the issue, but after imaging enough devices it does become a bit annoying. - tpiantanida 3 years ago-
Carbon black is a very "paranoiac" AV that relies on a lot of libraries and services in order to function.
If removing that one task from the list, prevents the error from happening, you would have narrowed it down the issue.
See:
https://support.quest.com/kb/131472/what-order-should-i-place-my-post-install-tasks- - Channeler 3 years ago -
Have you tried to google other suggestions and scripts to deploy carbon black. Maybe a few tweeks to the code should fix it. Check these out.
https://community.carbonblack.com/t5/Knowledge-Base/App-Control-How-to-Script-the-Agent-Installation/ta-p/91510
https://community.carbonblack.com/t5/Knowledge-Base/Cb-Protection-Silent-Install-with-PowerShell/ta-p/44405 - akmagnum 3 years ago
One nuisance I've ran into the past is with application auto-updaters trying to run a MSI installer update package as other things were installing.
There are a couple of ways I've addressed this.
- For packages like Google Chrome, use a deployment script that downloads and installs the most current version of the package.
- For packages that install micro-updates after installation, If the update process can be invoked via command line or a scheduled task, include that in the install script. If the update process can't be forced, add a blind wait of a few minutes to the end of the installer script.
- For packages that will pull down additional software pieces or sensors (like SolarWinds Orion) give the installer script a wait of a couple of minutes to allow for this.
- Do not install the KACE agent until near the end of the post-install tasks as to avoid any Managed Installs conflicting with post-install tasks.
