This section provides troubleshooting information for power management in Configuration Manager 2007 R3.

Note
The information in this topic applies only to Configuration Manager 2007 R3.

Client Computers Do Not Sleep after Applying a Power Plan

Certain issues might prevent client computers from entering sleep even after the successful application of a power plan. Examples of these issues include:

  • A busy process, such as a virus scanner, is preventing the client computer from entering sleep.

  • An external USB device is connected to the computer.

  • A generic video device driver is in use.

  • The computer does not support sleep, or the option to enter sleep is not enabled in the computer BIOS.

Solution

Identify the process that is causing the client computer not to enter sleep.

Run the report Power Capabilities to check that the computer supports sleep. For more information, see About the Power Capabilities Report for Power Management.

Run the Power Computer Activity report to view activity on computers in the affected collection. For more information, see About the Power Computer Activity Report for Power Management.

Run the Power Insomnia report to view a list of common causes that prevented computers from entering sleep or hibernate and the number of computers affected by each cause. For more information, see About the Power Insomnia Report for Power Management.

Note
The Windows powercfg command allows the administrator to control the power settings of computers from the Windows command line. On computers running Windows Vista and later, you can use the command powercfg /a to report reasons why a computer is not entering sleep or hibernate. On computers running Windows 7 or Windows Server 2008 R2, you can use the command powercfg/requests to find information about processes that might be preventing the computer from entering sleep or hibernate. For more information about the powercfg command, see your Windows documentation.

Client Computers Do Not Wake after Applying a Power Plan

Client computers in your site might not wake at the time specified in a power management plan.

Solution

Run the Power Computer Activity report to view activity on computers in the affected collection. For more information, see About the Power Computer Activity Report for Power Management.

Run the report Power Capabilities to check that the computer can wake from sleep. For more information, see About the Power Capabilities Report for Power Management.

Multiple Power Plans Are Applied to the Same Computer

If a computer is a member of multiple collections, each applying different power plans, the following actions are taken:

  • Power plan: If multiple values for power settings are applied to a computer, the least restrictive value is used.

  • Wakeup time: If multiple wakeup times are applied to a desktop computer, the time closest to midnight is used.

Solution

Run the report Power Computers with Multiple Power Plans to display any computers that have conflicting power settings applied to them. For more information, see About the Power Computers with Multiple Power Plans Report for Power Management.

Remote Desktop Fails to Connect to a Computer that Has Entered Sleep

If a computer has entered sleep, Remote Desktop Connection fails to connect to the computer.

Solution

Configuration Manager 2007 R3 power management does not support waking computers from sleep when a Remote Desktop session is initiated. If you need to support Remote Desktop on some computers, consider excluding these computers from power management. Alternatively, you might be able to use a Wake on LAN solution or the power management features of the network card to wake these computers from sleep.

Report Parameters Specified on the Properties Page of Power Management Reports Are Displayed Incorrectly

When you specify numeric parameters with more than 2 decimal places on the Properties page of the power management reports, the parameter is rounded to 2 decimal places. However, when you view the report, the parameter is displayed in the report with the correct number of decimal places.

Solution

There is no workaround to this problem. However, the correct parameter is used and displayed in the report results.

See Also