KACE Product Support

First note that the latest windows agent for 5.2 server is 5.1.38724 so you should move to that version.

A managed install (MI) can when users are not logged in as well. There are deployment options and the default action is to"execute anytime" including when no one is logged in. MIs will act according to the SYSTEM user. If you want an install to act according to specific credentials then you need a script instead of an MI. If you want an install to act according to the credentials of the currently logged in user then that would also be accomplished via a script and someone would need to be logged in.

Thanks for the quick reply. My experience thus far shows that it does not work. Is this a bug or is there a setting you must select to get it operational? If I do a force check-in with the user logged off it just sits there. Are there certain logs I should look at to trace the issue?

The logs on the client are probably enough as is, but you can add debugging
http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=519&artlang=en

For the logs, try looking at kdeploy.log in the application data folder on the agent PC (XP: under the "all users" profile, Win7: C:\ProgramData\Dell\KACE).
I fat-fingered a switch on the command line of one of the three new MIs I ran last night. I corrected the command, set it to run immediately against a couple of the machines that had failed and forced check-ins for those PCs. The job showed in the "To Install List" on the computer details page, so it was acknowledged but wouldn't run. The KDeploy log showed "Error: KDeploy is already running. Only one instance may be run at a time." I killed that process on the agent PCs and forced another check-in; the job then ran immediately. It appears that the bad msiexec command left the KDeploy stuck in a sort of listening mode.
Klaunch.log may also be of help. For me, it showed Tue Nov 29 22:11:13 2011] KLaunch signal timed out process (4192) to shutdown
[Tue Nov 29 22:11:14 2011] KLaunch force timed out process (4192) to terminate Not super useful in my case, but at least it shows the job started to run. I'm guessing that 4192 was the PID for either msiexec or kdeploy, but I'm only guessing based on the time and the fact that I know what failed.