KACE Product Support

I usually set my MIs to "execute while user is logged in". That ensures that a user is logged in to receive my pre-install message (otherwise the MI fails) but it doesn't prevent them from working.

Casey

In my case I'm trying to install the Plug-in version of Adobe Flash, and it will fail if Firefox is running, so I need to install it when I'm sure no one is logged in. (it is an MSI package and will install successfully with no user logged in).

What if you used a batch file in your MI and had it close firefox (if open) as the first thing?

There is also an option to execute while user logged off.

Casey

What exact version of the K1000 server software and Agent was used in your testing?
Also what was the OS of the client?

This happens on all client OS editions (XP, Vista, 7).

We are running server version v5.3.47927, agent version 5.3.47657.

I reported this to tech support and they said this is by design: "The managed install action of "Execute before logon" is functioning the way it's been program [sic] too. The information that is within "()" might not be wrong, but maybe a little misleading."

If someone would explain why they chose to do it this way I would appreciate it.

Did you also check the box to be able to run without anyone logged in? In our web ui, that check box is down 2 or 3 boxes from the "Execute before Login" box.

zookdj, do you still have a 5.1 test bed?

FWIW, It could be that 5.3 and 5.1 have a difference of behaviour here. I don't know off the top of my head. But with the port that we did from .net there can be differences. If you can demonstrate a difference from what 5.1 did to what 5.3 now does then that would carry a lot of weight.

If you do see a difference then please reopen your ticket. If you do not then we're talking about an enhancement. Regardless of what the option says changing the behaviour of it would not be a trivial change. Maybe in that case we're looking at a possible additional option to achieve your desired result.

RE: "Execute before Login" checkbox, that option does not appear to be available for managed installs. I did see something similar for scripts though.

RE: 5.1 test bed, we don't have one, so I can't compare the two. If memory serves, this has been a problem since day one.

Question: how in the world does the agent know when ctl+alt+del is pressed, and why does it wait until then?

I just heard back from support that this issues is a bug. When an MI is set to install at bootup, it should install before the user gets a chance to press Ctrl+Alt+Del. This statement is true on XP clients. However, Windows 7 clients act different - for some reason. With 5.3 and later, the user selects Ctrl+Alt+Del to login but then KACE kicks in and installs all MI's that are set to install at bootup.

Statement from support: I have been able to confirm your report as a known issue documented as number AGENT-1142. 

Thanks,

Dave