Power Management Requirements

Before performing a power management task, please confirm that you meet the following requirements.

General Requirements

  • Power management tasks performed from machine groups will be successful on physical machines and online virtual machines, but not on offline virtual machines
  • 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.
  • When initiating a power management action, the program will attempt to authenticate to the target machines using a variety of credentials and will do so using the following strategy:
  1. If one or more of the following are available, try to authenticate using the credential with the highest precedence, where the precedence order is as follows:
    1. Any managed machine credentials (if initiating the action from Machine View or Scan View) or machine group credentials (if initiating the action from a machine group or favorite)
    2. Default credentials (used if the machine credentials are missing)
  2. If the credential used above does not work, the Integrated Windows Authentication credentials (the credentials of the person currently logged on to the program) will be used.

    3. If neither of these credentials work then the action 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

Hardware 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.
  • The target machines can be in sleep, hibernate, or powered off states.
  • The 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 then 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, then the intervening routers must be configured to forward subnet-directed broadcasts on UDP port 9.

Software Requirements

  • 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.