This does not seem like expected behavior. Workarounds?
Technically no one is logged into the system so that is probably why it is triggering. If you were to vnc or something like that using the active sessions it would indicate someone is logged in and wouldn't do the installation.
I suspect it would recognize someone logged on through a remote desktop cosole session. My workaround is to add a check for any running explorer.exe processes in my install scripts.
Sign up today to participate,
stay informed, earn points and establish a reputation for yourself!