sorry for the double-post but that problem fits better here:


we get the following behaviour on several machines (XPSP3):

Agent Version on those machines is 5.1.31821

We´ve configured a Software Distribution for several machines. The installation is planned for "Execute after logon (before desktop loads)". Furthermore we configured a pre-install message. The distribution is listed on the "To install list" in the inventory. We´ve forced an inventory update to update the client.
When we restart the machine, the window "Kbox checks your system configuration" before the logon screen appears. When the user logged in, that screen appears again but no pre-install message comes up an no installation takes place.
The desktop is gonna be loaded immediately. I already enabled the debugging on a machine, but I could not find anything. Attached the logs on the machine.

A reinstallation of the kbox-agent did not solve the problem. I checked the network configuration and I can say that there are no network interrupts while logging on the machine.

I also installed the most current agent version, but there is the same behaviour. There must be something wrong.

Especially because of the fact that it worked before.....

Any ideas or did anyone experience the same problem?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Have you tested the installation on a computer which is logon for some time (few hours). If distribution is working on that PC then you should remove the pre-install message and then try it as 'Execute after logon'
Answered 08/25/2011 by: afzal
Fourth Degree Green Belt

Please log in to comment

I already tried to remove the preinstall message, but it does not work. I get the windows "KBOX checks your confguration for updates" before and after logon, so I think it "wants" to execute the task. But somehow it does not do it or maybe the agent itself runs in an error when it tries to execute the command....
Answered 08/25/2011 by: jimbeam128
Yellow Belt

Please log in to comment
This looks like a support call, but otherwise I would definitely be using agent 5.1.38724 if on 5.1
Answered 08/25/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
I cannot do it either but I have found this that I'm gonna test when I get some time, we are running Trend Micro Officescan but I guess other virus scanners have something simular:

Answered 08/26/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment