SCCM R3 : Power Management In Practice (Lessons Learned)

November 6, 2010 at 6:56 am in ConfigMgr, ConfigMgr 2007, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, Power Management, R3, sccm, SCCM 2007 R3, sccm2007, Windows 7 by Kenny Buntinx [MVP]

Hi there ,

I have recently deployed Configuration Manager 2007 RTM in production at my TAP customer. Those who attended yesterday my Presentation at the Belgian System Center Day “http://scug.be/blogs/sccm/archive/2010/09/30/announcement-system-center-day-in-belgium.aspx” have seen already the best practices & lessons learned .

I want to thank everyone that has attended our event as it was a great success. The presentations and the links to the recordings will be uploaded very soon , but for those who cannot wait , I’ll post a few teasers below :

 

  • Communication and User Preparation :

We created a communication plan that supported two main objectives:

Drive awareness : Client power management can reduce client computer power consumption, which in turn reduces both the carbon footprint and operational expenses.

Allow users adequate time to decline participation in the program, prior to enforcement:

–Established a four-week period between initial communications and the enforcement of the power management settings.

–Clear communication about the program, the extent of impact, and a link to a process to decline participation were critical to the success of the program. Even though the majority of users would perceive little or no impact, it was key that they reach the few that might.

  • Operational remarks :

 

    • You must Reboot the computer after installing the power mgmt. hotfix.
    • If you create your own Package/Program to install the hotfix, you must select: The program restarts the computer setting, even though the hotfix DOES NOT reboot the computer.
    • If you want to install the power mgmt hotfix during a task sequence for new computers, select “Continue on error”. Put it as the last step of the task sequence.
    • A computer requires an active keyboard/mouse, otherwise it might not go to sleep at all. Mostly this affects KVMs, but we had few examples where a computer is only used remotely (no KVM or a mouse/keyboard) & they don’t fall a sleep.
    • The basic principle: get rid of all your XP machines!
    • Windows XP machines could been switched on for too long. There are multiple processes that can block sleeping!
    • Use correct drivers. Especially display drivers. Fortunately (Vista and higher), R3 report nicely shows those problem machines.
    • It could be very difficult to pinpoint what is the culprit of machines that will not sleep. It could be a client/server app , a remoteApp (TS connection , Citrix , etc ). Regular rebooting helps the situation!
    • Change currency symbol in your reports from $ to €.
    • The following (non limited list) could cause sleeping issues on windows XP or other machines :
    • •Anti Virus scanner

      •Video Card Drivers

      •Report on “Standard VGA Graphics Adapter”

      •Report on “Video Controller”

      •Report on “Video Controller (VGA Compatible)”

      •Check at vendor if Video card supports S3/S4 principle (white brand desktop)

      •Capable hardware with power management features disabled in BIOS ( S3/S4 )

      •HW BIOS version ( Put them on the same level )

 

These lessons learned sections has been build up by sharing our own experiences at our TAP Customers. Thanks to Panu Saukko (MVP) for also sharing his experiences during his TAP assignment with me.

 

Hope it Helps ,

Kenny Buntinx

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest