in

myITforum.com

This Blog

Syndication

1E Blog

Empowering Efficient IT

June 2009 - Posts

  • Energy Management in Practice

    Tackling Hard to Reach Distributed Energy Losses in the Non-Intensive Energy Use Sector – Power Management in PCs 

    With the new Carbon Reduction Commitment (CRC) regulations, many businesses are about to face the realities of carbon budgeting for the first time.  Organisations will be required to buy allowances to cover their CO2 emissions; top performers will receive financial rewards; and poor performers will be penalised. 

     The CRC uses electricity consumption as a means for determining which organisations fall under the new regulations, and covers all organisations with an electricity consumption of greater than 6,000 MWH per year (equivalent to emissions of approximately 1,280 tonnes CO2 per year from electricity use). Organisations must purchase allowances to cover all of their CO2 emissions with the exception of transport. 

    The CRC will incentivise energy efficiency and greenhouse gas emissions reduction in the non-energy intensive sector of business and industry.   As well as driving supply side measures to reduce the carbon intensity of energy consumed, the CRC will also provide big incentives for demand side energy efficiency.  Once quick wins have been identified, attention will become more and more focused on harder to reach energy losses.  These include energy losses distributed across organisations due to the organisations physical infrastructure, and also the way it uses energy consuming devices.

     Invisible Energy Losses 

    Whilst most people are familiar with measures such as smart lighting systems using low energy bulbs and motion sensitive switching, a ubiquitous energy demand across all businesses is the personal computer.   A typical PC will use in the order of 90 watts when active (approximately 50 watts for the base unit, and 40 watts for a typical LCD screen); and three to four watts when ‘asleep’. 

    With up to 25% of a modern office’s electricity demand being used to feed an ever-growing IT infrastructure, and PCs and monitors accounting for nearly 40% of IT energy demand, PC power management is a key aspect of facilities energy management. Recent research [1]shows that across the industrialised economies, major and unnecessary energy losses occur simply through people failing to power down their PCs when they leave work. 

    In the UK, it is estimated £300 million per year in energy costs are wasted, and 1.3 million tonnes CO2 emitted as a result.  In the US, where research shows over 50% of PCs are left on overnight, the figures are even higher - $2.8 billion and 20 million tonnes of CO2 per year – the equivalent of the whole of Estonia’s CO2 emissions. 

    It is also the case that whilst PCs do allow low power settings to be used, there are many situations, especially in a networked environment, where processes running on the computer will prevent the in-built low power settings from taking effect.  This can have a dramatic effect on energy use that is invisible to the user.  T

    he monitor may have gone into standby mode, and the PC may appear to be idle, but operational testing by 1E, a specialist software and services IT consultancy, shows that  on any given day an average of over 50% of an organisations computers would fail to go to sleep, and over time this happened to over 90% of the machines. This means that the actual power use of ‘sleeping’ computers is over 7.5 times the expected ‘sleeping’ power demand. 

    Sleepless PCs  

    There are three things that prevent a computer from switching to sleep mode. These are:

    ·        user activity (keyboard input or mouse movement);

    ·        CPU Activity above a threshold (by default 20% overall CPU utilisation);

    ·        a process actively requesting that the computer remains awake.Further detailed analysis showed that all of these things were happening on various computers and at various times of day and night for a variety of reasons:

      some computers had faulty mice which caused pointer drift, making the operating system think that a user was continually moving the mouse;

    others had installed utility software that attempted to actually prevent the computer from sleeping by periodically sending a spurious key press event;some applications would periodically run internal maintenance tasks causing spikes in CPU activity, but doing no useful work;

    some applications would raise a ‘System required’ flag preventing the computer from sleeping. Sometimes this was where users had left applications open that were playing music, or in ‘presentation’ mode.  A lot of the time this was because the application had a file open across the network. 

    Energy Management Solutions 

    PCs refusing to sleep, and the subsequent waste of energy, is difficult to manage across a network using a computer's internal energy management settings.
    However, a very effective energy management tool, NightWatchman, has been developed by 1E that addresses these problems, and also allows network administrators to automatically wake up machines for eg network maintenance and corporate software upgrades, and power them down afterwards.
     Using this energy management tool on an organisations network has been demonstrated to save on average 200 kg of CO2 emissions per PC per year, and generate £26 per PC per year in energy savings.  

    The NightWatchman tool has been extensively used in many organisations over the last eight years.  With over 4.5 million users globally, it represents a tried and tested energy management system that attacks a particularly hard to reach distributed energy loss.  CO2 emissions savings of over 900,000 tonnes, and energy savings of over £110 million are made each year by NightWatchman users across the world.  This type of energy management tool can be a very powerful weapon in an environmental or facilities manager’s armoury.  An organisation such as a large consultancy with 4,000 employees would be able to make CO2 emissions savings of over 800 tonnes and over £100,000 per year in energy savings.  A large corporation with 50,000 employees could save 10,000 tonnes of CO2 and over £1.3 million per year in energy costs. 

    Implications for the CRC

     By looking at IT operations and energy use, proven energy management tools such as NightWatchman demonstrate that the CRC target of 4 million tonnes of CO2 emissions reduced by 2020 is readily achievable.  With the reward and penalty system under the CRC, organisations will be continually pushed to improve their emissions reduction performance.  Energy management solutions such as NightWatchman turn a very hard to reach energy loss into an easily achievable and quantifiable efficiency gain.  This type of solution can help organisations maintain leadership positions in CRC league tables, so as well as very significant energy cost savings, financial rewards under the CRC can be ploughed back into the organisation, making a very clear business case for effective environmental management.             

  • 1E at Low Carbon ICT: Keeping IT Green Conference

    Oxford University, Said Business School – May 2009

    This event is a follow-up from the original 2008 initiative from JISC's activities in education and research by promoting innovation in new technologies and by the central support of ICT services.

    In March 2008, the University of Oxford hosted the 'Towards Low Carbon ICT' conference to stimulate discussion on the practical measures that can be taken to build ICT services that both reduce carbon dioxide emissions, and mitigate the effects that higher energy prices will have on our institutions.

    The JISC funded low-carbon ICT project at the University of Oxford has developed tools and techniques to reduce energy consumption and costs in networked desktop computing environments. At the time of last year's conference, it was policy throughout most of the University departments to leave desktop computers switched on, all day, every day of the year. This need no longer be the case: the tools developed through the project allow desktop computers to be switched off when not in use with, importantly, no inconvenience to the user nor their IT support teams.

    JISC’s aim in commercial engagement is to provide a voice for universities and colleges technical needs and aspirations. They do this by working with the ICT industry leaders to ensure that the sectors current and future needs are met as effectively as possible through their products and services.  1E was invited to participate in the May event to this effect.

    1E showcased the market-leading NightWatchman® PC Energy management software, which has proven energy efficiency gains of on average 40%, saving over $35 and 440 pounds of CO2 emissions per PC per year.   

    As well as the energy savings made by NightWatchman, many delegates were extremely interested in its advanced measurement and reporting features, along with the rapid and verifiable return on investment (typically 6 months).  Being able to verify energy savings and build a cast-iron business case is one of the many features that attracted delegates to NightWatchman and 1E’s market leading software products.   With the overall theme of energy efficiency, 1E opened up a whole new perspective to many delegates by showing that IT equipment is not a black box, but are devices whose power can be actively managed to make significant energy savings.

    Posted Jun 30 2009, 06:14 AM by 1E Blogs
    Filed under:
  • 1E at West Coast Energy Management Congress

    Recently, 1E's own resident engineer Pete Smith, attended the West Coast Energy Management Congress. Here are his thoughts..

     

     Energy efficiency is a major issue on the West Coast, as highlighted by Governor Scharzenagger’s welcoming letter to the event.  The West Coast Energy Management Congress, organized by the Association of Energy Engineers, attracted over 2,000 delegates.  The level of interest in proven energy efficiency technology in these difficult economic times clearly shows that organizations of all types see cutting energy costs through efficiency is both an economic and environmental imperative. 

    IT energy management is a whole new area for many energy management professionals, and can significantly enhance building energy management programs.  1E showcased the market-leading NightWatchman PC Energy management software, which has proven energy efficiency gains of on average 40%, saving over $35 and 440 pounds of CO2 emissions per PC per year.  The new technologies breakfast presentations were very well attended. where1E also provided more information on the eagerly anticipated NightWatchman Server due out in late summer, which is expected to have a transformative effect on Data Center energy management, both through its unique software-based energy measurement system that allows effective rationalization of Data Center hardware, and active energy management – the only tool on the market that automatically reports on and manages energy use by every server in the system. 

    As well as the energy savings made by NightWatchman, many delegates were extremely interested in its advanced measurement and reporting features, along with the rapid and verifiable return on investment (typically 6 months).  Being able to verify energy savings and build a cast-iron business case is one of the many features that attracted delegates to NightWatchman and 1E’s market leading software products.  Another feature that attracted a great deal of interest is NightWatchman’s eligibility for Utility rebates, such as those offered by Southern California Edison and Pacific Gas and Electric, as part of their demand management and energy efficiency programmes, which brings the return on investment down to 1-2 months. 

    With the overall theme of energy efficiency, 1E opened up a whole new perspective to many delegates by showing that IT equipment is not a black box, but are devices whose power can be actively managed to make significant energy savings.

     

    To find out more about 1E's drive for IT Energy Efficiency, cick here.

     
  • Top 5 Green IT Solutions

    So, everyone's talking about it - Green IT. But what should you be prioritizing? Here's an interesting survey from IBM and Info-Tech

    IBM and Info-Tech recently surveyed 1,000 medium-sized companies and looked at adoption rates of different green IT solutions.

    Which ones made the top of the list?

    Read More :- http://tinyurl.com/ln6d25

  • Why won’t my PC go to sleep?

    This is a timely piece, sent to me by Mark Blackburn, a fellow co-founder here at 1E and general technical funkmeister. Timely because I've been having this exact problem with my VAIO laptop on and off (no NightWatchman pun intended) for a while now.. cheers Mark!

     

    Windows power management settings are supposed to make your PC go to sleep after it’s been left unused for a period of time, but you will often find that this doesn’t actually happen when it should.

    There are three things that can keep a PC awake

    User presence

     Keyboard and mouse movement is the only way that the PC has of knowing if a user is present, so ‘mouse drift’ - where the mouse cursor slowly moves across the screen in one direction or another without any actual mouse movement occurring,  usually because of faulty hardware, will prevent a PC from sleeping, since it thinks it’s being constantly used.

    CPU Activity

    The windows idle timers get reset whenever the PC thinks it’s busy (80% idle for the default Vista power scheme), so if something makes the overall CPU utilization of your PC go above 20% then the idle timer will reset, and if this happens regularly (say every 30 minutes) then the PC will never sleep.

    System_Required flag

    Any thread in a process can raise this flag to purposefully prevent the PC from sleeping. There are many reasons why applications raise this flag, some are legitimate, for example Media Player will raise it if you’re watching a video (you don’t want the PC to go to sleep whilst you watch a movie after all), and some are not.

    A lot of the time applications won’t raise the flag themselves, but will cause the underlying OS subsystems to raise it instead. For example if you open a document from a network share the Network Redirector driver (rdbss.sys) will raise this flag to prevent the PC from going to sleep whilst there is an open file across the network.

    So, if your PC won’t sleep here’s what to look for;

    1)      Check that mouse drift isn’t happening

    2)      Run a performance monitor log and look for CPU spikes over 20%

    3)      Close down all apps and see if the PC goes to sleep – figure out by a process of elimination which application is preventing sleep

    Alternatively you can install our NightWatchman client, enable advanced sleepless client detection using the command line “nightwatchman -advancedsleeplessdetection=on“ and then check in the log file to see which process keeps your PC awake.

    If you find it’s a process you don’t care about, you can set NightWatchman to ignore it and force the PC to sleep by using the –selistadd switch to add it to the list of processes that will not be allowed to prevent the machine from sleeping.

  • Diagnostic and Recovery Tasks in Operations Manager - An Overview

    The strength of any great monitoring solution is not just in its ability to report issues and the current state of servers and applications (there are a plethora of good monitoring tools that can do this), but in its ability to resolve problems automatically when they arise. Through the creation of automated tasks, administrators can simplify day to day management of servers and applications to allow support teams to concentrate on only the most critical of issues. This is what distinguishes a GREAT monitoring solution from a good one.

     

    Here at 1E, we love the System Center suite of products. You only need whisper the words ‘Config Manager’ or ‘VMM’ in the ear of a 1E consultant to get their pupils dilated and their heart racing. Be careful with ‘Ops Manager’ though, as this can send one particular 1E consultant into a lather.

     

    Why? I hear you ask... Simply put, Microsoft System Center Operations Manager 2007 (or OpsMgr for short) is the premiere enterprise class monitoring solution, and it just got better with the release of OpsMgr R2. But does OpsMgr meet my criteria for a ‘great’ monitoring solution? You bet!

     

    The true power behind OpsMgr lies within the workflow engine that underpins everything. Each Discovery, Rule and Monitor is a workflow comprised of individual modules that are executed sequentially in order to identify the current status, overall health or relationships between objects. It is this workflow engine that empowers administrators to configure automated tasks. In OpsMgr, these are Diagnostic and Recovery Tasks and they are available for all Monitor workflows.

     

    To better understand the difference between a Rule and a Monitor consider the following:

     

    A rule collects data from various sources (PerfMon, Event Logs, SNMP etc) and stores that data in the Operations Database and the DataWarehouse database. This data is then made available for reporting purposes. Rules (generally speaking) do not generate alerts.

     

    Similarly, a Monitor also collects data but for a different purpose. A monitor uses its captured data to determine the health state of an object. The monitor will change the state of an object (Healthy, Warning or Critical) in response to the information being gathered and the configuration of the monitor (i.e. CPU utilisation threshold), and may in turn generate an alert or run diagnostic and recovery tasks.

     

    For more information, please see this TechNet article (http://technet.microsoft.com/en-us/library/bb977440.aspx)

     

    With this in mind, let’s take a look at an example of what you can do with Diagnostic and Recovery Tasks.

     

    In this example, we will look at the Health Service Heartbeat Failure monitor.

     

    Open the Operations Console and navigate to the Authoring window, expand Management Pack Objects and select Monitors. Change the Scope to Health Service Watcher (Agent) and then expand Entity Health and Availability.

     

    Now select Health Service Heartbeat Failure, right click and select Properties and then navigate to the Diagnostic and Recovery tab.

     

     

    What we can see here are the Diagnostic Tasks (top) and the Recovery Tasks (bottom). From an execution perspective, if the monitor triggers a state change it will automatically launch all Diagnostic tasks that are configured for the specific Health State. It will then launch any recovery tasks, again based on the Health State, passing any parameters from the completed Diagnostic task.

     

    Within the confines of our example;

    1.  The agent managed server does not reply to the heartbeat, causing the Health Service Heartbeat Failure monitor to trigger a state change from Healthy to Critical, indicating that either;

    a.  the OpsMgr Health Service service is in a stopped state or

    b.  the agent managed server is uncontactable

    2.  The Health Service Heartbeat Failure monitor executes the Ping Computer on Heartbeat Failure and Check If Health Service Is Running Diagnostic tasks.

    3.  Once complete, the next step will be to execute any Recovery tasks that are configured to run automatically for the specified health state. In our example there a 2 which relate to the state of the object, however as you can see there are additional Recovery tasks that can be enabled and configured to run. These include restarting the Health Service, enabling and restarting the Health Service and reinstalling the Health Service.

     

    This has been a brief, high level overview of the Diagnostic and Recovery tasks capabilities of OpsMgr. In future blog posts I will cover this topic in greater detail, first examining the underlying xml code and configuration of Recovery and Diagnostic tasks, and then how to create Diagnostic and Recovery tasks to automate system management.

  • Using a GPO to disable the 'Windows XP tour' ballon

    On OSD projects, many times one of the first image/desktop customization requests are:

  • Disable the Windows XP Tour balloon from popping up when domain users logon
  • image
  • At the logon prompt, have the Log on to drop-down set to a domain instead of the local computer name

    Note: I’m not going to blog about this one, as there is already a decent blog entryabout this by John Savill

  • image

    Let's be honest, the "Windows XP Tour" balloon is just plain annoying!!  After eight years, when was the last time you took “The Tour”?...Yup, my thoughts as well.

    I’m all about customizing the OS deployment and making things pretty and simple.  For most, the first option to implementing these customizations would be to script them as a reg-hack during the WIM reference build.  It’s easy…but it’s static and requires modifying the Default User and/or Administrator account profile in the reference image.  I’m from the school of thought: If at all possible, do not make any changes to the image other than installing the base OS and the latest hotfixes.  I try to make all efforts to customizing the image during the actual deployment (e.g. not to the reference image) to the target computers as a reg-hack, or as a “post-deployment” managed configuration via Group Policy.

    There is not a default group policy object to disabling Windows XP Tour for domain users when they logon.  The good news is, I’ve gone ahead and created a group policy template file (.adm) that does this, which you can download and import into your environment.  The template has been created and tested under a Windows Server 2003 AD forest/domain environment.  If you are still running Windows 2000 AD, (haven’t tested it) I think it should still work.  It definitely will not work for Windows Server 2008…

    Well, let’s begin…

    1. Download the Group Policy template file

     

    2. Logon to a domain controller, and open Group Policy Management Console

    image

    3. Right-click the selected group policy object and select Edit

    Note: Either create a new group policy object or select an existing one

    image
    Note: Since the Windows XP Tour option is applied to domain users when they logon to a domain computer, you will be importing the template under User Configuration: 

    4.  Under User Configuration, right-click Administrative Templates

    5. Select Add/Remove Templates
    image 
    6. Click the Add button and browse to the location you downloaded the .adm template to image
    7. Select the template-file and click the Open button image
    8. In the Add/Remove Templates dialog-box, click Close. image
    9. Under User Configuration, navigate to Administrative Templates -> System -> Configure Windows XP Tour

    Note: Since the Windows XP Tour options in the template are not "managed", you will not see the Windows XP Tour option in the right-pane.  You will need to configure the Group Policy Object Editor so that it is able to show policy settings that are unmanaged.
    image 
    10) In the Group Policy Editor, click View –> Filtering image
    11)  …and then uncheck (DISABLE) Only show policy settings that can be fully managed and click OK image
    12) Navigate to Configure Windows XP Tour and you should now see the setting in the right-pane. image
    13) In the right-pane, double-click the setting Windows XP Tour: Number of logons that display a balloon prompt click Enabled and set RunCount value to 0

    14) Click OK and close Group Policy Object Editor

    If not done already, don’t forget to apply the GPO to the desired OU.
    image
  • Using a GPO to disable the 'Windows XP tour' balloon

    On OSD projects, many times one of the first image/desktop customization requests are:

  • Disable the Windows XP Tour balloon from popping up when domain users logon
  • image
  • At the logon prompt, have the Log on to drop-down set to a domain instead of the local computer name

    Note: I’m not going to blog about this one, as there is already a decent blog entryabout this by John Savill

  • image

    Let's be honest, the "Windows XP Tour" balloon is just plain annoying!!  After eight years, when was the last time you took “The Tour”?...Yup, my thoughts as well.

    I’m all about customizing the OS deployment and making things pretty and simple.  For most, the first option to implementing these customizations would be to script them as a reg-hack during the WIM reference build.  It’s easy…but it’s static and requires modifying the Default User and/or Administrator account profile in the reference image.  I’m from the school of thought: If at all possible, do not make any changes to the image other than installing the base OS and the latest hotfixes.  I try to make all efforts to customizing the image during the actual deployment (e.g. not to the reference image) to the target computers as a reg-hack, or as a “post-deployment” managed configuration via Group Policy.

    There is not a default group policy object to disabling Windows XP Tour for domain users when they logon.  The good news is, I’ve gone ahead and created a group policy template file (.adm) that does this, which you can download and import into your environment.  The template has been created and tested under a Windows Server 2003 AD forest/domain environment.  If you are still running Windows 2000 AD, (haven’t tested it) I think it should still work.  It definitely will not work for Windows Server 2008…

    Well, let’s begin…

    1. Download the Group Policy template file

     

    2. Logon to a domain controller, and open Group Policy Management Console

    image

    3. Right-click the selected group policy object and select Edit

    Note: Either create a new group policy object or select an existing one

    image
    Note: Since the Windows XP Tour option is applied to domain users when they logon to a domain computer, you will be importing the template under User Configuration: 

    4.  Under User Configuration, right-click Administrative Templates

    5. Select Add/Remove Templates
    image 
    6. Click the Add button and browse to the location you downloaded the .adm template to image
    7. Select the template-file and click the Open button image
    8. In the Add/Remove Templates dialog-box, click Close. image
    9. Under User Configuration, navigate to Administrative Templates -> System -> Configure Windows XP Tour

    Note: Since the Windows XP Tour options in the template are not "managed", you will not see the Windows XP Tour option in the right-pane.  You will need to configure the Group Policy Object Editor so that it is able to show policy settings that are unmanaged.
    image 
    10) In the Group Policy Editor, click View –> Filtering image
    11)  …and then uncheck (DISABLE) Only show policy settings that can be fully managed and click OK image
    12) Navigate to Configure Windows XP Tour and you should now see the setting in the right-pane. image
    13) In the right-pane, double-click the setting Windows XP Tour: Number of logons that display a balloon prompt click Enabled and set RunCount value to 0

    14) Click OK and close Group Policy Object Editor

    If not done already, don’t forget to apply the GPO to the desired OU.
    image
  • Installing Shopping Central when SMS Provider is NOT hosted on ConfigMgr site server

     

      The following describes the required permissions the Shopping Service Account needs when installing Shopping Central in a distributed server/component environment:

       

      Servers

      ========

      SHOPPING (W2K3)- Shopping Central Server

      NMCM01 (W2K8) - ConfigMgr Central Site Server

      NMSQL01 (W2K8) - SQL Server (2K8) hosting ConfigMgr site database AND ConfigMgr SMS Provider

       

    1. On server hosting ConfigMgr SMS Provider: add Shopping Service account to local Distributed COM Users group. - NOT documented in Shopping Installation Guide
      • Note: In my environment, this was the SQL server (NMSQL01)
    2.  

    3. On the ConfigMgr site server: grant full WMI permissions for both the Root/SMS (Note: Root\SMS\Site_<sitecode> is not listed because in my lab, the SMS Provider is hosted on the remote SQL server.  See bullet below for instructions for when SMS Provider is hosted remotely on a different server).
    4.  

    5. On server hosting ConfigMgr "SMS Provider": grant full WMI permissions for both the Root/SMS and the Root/SMS/SMS_<SiteCode> namespaces. - IS documented in Shopping Installation Guide.  However, "Root\SMS\Site_<sitecode>" namespace ONLY exists on servers hosting the SMS Provider.  If the SMS Provider is installed on the site server, then the namespace will exist on the site server.  As you see on the left is the SQL server hosting the SMS Provider, which has the namespace.  At the bottom is a site server that is also hosting the SMS Provider.  However, on the right is the site server (which is NOT hosting the SMS Provider) does NOT have the namespace.

     

    Posted Jun 05 2009, 12:10 AM by 1E Blogs
    Filed under:
Copyright - www.myITforum.com, Inc. - 2010 All Rights reserved.
Powered by Community Server (Commercial Edition), by Telligent Systems