Use cases for Lights-Out
If you are new to Lights-Out and all the possible usage scenarios, have a look at the sample use cases here.
Operate a server on demand
Operate a server according to a fixed schedule
Operate a server 24/7
Operate multiple workstations
More details can be found in the online manual.
Operate a server on demand
Scenario
A server is used for file sharing, streaming and remote access.
Intention
Run the server automatically if needed, save energy the rest of the day.
Recommended Settings
Standard delay and action: 5 minutes, save energy or hibernate.
Monitored sources: All standard sources (Computers, IP based clients, Mac OS X, Server backup)
Select all client computers and all IP clients for monitoring on computers page tab (default).
Enable “automatic wake-up” on all client computers (computers properties).
Disable “client side suspend” on all client computers (computer page tab, default).
Result
Server will wake-up when a client computer is started or resumed from standby. Server will stay awake as long as one or more clients are running or as long as audio or video streaming are active.
Additional options
Use network load or share monitoring for devices which are always active (for example Apples iPad).
Configure Wake-On-Wan on your router to enable wake-up over internet.
Configure Lights-Out computer backup.
Operate a server according to a fixed schedule
Scenario
A server is used for file sharing, streaming and remote access.
Intention
Run a server with a fixed start and end time.
Recommended Settings
Create a calendar uptime with a start and end action. Use save energy or hibernate as end action.
To stop the server at the end time, use a forced end action. Otherwise enable monitoring and set-up a standard action.
Enable “automatic wake-up” on all client computers (computers properties).
Disable “client side suspend” on all client computers (computer page tab, default).
Result
Server will wake-up at the configured start time and remain active until the end time. If your server wakes up outside the configured uptime you have to configured a standard action to disable the running server. This may be triggered by a scheduled backup, shadow copies or your network interface card (if pattern match is enabled).
Operate a server 24/7
Scenario
A server which is always on.
Intention
Use Lights-Out for backup control, remote wake-up and runtime monitoring of client computers.
Recommended Settings
Standard delay and action: 5 minutes, Do nothing.
Result
Lights-Out will not control your server. You can still use the backup features, Wake-On-Lan and the monitoring information of Lights-Out as well use the client management features.
Operate multiple workstations
Scenario
You have fixed working hours, for example 8:00 AM to 5:00 PM.
Intention
You like to have the computer ready at start of work in the morning. You want the computer to shut down in the evening.
Extra bonus: If the employee does not come to work, the computer should enter standby.
Recommended Settings
Configure Windows Update active hours to 8:00 AM – 5 PM.
Create three calendar entries:
1. Entry: Start at 7:45 AM, end at 8:00 AM. Start action is wake-up, end action do nothing.
2. Entry: Start at 8:00 AM, end at 5:00 PM. No start action, end action is save energy executed after 15 minutes of inactivity.
3. Entry: Start at 5:00 PM, end at 5:15 PM, Start action is wake-up, end action is forced shutdown.
Result
Computer will wake-up at 7:45 AM outside of active hours and install/complete Windows Updates. If the employee arrives at 8:00 AM, the computer is ready for work. If the employee does not come to work, the second entry will start saving energy at 8:15 AM. The third entry ensures that the computer is shut down after work.