Skip navigation

New scheduler options are needed to account for devices that sleep (Hibernate).

score 65
You have not voted. Product Team Review
  1. Modern workstations are configured to enter a lower power "Sleep" state while idle.  During this sleep state the operating system, running applications, and system services are effectively suspended.
  2. End users, myself included, rarely logoff of a workstation at the end of the day.  More commonly the user session is simply locked and then unlocked at the start of the next business day.


As a result of these two situations our product scheduling options can be ineffective in some cases.

  • Items scheduled to execute at a specific time of day won't execute if the workstation is asleep (The default inventory updates schedules are frequent victims of this situation)
  • Items scheduled to occur at startup won't execute unless the OS is rebooted.  When the OS wakes up after a low power sleep state, running applications and services are resumed as if the low power state had not occurred. Frequently the only method to detect a low power sleep state is due to a sudden jump in the log time stamps.
  • Items scheduled to occur at Session Startup (user login) won't execute as the user never logged off, they only unlocked a user session that previously had been locked.  Unlocking a user session does not invoke the "At Session Startup" schedule.


To overcome the situation(s) described above, new product functionality related to the scheduler entries shown below would be of great benefit to the community:


To the above list add the additional options of:

  1. "At Resume from Sleep or Hibernate"
    • Similar in functionality to the existing option "At Startup"
    • Causes execution when Client Management service has detected that the Operating System exited a Sleep or Hibernate power state.  This detection method currently exists in the product, but no method exists to invoke a scheduled action based on the event detection.
  2. "At Session Unlock"
    • Similar in functionality to the existing option "At Session Startup"
    • Causes execution when the Client Management server has detected a user session transitioned from an inactive state to an active state.


Vote history