SCCM 2007 Client Troubleshooting – Part 9: R3 Client Power Management

Configuration Manager 2007 R3 introduced new Power Management features for gaining greater control over device power consumption. While Group Policy provides a fairly robust range of power management options, the additional capabilities 2007 R3 provided add more granularity and flexibility with respect to scheduling and dynamic level control than Group Policy settings alone.

David Stein By David Stein - Thu, May 16, 2013 - 0 comments google+ icon

David is an author and consultant, working for Endurance IT Services in Virginia Beach, Virginia, specializing in Microsoft enterprise systems and Business Process Automation.

Articles in this series

SCCM 2007 Client troubleshooting

Symptoms

  1. Computers are not adjusting power settings in accordance with expectations

Potential Causes

  1. Client doesn’t have required hotfix KB977384 installed (for Windows XP, Vista, Windows 7), or KB2750782 (for Windows 8)
  2. Minimum Operating System requirements are not met
  3. Conflicting AD Group Policy settings
  4. Incorrect or incompatible BIOS settings
  5. Users power off their computer when leaving work (if WOL is not in use)
  6. Users locking computers with CPU-intensive tasks running overnight

Suggestions

Verify that your clients are at least Windows XP Service Pack 3 or newer. While you can install the Client on Windows 2000 SP4 and above, Power Management features are only available starting with Windows XP SP3.

  1. Verify needed hotfixes and updates are installed.
  2. Review Group Policy settings. Use GPRESULT to generate a report to help trace what policies and policy settings are being applied.
  3. Verify that the device hardware model firmware supports Power Management features
  4. Instruct and re-affirm company-wide policies regarding leaving computers powered on, but logged off, when leaving work each day (or whatever your standard policy happens to be). Communicate it until you’re confident every employee knows what they’re supposed to do. Those that refuse to comply can be dealt with later.
  5. If certain users, or teams of users, are identified as commonly needing to run CPU-intensive tasks overnight, work with them to designate special computers to use and develop custom GPO settings, OU locations and Power Management policies to find a suitable compromise.

Helpful links

Series NavigationSCCM 2007 Client troubleshooting – Part 8: Internet Client installation - SCCM 2007 – Advertisements seem to be stuck at “waiting”

-1+1 - Rate this post
Loading ... Loading ...
Disclaimer
Your question wasn't answered? Please ask in the new 4sysops forum!
Please share your thoughts in a comment!

Login

Lost your password?