Logged In/Out

 

 

Top  Previous  Next

The 'Run event when users are logged in or out' provides another level of control over when your scheduled jobs can run. Below is a table to indicate best use of these options:

 

 


       NO users are logged in ticked. YES/NO

       are logged in ticked. YES/NO

       is logged in ticked. YES/NO

Event can run when NO users are logged in to the computer, or when ANY users are logged (default setting). Basically no restrictions to running events.

                       
 
YES

                       
 
YES

                       
 
NO

Event can run ONLY when NO users are logged in. Useful if you want to ensure that all users have logged out before a job is run.

                       
 
YES

                       
 
NO

                       
 
NO

Event can run ONLY when the SPECIFIED USER is logged in. That user must be logged in for the job to run (note for Terminal Services, other users can be logged in at the same time but job will only run if that SPECIFIED USER is also logged in).

                       
 
 
 
NO

                       
 
 
 
NO

                       
 
 
 
YES

Event can run when SPECIFIED USER is logged in or NO USERS are logged in. (note for Terminal Services, if the specified user is not logged in the event will not run while other users are logged in. Either the specified user has to be logged in or ALL users have to be logged out for the event to run).

                       
 
 
 
 
 
 
YES

                       
 
 
 
 
 
 
NO

                       
 
 
 
 
 
 
YES

Event can run when one or more users are logged in, but wont run if no users are logged in.

                       
 
NO

                       
 
YES

                       
 
NO

 

 

Back to Introduction