I have a deployment setup that worked on a little over half of the machines it was supposed to deploy to.  My questions are:

1.) Is there a log someplace I can check to see what went wrong?

2.) Is there a way to force the machines to re-deploy after they have reached there max attemtps? (i.e. Not Installed (3 of 3 attempts)


Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment



1) If you right click on My Computer, go to 'Manage'. This will open a new window. Go then to System Tools, Event Viewer, Windows Logs, Application. You might need to search through to find any errors. Of the top of my head you may find there are some pre-requisites need deployed or installed first (e.g. .net 4, visual studio C++ 2010, etc.)

2) If you open a run window, type 'regedit', hit enter. in the registry editor go to HKEY_LOCAL_MACHINE, software, microsoft, windows, current version, group poligy, appmgmt. Anything deployed by MSI is listed here and if you delete the link and restart with 'gpupdate /force /boot' it will try and reinstall the software again.

Answered 05/28/2013 by: alphabeta
Third Degree Brown Belt

Please log in to comment

If I recall correctly, simply saving the managed install again will reset the attempts, but if not, you can just increase the number of attempts to say 4 in your MI.

Find a system that the deployment failed on and enable debug: http://www.kace.com/support/resources/kb/article/how-to-enable-debug-logs-on-the-kace-k1000-client-kbox-client-deployment

Run the deployment and then look in the kdeploy and runkbot logs.  Post here if you need further help.

Answered 05/28/2013 by: jknox
Red Belt

Please log in to comment

I would also check out our recent KKE on Troubleshooting Software Distributions as you may have missed a small step when creating your deployment (like choosing the OS that it can be installed on.)

You can find that session from May 21st and others here:


Answered 05/28/2013 by: andrew_lubchansky
Black Belt

Please log in to comment

Thanks for all the suggestions and the quick responses.   Resetting the attempts was easy enough and enabling debug was exactly what i was looking for.  


Answered 05/28/2013 by: mikeg77
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity