First to mention, Auto Shutdown Manager operates even if no users are logged on to the systems in a so called full background - or service mode. All operations are supported in this mode including power up, power down, restart, standby, updates & patches, deployment and receiving of new settings, Time Rules, remote shutdown, wakeup, reboot etc.
Flexible Operation Modes
The operation modes provided by Auto Shutdown Manager are very flexible.
Depending on the required policies - the system can be configured in a "Can", "Should" or "Must"
shut down mode. Shutdown can be prevented during core business times or while maintenance tasks are going on.
Outside of core times, the idle shutdown timer will start monitoring the PC for productive tasks. If no one can be detected for a specified period of time, the shutdown will be prepared (open documents will be saved etc.) and the PC shut down into a specifed mode such as standby, hibernation or complete power off. The shutdown mode can be defined depending on the time, day of week or date.
This is an example how a day could look like:
RED: The PC won't shut down
GREEN: The PC may shutdown (e.g. Standby), if detected as idle (not productive)
Light Blue: The server starts the PC for maintenance via WOL
Dark Blue: The PC will shutdown
Example: All Systems can be grouped by required policies.
"CAN" - allow shutdown, but respect users
One group of PCs could be configured to be allowed to go into a defined sleep mode
during the lunch hours. This means if no activities are detected during a defined
period of time, the systems would be allowed to go into a defined sleep mode such
So the logical rule for lunch time could be:
- Keep permanent running between 7:30am and 11:45am (core business time)
- Check for user or system activities between 11:45am to 1:15pm - if there are no
activities for at least 10 minutes - go into Standby…
- Wake-Up at 1:15pm (if wanted at all)
- Keep permanent running between 1:15am until 5:00 pm (core business time)
- Check for user or system activities after 5pm - if there are no activities for at least 10
minutes - go into Hibernation…
"SHOULD" - try to shut down at a specified time, but with a warning message and user decision
Another group of PCs could be setup to go into a sleep mode during lunch hours, say
at 12:15 pm regardless other options. In this case the users would get a warning
message notifying them about the planed shutdown. If the users want to continue
their work, they just can disagree and continue their work.
Finally, the idle shutdown timer would shutdown the PCs when the users forgot after
the work was done. And of course, unsaved documents would be automatically saved before.
“MUST”- enforce shut down w/o user interaction
Another group of PCs could be used to display - say - stock prices. This makes only
sense until the market closes plus some extra time for aftermarket deals. So these PCs
could be definitely switched off say at 6pm every day. In this case the shutdown could be
enforced without any user interaction.
Auto Shutdown Manager operates network aware
In Enterprise environments - but also more and more in networked homes - it is core for the
systems to run reliable and also to be available during core business hours or whenever
needed. Furthermore, systems might depend on each other. For example client computers
can’t be operated properly if their servers aren’t available.
To map these requirements, Auto Shutdown Manager was build with a network aware
logic. This means that on one hand client computers can wake up their server on demand and
keep it running as long as required. On the other hand the servers know about clients and
keep up and running until the last client disconnects. Additionally, other IP enabled equipment
can be used to control the idle shutdown decision.