Save Money by Implementing Power Management Policies with Novell ZENworks Configuration Management

Save Money with Novell® ZENworks® Configuration ManagementImplementing Power Management

Jon GiffardProduct Management/[email protected]

Bob ReynoldsProduct Management/[email protected]

mailto:[email protected]

mailto:[email protected]

© Novell, Inc. All rights reserved.2

Contents

Background

Guidelines for Power Management

What sort of Power Management

– Productivity vs. savings

Preparing for Power Management

Configuring ZCM for Power Management

Geek Zone

– The gory details


But First – Why the Interest Around Power Management?• Are you looking at power management because:-

My company is deeply concerned about the environment

My company is deeply concerned about being seen to be green

My company is deeply concerned about its operating costs


A Pain That I'm Used to

5.00

6.00

7.00

8.00

9.00

10.00

11.00

1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009

North AmericaElectricity average cost per kWh ( cents )

North AmericaElectricity Average Cost per kWh (cents)


Impact of Electricity Price on IT

• Scenario

– 1,000 PCs

– 250 work days per year

– 7 hours normal apps

– 1 hour max performance

– 30% left on overnight*

• Model

– Dell Energy calculator

• PC Specification

– Model: Dell Optiplex 330

– PSU: standard

– CPU: Core 2 Duo

– Graphics: mid range

– Optical drive: CD-Rom

– Memory: 2Gb

– Display: 17” flat screen

*Lawerence Berkeley Laboratories Survey


1000 PCs with 30% Off at Night

$70,000

$75,000

$80,000

$85,000

$90,000

$95,000

$100,000

$105,000

$110,000

$115,000

$120,000

1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009

Power consumption costs

2009: $117,938

Power Consumption Costs


Impact of Power Management

• Same scenario as before with basic power management enabled

– Monitor off after 30 minutes of idle time

– PC into sleep mode after 1 hour of idle time

• Model

– Dell energy calculator


1000 PCs with 30% Off at Night with Basic Power Management

$10,000

$15,000

$20,000

$25,000

$30,000

$35,000

$40,000

1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009

Power consumption costs

2009: $30,729

Power Consumption Costs


Why the Interest Around Power Management?• Are you looking at power management because:

My company is deeply concerned about the environment

My company is deeply concerned about being seen to be Green

My company is deeply concerned about its operating costs

Scenario suggests saving of 74% on PC electricity costs by implementing basic power management

Guidelines for Power Management


Goals for Power Management

• Increase user adoption– Flexible scheduling

– Centralized control

• No impact to productivity– End users will push back

• Integrate with IT Operations– Should fit in with existing toolsets

• Show and tell– Sell the benefits

– Report the benefits


Increase User Adoption

• Sell it to them– Show how power management will be good for them

as well as the organization> Improve battery life for laptop users

> Cooler working environment from I.T equipment using low power modes

– They are still in control> Can choose appropriate power scheme from a defined list

– It will not impact their working day> Not shutting down during work hours

> Monitors come back on from mouse/key movement

> Equipment powers back up from standby


Integrate with IT Operations

• Power management must in control of IT– Define power management policies– Deploy schemes to end users– Report

• Toolsets– Use existing toolset

> Think of power management as application distribution> Reporting is nothing more than an inventory audit

– Using what you have saves on > Costs> Learning something new


Show and Tell

• Progress and adoption of power management

– Schemes that are being used and by who

– Devices with power management vs. those not

– Take before and after pictures of an office at night

– User feedback

– Buy some power monitoring devices

> Show real power consumption before and after

– Look at the utility bills

What Sort of Power Management Productivity vs. Savings


Get the Balance Right

• Aggressive power management will provide highest savings

– Climate Savers* suggest> Monitor/display: turn off after < 15 mins> Hard disc drive: turn off after < 15 mins> Standby/hibernate: < 30 mins

• Aggressive power management will provide the highest level of disruption

– Generate service desk calls – Lose end user buy in – Complaints

*Climate Savers: http://www.climatesaverscomputing.org


Understand Work Patterns and Usage

• When are end users working?– 9 to 5, Monday to Friday no weekends– Shift patterns– Weekend working– Combination thereof

• What are they doing?– Call center worker constantly using device– Marketing who uses device for short bursts at a time– CxO presenting to stockholders

• May need multiple power management schemes to avoid disruption


The Bottom Line

• Power management policies need to be related to end user work patterns

– Avoid impacting productivity

Preparing for Power Management


Preparation

• Obtain VMware Workstation 6.5 or above– Official Windows 7 support found in VMware Workstation v7.0

• Desktops– Build VM machines representing managed device estate

> Windows XP/Windows Vista/Windows 7> Take snapshot of each before starting to experiment with power management

• Laptops– Will need physical devices in order to define settings for

mains power and when on battery– Could sysprep VMs, then use Novell® ZENworks®

Configuration Management to image and deploy to laptop


Design Considerations

• Generic or granular policies– One power management policy will be easy to maintain

but may not provide the biggest savings– Policies covering every combination of devices and work

patterns will help to deliver the biggest savings but will be difficult to maintain

• End user devices– Laptops will require power scheme settings for when on

battery power– Hibernate requires free disk space >= memory

• Screen saver– Not part of power management, its a group policy setting


Design Considerations(cont.)

• End user work hours and out of work hours

– Decide if multiple bundles will be necessary

– Use Novell® ZENworks® Configuration Manager bundle scheduler to set desired policy at the wanted time

• Use KISS principles


What Settings to Use

Windows– XP/2003 has quite a few possible settings

– Vista/7 has lots

This approach uses most common– Disk timeout (mins)

– Monitor timeout (mins)

– Standby timeout (mins)

– Hibernate state (on/off)

– Hibernate timeout (mins)


Suggested Settings for Work Hours

• Objectives: – Achieve greater savings than no power management at all– Do not disruptive end user productivity

• Suggested settings– Screen saver: blank screen after 5 minutes– Monitor/display: 15 minutes– Hard disc: 30 minutes– Standby: 1 hour– Hibernate: Never

• Why not hibernate?– Takes too long for computer to come back


Suggested Settings for Non-work Hours

• Objectives: – Achieve greater savings than assertive power management– Out of hours, no need to worry about disrupting end users

• Suggested settings– Screen saver: blank screen after 5 minutes– Monitor/display: 5 minutes– Hard disc: 10 minutes– Standby: Never– Hibernate: 30 minutes

• Why not standby?– Standby consumes power; hibernate does not


Target Users or Devices?

Users– For

> Define power scheme based on job role> Can accurately target power scheme

– Against> More effort to set up> Creates endless opportunity to refine without actually doing anything

Devices– For

> Minimal effort to implement

– Against> Generic approach that may not achieve full results

Configuring Novell® ZENworks® Configuration Management for Power Management


Three Steps to Success

1. Control– Set power settings in ZCC

– Have as many power schemes as needed

2. Deploy– User or device basis

– Work for Windows XP/Vista/Windows 7

3. Report– Obtain active power scheme

– Generate reports


Methodology

BundleAssignmentTrigger at user log in/user log out

i. Prepare device for power management

ii. Write registry values that define power settings

iii.Launch vbscript that reads values, creates scheme and activates it

iv.Trigger audit to update active scheme details


ControlOverview

• Power settings are stored in the bundle

– Registry values hold the settings

– Gives control to IT

• Two bundles required to address differences in power management between Windows XP and Vista/Windows 7

– Logged in vs. logged out

– Same approach

– Also allows different settings to be used


Control Scheme Settings

• Stored in registry values• Separate values for

logged in and logged out• PowerInfo

– Audit values

• PowerSettings– Scheme values

• Use Registry Edit – Keeps control in ZCC


Control DetailsScheme Settings Registry Values

Name Description Values

pwr_hibernate_state_ac Hibernate status on power On/Off

pwr_hibernate_state_dc Hibernate status on battery On/Off

pwr_scheme Current power scheme Namepwr_monitor_ac Turn off monitor when on power Number of minutespwr_monitor_dc Turn off monitor when onbattery Number of minutespwr_disk_ac Turn off hard disk when on power Number of minutes

pwr_disk_dc Turn off hard disk when on batter Number of minutes

pwr_standby_ac Go into standby when on power Number of minutes

pwr_standby_dc Go into standby when on battery Number of minutes

pwr_hibernate_ac Go into hibernate when on power Number of minutespwr_hibernate_dc Go into hibernate when on battery Number of minutes


ControlThe Bundles

• Three bundles– Prepare

> Creates registry values> Changes registry key permissions

» Power schemes are per user but XP doesn't allow normal user to change

» Simple registry key change solves this

» Need for storing activate power scheme in our registry values

– Set logged in and Set Logged Out> Write registry values for the desired scheme> Launch vbscript to create and activate the power scheme

» Runs as normal user for logged in, SYSTEM for logged out

> Trigger audit


DeploySending the Bundles Out

• Assignments – Bundle: Set logged in

> Install: User log in> Launch: User log in

– Bundle: Set logged out> Install: Device refresh> Launch: Device refresh

• User or device– What ever is best for your environment– Device is the best starting point


ReportOverview

• Audit power management settings

– Logged in and logged out

• Bring back audit information into Novell® ZENworks® Configuration Manager

– View as part of device inventory record

– Include on reports

> Quick reports within ZCC

> Custom reports with ZRS


ReportProcess

Vbscript obtains active power scheme details

Stores in registry keys

CDF grabs registry value, putting them into device inventory record

Novell® ZENworks® Configuration Management agent sends device inventory

Values stored in ADFs in the database

Available for viewing and reporting


ReportThe Bundles

• Two bundles

– Get logged in and get logged out

> Obtain active power scheme and write details into registry values

> Runs as normal user for logged in, SYSTEM for logged out


ReportThe Results ZCC Reports


ReportThe Results ZRS Report

Rollout Best Practice


Guidance

Use 3 stages, each with exit criteria that must be met before moving to next

Development Test Production


Development

• Treat use VMs/laptop from policy design as development environment

• Modify power schemes until they meet your needs• Tweak reports to look pretty• Gate exit criteria

– Registry security modified correctly

– Schemes are delivered and installed with Novell® ZENworks® Configuration Management

– Power schemes become active

– ZCM gathers information on active power scheme


Test

• Move out from development environment to use end user devices

– But not all of them

– Just a few

• Representative sample from friendly users– Not just the IT department

• Gate exit criteria– Same as development

– Include end user satisfaction


Production

• Expand further out from your nice end users• Avoid career defining moments

– No big bang– Rollback plan

• Staged, methodical approach– Floor by floor, building by building

• Exit criteria– Same as development + test– % of estate off outside work hours– Utility bill reduction

Questions and Answers

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

Geek zoneBundle details


Bundle: Prepare


Bundle: PrepareInstall actions

• Install MSI– Install subinacl.exe from resource kit MSI

• Install Files– Install vbscripts used by other bundles

• Registry edit– Create keys & values for storing and setting schemes

• Run script– Batch file that sets reg permissions


Bundle: PrepareInstall Actions: Install MSI

• Download MSI from www.microsoft.com– Search for subinacl

• Use Install MSI action– Upload entire MSI– This will then install to

c:\program files\Windows Resource Kits\Tools

http://www.microsoft.com/


Bundle: PrepareInstall Actions: Install File(s)

• File name: set-power.vbs• Destination: %zenworks_home%• File name: get-power.vbs• Destination: %zenworks_home%• Run as SYSTEM

– Destination is not writable by normal users


Bundle: PrepareInstall Actions: Registry edit

• Registry key changes to store active settings– Create

HKLM\SOFTWARE\Novell\Zenworks\PowerInfo\LoggedIn– Create

HKLM\SOFTWARE\Novell\Zenworks\PowerInfo\LoggedOut– Under each branch, add the following string values , set to

“create if don't exist”pwr_hibernate_state_acpwr_hibernate_state_dcpwr_hibernate_acpwr_hibernate_dc

pwr_monitor_acpwr_monitor_dcpwr_disk_acpwr_disk_dcpwr_scheme


Bundle: PrepareInstall Actions: Registry edit

• Registry key changes to set active settings– Create

HKLM\SOFTWARE\Novell\Zenworks\PowerSettings\LoggedIn– Create

HKLM\SOFTWARE\Novell\Zenworks\PowerSettings\LoggedOut– Under each branch, add the following string values , set to

create if don't existpwr_hibernate_state_acpwr_hibernate_state_dcpwr_hibernate_acpwr_hibernate_dc

pwr_monitor_acpwr_monitor_dcpwr_disk_acpwr_disk_dcpwr_scheme


Bundle: PrepareInstall Actions: Run script

@echo oncd "%ProgramFiles%\Windows Resource Kits\Tools"subinacl.exe /noverbose /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\PowerCfg" /grant=userssubinacl.exe /noverbose /subkeyreg "HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Zenworks\PowerInfo" /grant=users


Bundle: Set Logged in


Bundle: Set logged inbundle actions: Install

• Prepare for power management : Launch bundle – Run registry change bundle


Bundle: Set logged inInstall Actions: Launch bundle

• Launch bundle prepare


Bundle: Set logged inLaunch actions

• Power details : Registry Edit– Put registry keys & values into place

• Set scheme : Launch Windows Executable– Run vbscript to create and activate scheme

• Audit : Launch bundle– Use Get logged in bundle for audit


Bundle: Set logged inLaunch actions: Registry Edit

• Put registry keys & values into place• Each registry key & value action needs to be set to

Create Always– Ensure that any existing values are overwritten

• Run as System


Bundle: Set logged inLaunch actions: Launch windows executable

• Runs vbscript which reads registry values, creates scheme and activates it

• Command: wscript.exe • Parameters:

“%zenworks_home%”\set-power.vbs “Logged-In”– Note placement of “

• Working folder: %zenworks_home%• Run as Normal user• Wait before proceeding


Bundle: Set logged inLaunch actions: Launch bundle

• Launch bundle Get logged in• Wait to complete before proceeding


Bundle: Set Logged out


Bundle: Set logged outbundle actions: Install

• Prepare for power management : Launch bundle – Registry change bundle


Bundle: Set logged outInstall actions: Launch bundle

• Launch bundle prepare


Bundle: Set logged outbundle actions: Launch

• Power details : Registry Edit– Put registry keys & values into place


• Audit : Launch bundle– Use Get logged in bundle for audit


Bundle: Set logged outLaunch action: Registry Edit

• Put registry keys & values into place• Each registry key & value action needs to be set to

Create Always– Ensures that any existing values are overwritten

• Run as System


Bundle: Set logged outLaunch action: Launch windows executable

• Runs vbscript which reads registry values, creates scheme and activates it


“%zenworks_home%”\set-power.vbs “Logged-Out”– Note placement of “

• Working folder: %zenworks_home%• Run as SYSTEM user• Wait before proceeding for 10 seconds


Bundle: Set logged outLaunch actions: Launch bundle

• Launch bundle Get logged in


Configuration steps: Reporting


ReportStoring audit in ZCM with ADF and CDF

• Administrator Define Fields are lovely for storing additional information

– Define name, type, length, default values– Limit of 20 per table– Appear on Collection Data Forms

• Collection Data Forms provide a mechanism for populating these easily

– User entered values– From registry keys / environmental variables

• Information obtained from CDF forms part of managed device inventory record

– Use on reports


ReportStoring audit in ZCM with ADF for logged in user• ZCC, Configuration → Asset inventory →

Administrator-Defined Fields – Click on User

Name Data type Size Descriptionpwr_hibernate_state_ac_user Character 10 Hibernate status on power

pwr_hibernate_state_dc_user Character 10 Hibernate status on battery

pwr_scheme_user Character 20 Current power scheme

pwr_monitor_ac_user Character 10 Turn off monitor when on power

pwr_monitor_dc_user Character 10 Turn off monitor when on battery

pwr_disk_ac_user Character 10 Turn off hard disk when on power

pwr_disk_dc_user Character 10 Turn off hard disk when on batter

pwr_standby_ac_user Character 10 Go into standby when on power

pwr_standby_dc_user Character 10 Go into standby when on battery

pwr_hibernate_ac_user Character 10 Go into hibernate when on powerpwr_hibernate_dc_user Character 10 Go into hibernate when on battery


ReportStoring audit in ZCM for logged in user

• Should end up with something like this

• Note the internal names, we'll need them later


ReportStoring audit in ZCM for logged out user• ZCC, Configuration → Asset inventory →

Administrator-Defined Fields – Click on Workstation

Name Data type Size Description

pwr_hibernate_state_ac_system Character 10 Hibernate status on powerpwr_hibernate_state_dc_system Character 10 Hibernate status on batterypwr_scheme_system Character 20 Current power schemepwr_monitor_ac_system Character 10 Turn off monitor when on powerpwr_monitor_dc_system Character 10 Turn off monitor when on batterypwr_disk_ac_system Character 10 Turn off hard disk when on powerpwr_disk_dc_system Character 10 Turn off hard disk when on batterpwr_standby_ac_system Character 10 Go into standby when on powerpwr_standby_dc_system Character 10 Go into standby when on batterypwr_hibernate_ac_system Character 10 Go into hibernate when on powerpwr_hibernate_dc_system Character 10 Go into hibernate when on battery


ReportStoring audit in ZCM for logged out user

• Should end up with something like this

• Note the internal names, we'll need them later


ReportLinking ADF fields with CDF

• ZCC, Configuration → Inventory → Collection Data Form

– Scroll down list until you reach the ADFs entered previously

• Each ADF will be populated by registry key representing environmental variable set by script that will be run from the gather bundle

– Set each ADF to autofill and enter registry key• All registry keys are found under

– HKLM\SOFTWARE\Novell\Zenworks\PowerInfo

> LoggedIn

> LoggedOut


ReportLinking ADF fields with CDF for logged in

• All registry keys are found under– HKLM\Novell\Zenworks\PowerInfo\LoggedIn

ADF Registry key value

pwr_hibernate_state_ac_user pwr_hibernate_state_acpwr_hibernate_state_dc_user pwr_hibernate_state_dcpwr_scheme_user pwr_schemepwr_monitor_ac_user pwr_monitor_acpwr_monitor_dc_user pwr_monitor_dcpwr_disk_ac_user pwr_disk_acpwr_disk_dc_user pwr_disk_dcpwr_standby_ac_user pwr_standby_acpwr_standby_dc_user pwr_standby_dcpwr_hibernate_ac_user pwr_hibernate_acpwr_hibernate_dc_user pwr_hibernate_dc


ReportLinking ADF fields with CDF for logged out

ADF Registry key value

pwr_hibernate_state_ac_system pwr_hibernate_state_acpwr_hibernate_state_dc_system pwr_hibernate_state_dcpwr_scheme_system pwr_schemepwr_monitor_ac_system pwr_monitor_acpwr_monitor_dc_system pwr_monitor_dcpwr_disk_ac_system pwr_disk_acpwr_disk_dc_system pwr_disk_dcpwr_standby_ac_system pwr_standby_acpwr_standby_dc_system pwr_standby_dcpwr_hibernate_ac_system pwr_hibernate_acpwr_hibernate_dc_system pwr_hibernate_dc

• All registry keys are found underHKLM\Novell\Zenworks\PowerInfo\LoggedOut


Bundle: Get Logged in


Bundle: Get logged inbundle actions: Install



Bundle: Get logged inInstall action: Launch bundle

• Launch bundle prepare• Wait for bundle to complete before proceeding


Bundle: Get logged inbundle actions: Launch

• Get scheme : Launch Windows Executable– Run vbscript to get power information


Bundle: Get logged inLaunch action: Launch windows executable

• Runs vbscript which gathers active power scheme, writes to registry values and triggers inventory to populate CDF


“%zenworks_home%”\get-power.vbs “Logged-In”– Note placement of “

• Working folder: %zenworks_home%• Run as normal user• Wait before proceeding


Bundle: Get Logged out


Bundle: Get logged outbundle actions: Install



Bundle: Get logged outbundle actions: Launch



Bundle: Get logged outLaunch action: Launch windows executable

• Runs vbscript which gathers active power scheme, writes to registry values and triggers inventory to populate CDF


“%zenworks_home%”\get-power.vbs “Logged-Out”– Note placement of “

• Working folder: %zenworks_home%• Run as SYSTEM user• Wait before proceeding for 10 seconds

Save Money by Implementing Power Management Policies with Novell ZENworks Configuration Management

Documents

Transcript of Save Money by Implementing Power Management Policies with Novell ZENworks Configuration Management