AutoShutdownManager 2.2

AutoShutdownManager is a professional management tool that helps reducing the power consumption of Laptops, tablets, PCs and servers running Microsoft Windows 2000, 2003, XP, Vista, Microsoft Server 2003 and 2008 (32/64Bit) and ready for Windows 7 - by bringing the machines down in a controlled and managed way. On the other hand it can help to maximize security following the principle: machines that are down can’t be attacked.
Its interactive interface allows users and administrators to easily setup and configure basic settings and tune the functionality in all details later on demand.
Its functionality was build under the objective of high machine’s stability and less resource consumption for its own operation. To allow execution on remote servers, there is no need for user interaction at any time during runtime.
AutoShutdownManager was architected to fit into most users’ scenarios – including local and remote resources.
There are several examples where AutoShutdownManager can effectively help to safe hardware and energy resources– and so money at the end.
Here are some typical examples why machines are unnecessarily kept powered-On :
*
TV Recording – machines run for days and nights to be available for recording
*
Burning of CDs or DVDs
*
Long internet downloads
*
Disk defragmentation
*
Backup operations
*
Archiving over night
*
Server based multimedia access – servers keep running after the “show”
*
Users just often forget to power off machines
*
Users just log-off instead of shut down
*
Servers keep running even last client was logged-off
*
There are more very good reasons why many PCs and servers are running – sometimes even 24 hours x 7 days
The key objective of AutoShutdownManager is to offer the same functionality and comfort by reducing useless energy consumption.
The supported environment can be as easy as just one PC - up to a fairly complex networked home or company setup.
Key product features:
*
Password protected and encrypted user settings
*
Network ready
*
Full background execution w/o any user interaction
*
Protocol writer for up/down time analysis
*
Kids protection – allow defined maximum time per day and the latest hour the PC can be used. Use “Smilies” to motivate or “punish” kids
*
German and US language versions
*
External applications can be executed before shutdown or after startup
*
VMWare handling– virtual machines can be added, deleted, suspended before shutdown and automatically restarted after startup
*
Warning splash screen and sound before shutdown
*
Fully configurable shutdown prevention – such as :
o
CPU utilization
o
Hard disk utilization
o
IP-Clients: Clients that are reachable via TCP/IP can be setup to prevent server's shutdown as long as they are reachable. Possible modes are Ping, Auto-mode, Client/Server to cover most possible setups such as set-top boxes, networked PCs and all other IP enabled equipment.
o
Applications: Running applications like PowerPoint in presentation mode, DVR, TV Software, Backup-Software, etc. can be selected to prevent shutdown while running
o
Advanced performance counters: – APCs are used to configure more complex situations such as monitoring of IO throughput of specific tasks, processor utilization by specific tasks etc. A good example to use APC is e.g. DVD burning - and all other software - that stays opened even the job is done. In this case the APC can be used to monitor activities behind the scene, like IO or processor consumption – and prevent shutdown if a certain level is being reached. After the job , the machine will be powered off, if all other mechanisms also allow it.
o
Planed Tasks: To avoid shutdowns if the next planed task would wake up the machine within a specified time.
o
Active usage of mouse and keyboard
*
Support of all relevant shutdown modes:
o
Power Off
o
Restart
o
Standby
o
Hibernate
o
Log off user
o
Shutdown
*
Auto-Reboot: automatically reboot the machine after a certain number of hibernations or standbys. This can be useful for stability reasons on servers as some machines are getting unstable after tens or hundreds of standbys or hibernates without being rebooted from time to time. This functionality requires that a user is being automatically login-in after a restart.
*
Night mode – it might be useful for stability reasons to use hibernation instead of standby to stay independent of power availability and quality during night hours.
*
Automatically shutdown if no users are logged on. This is often the case when users just log off and forget to shutdown.