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

Save Money with Novell ZENworks ® ®

Configuration Management
Implementing Power Management

Jon Giffard Bob Reynolds
Product Management/PSE Product Management/PSE
jgiffard@novell.com breynolds@novell.com

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
2 © Novell, Inc. All rights reserved.

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

My company is deeply concerned about
the environment

being seen to be green

My company is deeply concerned about its
operating costs


A Pain That I'm Used to

North Am ric
North America
e a
EElectricity Average Cost kW kWh ts )
le tric av ragec pe per ( c n(cents)
c ity e ost r h e
11.
00

10.
00

9.
00

8.
00

7.
00

6.
00

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


Impact of Electricity Price on IT

• Scenario • PC Specification
– 1,000 PCs – Model: Dell Optiplex 330

– 250 work days per year – PSU: standard

– 7 hours normal apps – CPU: Core 2 Duo

– 1 hour max performance – Graphics: mid range

– 30% left on overnight* – Optical drive: CD-Rom

• Model – Memory: 2Gb

– Dell Energy calculator
– Display: 17” flat screen

5 © Novell, Inc. All rights reserved. *Lawerence Berkeley Laboratories Survey

1000 PCs with 30% Off at Night

PowerrConsumption Costs
P e c su ptionc
ow on m osts
$120,
000

$115,
000

$110,
000

$105,
000

$100,
000

$95,
000

$90,
000

$85,
000

$80,
000

$75,
000
2009: $117,938
$70,
000
1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009


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

PowerrConsumption Costs
P e c su ptionc
ow on m osts
$40,
000

$35,
000

$30,
000

$25,
000

$20,
000

$15,
000
2009: $30,729

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


Why the Interest Around
Power Management?
• Are you looking at power management because:
the environment
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

16 © Novell, Inc. All rights reserved. *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

Assignment Bundle
Trigger 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


Control
Overview

• 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 Details
Scheme 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 Name
pwr_monitor_ac Turn off monitor when on power Number of minutes
pwr_monitor_dc Turn off monitor when onbattery Number of minutes
pwr_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 minutes
pwr_hibernate_dc Go into hibernate when on battery Number of minutes


Control
The 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


Deploy
Sending 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


Report
Overview

• 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


Report
Process

Vbscript obtains Stores in CDF grabs Novell ZENworks
® ®

active power registry keys registry value, Configuration
scheme details putting them into Management
device inventory agent sends device
record inventory

Values stored in Available for
ADFs in the viewing and
database reporting


Report
The 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


Report
The Results ZCC Reports


Report
The Results ZRS Report


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


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 Disclaimer
This 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.

Bundle: Prepare


Bundle: Prepare
Install 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: Prepare
Install 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 filesWindows Resource KitsTools


Bundle: Prepare
Install 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: Prepare
Install Actions: Registry edit

• Registry key changes to store active settings
– Create
HKLMSOFTWARENovellZenworksPowerInfoLoggedIn
– Create
HKLMSOFTWARENovellZenworksPowerInfoLoggedOut
– Under each branch, add the following string values , set to
“create if don't exist”
pwr_hibernate_state_ac pwr_monitor_ac
pwr_monitor_dc
pwr_hibernate_state_dc
pwr_disk_ac
pwr_hibernate_ac pwr_disk_dc
pwr_hibernate_dc pwr_scheme


Bundle: Prepare
Install Actions: Registry edit

• Registry key changes to set active settings
– Create
HKLMSOFTWARENovellZenworksPowerSettingsLoggedIn
– Create
HKLMSOFTWARENovellZenworksPowerSettingsLoggedOut
– Under each branch, add the following string values , set to
create if don't exist
pwr_hibernate_state_ac pwr_monitor_ac
pwr_monitor_dc
pwr_hibernate_state_dc
pwr_disk_ac
pwr_hibernate_ac pwr_disk_dc
pwr_hibernate_dc pwr_scheme


Bundle: Prepare
Install Actions: Run script

@echo on
cd "%ProgramFiles%Windows Resource KitsTools"
subinacl.exe /noverbose /subkeyreg
"HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows
CurrentVersionControls FolderPowerCfg" /grant=users
subinacl.exe /noverbose /subkeyreg
"HKEY_LOCAL_MACHINESOFTWARENovellZenworksPowerInfo"
/grant=users


Bundle: Set Logged in


Bundle: Set logged in
bundle actions: Install

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


Install Actions: Launch bundle

• Launch bundle prepare


Launch 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


Launch 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


Launch 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


Launch actions: Launch bundle

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


Bundle: Set Logged out


Bundle: Set logged out

– Registry change bundle


Install actions: Launch bundle



bundle actions: Launch

• Power details : Registry Edit
– Put registry keys & values into place
• Audit : Launch bundle
– Use Get logged in bundle for audit


Launch 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


Launch action: Launch windows executable

• Runs vbscript which reads registry values, creates
scheme and activates it
• Parameters:
“%zenworks_home%”set-power.vbs “Logged-Out”
• Run as SYSTEM user
• Wait before proceeding for 10 seconds


Launch actions: Launch bundle

• Launch bundle Get logged in


Configuration steps:
Reporting


Report
Storing 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

Report
Storing audit in ZCM with ADF for logged in user
• ZCC, Configuration → Asset inventory →
Administrator-Defined Fields
– Click on User
Name Data type Size Description
pwr_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 power
pwr_hibernate_dc_user Character 10 Go into hibernate when on battery

Report
Storing audit in ZCM for logged in user

• Should end up with something like this

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

Report
Storing 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 power
pwr_hibernate_state_dc_system Character 10 Hibernate status on battery
pwr_scheme_system Character 20 Current power scheme
pwr_monitor_ac_system Character 10 Turn off monitor when on power
pwr_monitor_dc_system Character 10 Turn off monitor when on battery
pwr_disk_ac_system Character 10 Turn off hard disk when on power
pwr_disk_dc_system Character 10 Turn off hard disk when on batter
pwr_standby_ac_system Character 10 Go into standby when on power
pwr_standby_dc_system Character 10 Go into standby when on battery
pwr_hibernate_ac_system Character 10 Go into hibernate when on power
pwr_hibernate_dc_system Character 10 Go into hibernate when on battery


Report
Storing audit in ZCM for logged out user

• Should end up with something like this

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


Report
Linking 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
– HKLMSOFTWARENovellZenworksPowerInfo
> LoggedIn
> LoggedOut


Report
Linking ADF fields with CDF for logged in

– HKLMNovellZenworksPowerInfoLoggedIn

ADF Registry key value

pwr_hibernate_state_ac_user pwr_hibernate_state_ac
pwr_hibernate_state_dc_user pwr_hibernate_state_dc
pwr_scheme_user pwr_scheme
pwr_monitor_ac_user pwr_monitor_ac
pwr_monitor_dc_user pwr_monitor_dc
pwr_disk_ac_user pwr_disk_ac
pwr_disk_dc_user pwr_disk_dc
pwr_standby_ac_user pwr_standby_ac
pwr_standby_dc_user pwr_standby_dc
pwr_hibernate_ac_user pwr_hibernate_ac
pwr_hibernate_dc_user pwr_hibernate_dc


Report
Linking ADF fields with CDF for logged out

HKLMNovellZenworksPowerInfoLoggedOut

ADF Registry key value

pwr_hibernate_state_ac_system pwr_hibernate_state_ac
pwr_hibernate_state_dc_system pwr_hibernate_state_dc
pwr_scheme_system pwr_scheme
pwr_monitor_ac_system pwr_monitor_ac
pwr_monitor_dc_system pwr_monitor_dc
pwr_disk_ac_system pwr_disk_ac
pwr_disk_dc_system pwr_disk_dc
pwr_standby_ac_system pwr_standby_ac
pwr_standby_dc_system pwr_standby_dc
pwr_hibernate_ac_system pwr_hibernate_ac
pwr_hibernate_dc_system pwr_hibernate_dc


Bundle: Get Logged in


Bundle: Get logged in



Install action: Launch bundle

• Wait for bundle to complete before proceeding



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



• Runs vbscript which gathers active power scheme,
writes to registry values and triggers inventory to
populate CDF
• Parameters:
“%zenworks_home%”get-power.vbs “Logged-In”
• Run as normal user
• Wait before proceeding


Bundle: Get Logged out


Bundle: Get logged out




• Runs vbscript which gathers active power scheme,
writes to registry values and triggers inventory to
populate CDF
• Parameters:
“%zenworks_home%”get-power.vbs “Logged-Out”
• Run as SYSTEM user
• Wait before proceeding for 10 seconds


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

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (8)

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

Similar a Save Money by Implementing Power Management Policies with Novell ZENworks Configuration Management (20)

Más de Novell

Más de Novell (20)

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