KACE K1000 how do you check why a managed install didn't install / failed ?
I recently got into using Managed Installs with KACE where I use them to call a batch file to install a program. I have a couple active ones right now, one for Flash Player 29 (batch file which runs the flash player uninstaller and then the msi) and one for Java 8u172 (batch file which runs a command to uninstall previous version of java and then installs the new one via .msi). I've got them set to push to about 20 machines in our environment and for some reason these push successfully to 5-10 machines and for the rest return a "Not Installed (3 of 3 attempts)" or just plain "Not Installed". Where can I go to check to see what is happening? I looked at the Klogs for a machine but it didn't appear to show anything for the managed installs, and just had regular missing patch info. That said, I pushed the patches on Friday/Sat and it is now Monday so am I just too late at checking the logs, since the logs only have info from today ? Any suggestions or tips for managed installs?
4 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
cbernard
6 years ago
1.https://support.quest.com/kb/114922/troubleshooting-managed-installs
2. https://support.quest.com/kace-systems-management-appliance/kb/133819/reading-the-kagent-log-managed-install - mulimotola 6 years ago
"The Quest KACE One Agent service terminated with the following service-specific error:
The system cannot find the file specified"
Is there a way to see what file it's looking for? Since it IS installing on some machines I'm thinking its not an issue with the package itself. Does KACE download the managed installs somewhere? For example SCCM downloads all deployed packages to a specific directory on the endusers machine. It would be helpful to check to see if the install is actually making it to peoples machines. If not that would explain the file not found thing. Maybe there is something else going unrelated to KACE: machines being turned off or going to sleep or something preventing the K1000 from communicating with them. - winterelegy 6 years ago
debug=all
I find the "KAgent.log" in "C:\ProgramData\Quest\KACE\user" to be helpful - JasonEgg 6 years ago