Video Screencast Help

Question about managed software delivery and run when no user is logged on.

Created: 31 Jan 2013 • Updated: 01 Feb 2013 | 3 comments
This issue has been solved. See solution.

Just a quick question.  When creating a manged software delivery policy, and choosing to have it only run when no user is logged on.  When will it actually execute the install if compliance check happens when a user is logged in?  Remediation is set to immediatetly.

Say User X is logged in and compliance check happens, determines software needs to be installed, downloads software, and then executes.  Software install then fails because user is logged in.  Does the install happen when user eventually logs off?  Or will it only try to execute again when another compliance check happens?

Comments 3 CommentsJump to latest comment

andykn101's picture

I think the job will show in the agent as running once the complince check runs and detects that the remediation should run and downloads the package but won't run until you log out. It's best to test with a dummy as agent behaviour can change between versions.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

mclemson's picture

Assign it to a test computer and check logs.  You can use the log viewer by running regsvr32 "C:\Program Files\Altiris\Altiris Agent\AeXAgentDiagnostics.dll" from a command prompt.  Then right-click the agent in the system tray and select Diagnostics > Log Viewer.  Update policy then run the policy (if it doesn't run itself).  Watch the logs--it'll probably state something like:

Policy <name of Managed Software Delivery>({GUID}) has no valid future scheduled run time (other than logon or startup schedules).
Once you log off or reboot, the condition for "No user logged on" will be met and it will remediate according to the schedule you defined.  If you use a scheduled time in the past (e.g. 00:00 yesterday) when you create the Compliance and Remediation schedules, the compliance check will run as soon as a logged on user is present, and remediation will happen after the compliance check as soon as no user is logged on.  The agent monitors for logon or startup events; if it detects a change, it checks its job index to see if anything is pending that would now be satisfied by the new logon state.
Does this answer your question?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner

Eunox's picture

So looks like if I ever started the policy from within the agent.  The execute task would fail and then nothing would run until next compliance check was scheduled.  Last Status under execute command would just say failed.

If I just let the policy run on it's own, execute status would remain with a last status of "In Process".  And once I logged off or rebooted it worked fine.

Thanks for the trick to get the log viewer on the agent itself.