Environmental and setup prerequisites for Power Management and Wake-on-Lan functionality
Power Management Requirements
Before performing a power management task, please confirm that you meet the following requirements.
- Power management tasks performed from machine groups will be successful on physical machines and online virtual machines, but not on offline virtual machines
- A power management license key is required for all power tasks
- An asset management license key is also required for Wake-on-LAN tasks
- In order for power state changes to be made to a target machine, a user must be logged on to the machine or the local security policy Interactive logon: Do not require
- CTRL+ALT+DEL must be disabled.
- The proper credentials must be available:
- When initiating a power management action from Machine View or Scan View, the program will attempt to authenticate to the target machines using the credentials used in the most recent patch scan. If those credentials are invalid or missing (for example, if an agent performed the scan rather than the console) the program will attempt to authenticate to the machines using the default credentials. If the default credentials do not work the program will attempt to authenticate using the account credentials of the person currently logged on to the program. If those credentials do not work, the power management task will fail.
- When initiating a power management action from a machine group or a favorite, the program will attempt to authenticate to the machines using the credentials defined in the machine group. If those credentials are invalid or missing, the program will attempt to authenticate to machines using the default credentials. If the default credentials do not work, the program will attempt to authenticate using the account credentials of the person currently logged on to the program. If those credentials do not work , the power management task will fail.
Sleep and Hibernate Requirements
In order to put a machine in or take a machine out of a sleep or hibernate state, its operating system must be configured to allow the operation.
Wake-on-LAN (WoL) Requirements
- WoL tasks must be performed on physical machines, not on virtual machines
- WoL must be enabled in the BIOS of the target machines. See your hardware vendor's product documentation for details.
- Target machines must have either a wired or a wireless Network Interface Card (NIC) that supports WoL. See your hardware vendor's product documentation for details.
- Target machines can be in sleep, hibernate, or powered off states.
- Network cards on the target machines must have power available (either electric or battery).
- Any intervening routers may need to be configured to forward subnet-directed broadcasts. See your hardware vendor's product documentation for details on configuring your routers.
- Whether you need to configure your routers depends on where your target machines are located. If all the target machines are located on the same subnet as the console, your routers do not need to be reconfigured. If some of your target machines are behind one or more routers and thus on different subnets, the intervening routers must be configured to forward subnet-directed broadcasts on UDP port 9.
- A hardware asset scan of each target machine must be performed prior to initiating a WoL request. The scan is needed in order to obtain the MAC address of each target machine. When configuring the hardware asset scan, make sure the Network option is selected.
- Each target machine's operating system must be configured to allow WoL.
- Outbound UDP port 9 must be open on the console machine.
Power Status Scan Requirements
A power status scan can be performed on physical machines, online virtual machines, and offline virtual machines.
A 3rd party freeware application can be used to verify that the target workstation is setup properly to receive Magic Packets. This is explained in the following document: Wake-on-Lan Magic Packet Test http://community.shavlik.com/docs/DOC-23187