You are browsing the archive for R3.

Softgrid 4.1 migration towards ConfigMgr with App-V 4.6 Integration : The story of automation , Part 2.

11:13 am in App-V, AppV, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, migration, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, Softgrid, WMI by Kenny Buntinx [MVP]

Yesterday , I have started explaining my little migration project to migrate away from a standalone Softgrid 4.1 infrastrucure towards a fully integrated SCCM2007 SP R2 App-V 4.6 infrastructure . You can read my previous post right here : http://scug.be/blogs/sccm/archive/2010/10/18/softgrid-4-1-migration-towards-configmgr-with-app-v-4-6-integration-the-story-of-automation-part-1.aspx

Below I will discuss the migration scenario once more in a few bullet points to migrate away from the Softgrid 4.1 standalone environment :

  1. Deploy the new app-V 4.6 clients on all workstations and check for inconsistencies (luckily all packages where sequenced with 4.2)  DONE in Part 1
  2. Pull all existing Softgrid 4.2 sequenced packages thru the new App-V 4.6 Sequencer to avoid any complications. DONE in Part 1
  3. Import all packages into ConfigMgr 2007 SP2 R2 DONE in Part 1
  4. Create all necessary collections and create a dynamic membership query with a AD group name.
  5. Create all the necessary advertisements.
  6. Switch over from Softgrid standalone to Configmgr 2007 R2 SP2. (Think about network impact !)

 

So that will leave us to creating all the necessary collections ( remember 400 Pieces ) and their lovely 400 AD Group Memberships as this was how the Softgrid environment worked (User Group Based) before.

You could accomplish this in basically 2 ways , with a Direct or Dynamic collection membership. Both will have different pro’s  & cons and I will try to explain the difference below :

1. Creating a Dynamic collection membership based on the User Group Resource that will point to an AD Security Groups that contains users in AD for Collection Population.

Assuming there is a best case ( not best practice ! ) scenario where  it can take at least a maximum possible latency (In the case below) of = 3hrs 15 minutes

  • AD Replication to happen – 15 minutes.
  • AD Security Group Discovery – 60 minutes (this is a very short setting – default is a day). ( R3 could save you another 55 minutes here with Delta Discovery enabled )

          image

  • As this is a dynamic membership collection , it is bound to a Collection evaluation cycle – 60 minutes (this is a very short setting – default is a day).
  • Configuration Manager Client Policy Refresh – 60 minutes (Default).

2. Creating a Direct collection Membership based on the User Group Resource that will point to an AD Security Groups that contains users in AD for Collection Population.

Assuming there is a worst case scenario where  it can take at least a maximum possible latency (in the case below) of = 60 minutes

  • Configuration Manager Client Policy Refresh – 60 minutes (Default).
  • User may needs to log off and log-on again.

Option nr 1 is not an approach that I’m  in favor off  as it introduces a much higher latency then option nr 2. I can live with the fact that users may need to do a logon/Logoff to receive there applications. As we have decided to go for option nr2 , it is now time to create a script and to do the following :

  1. Create a collection based on the “Virtual app” name that is been extracted out of the manifest.xml found in the folder of the \\<Servername>\VirtualPackageSource\<Package Name> under a allready existing SUB – Collection
  2. When creating the collection , create a direct collection membership with the Application AD Security group Name . (based on the resourceID)

To accomplish step 2 , you will need as prerequisite to turn on AD Security group discovery in your site settings. When done, you could pull out of SQL a *.csv file with all your Security group names and resource id’s as shown below . Please save the file as you will need it in a later phase .

image

Figure 1: This is how SCCM stores their security group information in the SQL db ( ResourceID/SecurityGroup)

Now we start working on the script , as we need the ResourceID to make it work

Below I will post the VBS code to only create 1 collection and link 1 Security Group :


 

Now I need to figure out how to link the ResourceID’s & groups with my softgrid AppID’s & Security Groups ( as shown below )  . However this will not be an easy task as I need to convert a LDAP GUID to a readable security groupname , make the correlation between the previous exported ResourceID/Security group name  and the converted GUID SecurityGroupName/AppID .

image

Figure 2: This is how Softgrid stores their security group information in the SQL db ( AppID/SecurityGroup (GUID))

Stay tuned for Part 3 very soon ….

 

Hope it Helps ,

 

Kenny Buntinx

ConfigMgr 2007 R3 : Installing Hotfix Prerequisite KB977384 on a Site Server with ICP Pack will fail.

6:26 am in ConfigMgr, ConfigMgr SP2, ConfigMgr2007 R3, Installation, R3, SCCM 2007 R3, SCCM 2007 SP2 by Kenny Buntinx [MVP]

When you install an ICP pack on your Site Server , the Site Server version number gets incremented. When you want to install the R3 Prereq hotfix (977384), it checks to make sure it is not being installed on a ICP Site Server as there is no support yet for any other languages than English. In Europe this happens more than in other parts of the world.

Basically if you try to install this hotfix on a ConfigMgr 2007 SP2 Site Server running an ICP the installation will fail with the following message :

This hotfix is not valid for this version of Configuration Manager"

 

Their is no supported way to uninstall a ICP pack from a site server , and that leaves you only with one  or two options :

  • Wait for the hotfix KB977384 with ICP1 and/or ICP2 support to be released.
  • Install R3 on a Site Server that isn’t running an ICP.

 

Hope it Helps ,

 

Kenny Buntinx

Softgrid 4.1 migration towards ConfigMgr with App-V 4.6 Integration : The story of automation , Part 1.

8:05 pm in App-V, AppV, ConfigMgr, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, migration, R3, sccm, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, SDK, Softgrid, Toolkit by Kenny Buntinx [MVP]

Today we have reached the second phase of migrating the existing Softgrid 4.1 stand-alone infrastructure towards the already upgraded and optimized System Center Configuration Manager 2007 SP2 R2 that we did in fase 1.

We all know that integrating a standalone Softgrid/App-V infrastructure towards a integrated Configmgr 2007 SP2 R2 – App-V implementation could only be done with a big bang. It is either On or Off. We also know that Softgrid sequenced app’s lower then version 4.5 can cause issues and more important , they are lacking the manifest.xml file that is necessary to create virtual packages in ConfigMgr 2007 SP2 R2.

 

image

 

Below I will discuss the migration scenario in a few bullet points to migrate away from the Softgrid 4.1 standalone environment “

  1. Deploy the new app-V 4.6 clients on all workstations and check for inconsistencies (luckily all packages where sequenced with 4.2)
  2. Pull all existing Softgrid 4.2 sequenced packages thru the new App-V 4.6 Sequencer to avoid any complications.
  3. Import all packages into ConfigMgr 2007 SP2 R2
  4. Create all necessary collections and create a dynamic membership query with a AD group name.
  5. Create all the necessary advertisements.
  6. Switch over from Softgrid standalone to Configmgr 2007 R2 SP2. (Think about network impact !)

 

Step 1 :

As the old Softgrid 4.1 stand-alone infrastructure has around 400 virtual packages , and they need to pass thru the app-V 4.6 sequencer to avoid any inconsistencies or complications , the last thing you want to do is play the monkey and open up all packages in the sequencer and save them manually … For this part I had very good teamplayers that are very skilled VBscript writers , again a big thank you to Ewald Lieuwes ( http://www.wchulseiee.net/) & Wouter Schrijvens …

Below I will post the VBS code written for :

 

  1. Going thru the list of virtual packages stored at E:\Softgrid\<Package Name>….
  2. Open them one by one in the App-V 4.6 sequencer and save then to a new location called F:\App-V\<Package Name> to have a backup!
  3. As you see in this script ,we use E:\, F:\ and U:\. The U:\ is the virtual drive partition (default this is Q:\)
  4. Make sure the virtual drive partition is big enough for all of your packages. In this case, this was limited to 2 GB ( standard as Softgrid 4.1 has this limitation of 2 GB in the size of sequenced apps ). We had to resize this to 50 GB.

 

 The code :


 

Step 2 :

As we need to import all 400 upgraded App-V 4.6 virtual packages into ConfigMgr , the last thing you want to do is play the monkey and create all packages in ConfigMgr 2007 R2 SP2 by hand … For this part I had a very good teamplayers that are very skilled VBscript writers , again a big thank you to Ewald Lieuwes ( http://www.wchulseiee.net/) & Wouter Schrijvens …

 

You could do it by using the ConfigMgr SDK , located at http://www.microsoft.com/downloads/en/details.aspx?familyid=064a995f-ef13-4200-81ad-e3af6218edcc&displaylang=en or you could use a standard base script that is located under <Drive>\<PathWhereYouInstalledSCCM>\Tools\VirtualApp\ManageVappPackage.vbs and wrap another VB script around it to build in some other checks or functionalities.

I used the default script located  under <Drive>\<PathWhereYouInstalledSCCM>\Tools\VirtualApp\ManageVappPackage.vbs and wrap another VB script around it .

Below I will post the VBS code written for :

 

  1. Going thru the list of upgraded 4.6 virtual packages stored at a DFS share \start\sccmsrc\[VIRTUALPACKAGESRC]\">\start\sccmsrc\[VIRTUALPACKAGESRC]\">\start\sccmsrc\[VIRTUALPACKAGESRC]\">\\<YourDomainName>\start\sccmsrc\[VIRTUALPACKAGESRC]\<Package Name>….
  2. Create a Source directory App-V package Folder for SCCM , In this case \\<ServerName\VIRTUALPKG$\<Package Name>… , if not exists.
  3. Import the App-V Package in ConfigMgr and add it to the distribution points , called \\CMSRV and \\CMDPMP
  4. Run this script on your SCCM box where your SCCM provider is installed !!

 

The code :


 

In Part 2 , I will continue to blog , if I technically manage to succeed in the following days to do the following :

  • Create all necessary collections and create a dynamic membership query with a AD group name on a automated fashion.
  • Create all the necessary advertisements on an automated fashion.

     

    Come back and check soon.

     

    Hope it Helps ,

     

    Kenny Buntinx

  • System Center Configuration Manager 2007 R3 has arrived

    6:11 pm in configmgr2007, ConfigMgr2007 R3, R3, SCCM 2007 R3 by Kenny Buntinx [MVP]

    Today Jeff Wettlaufer has announced at http://blogs.technet.com/b/systemcenter/archive/2010/10/14/configuration-manager-2007-r3-is-here.aspx that ConfigMgr R3 has been RTM’ed.

    You must all known as well that this is the FIRST release EVER within Microsoft been made that carries the name R3.

    Soon I will write a blog on how to install the final RTM code & if you really want to know how it really works in practice and what the caveats are , come to my session “ConfigMgr R3 , Notes from the field” at our own Belgian System Center Day at November 3thd. Register at http://systemcenterday.eventbrite.com/

    I am very excited to announce and to talk about the release of System Center Configuration Manager 2007 R3. ConfigMgr R3 drives new scenario support to existing world class capabilities.

    Below I will list a few :

    • Power Management for Green IT. When combined with competitive, environmental and regulatory pressure, it is really exciting to deliver centralized, policy based Power Management in ConfigMgr.
    • With ConfigMgr R3, 300,000 managed clients per hierarchy could be managed.
    • By tightening the key relationship to Active Directory with finer, more granular polling and delta monitoring, and marrying this with a new ability to rapidly populate those changes into collections. 
    • Some additional OSD Scenarios , such a Pre-staged Media.
    • Some always wanted ConfigMgr Administrator console extensions , such as “Add a resource to a collection” on a simplified way.

     

    See you at 3 November @ Living Tomorrow when delivering an ConfigMgr R3 session .

     

    Kenny Buntinx.

    Configmgr OSD Task sequence ; Success or Failure notification

    2:12 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Operating System Deployment, OSD, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

    A customers demanded for local support staff to have a simple feature in ConfigMgr 2007 . This feature would be that when operating system deployment has been launched in production , the Local Support staff would receive a simple email to say that their deployment was succeeded or not without touching any ConfigMgr console. Out of the box , this was not feasible . A colleague of mine ( Merlijn  Vanwaeyenberghe)  at  that particular customer found a rather simple but effective solution .

    The steps to reproduce this solution are mentioned below :

    1. Go to the Status filer Rules  in the following section  :

    image 

    2. Create two status filter rules as shown below .

    image

    3.Configure the Status filter Rules as shown below. Create a Status Filter Rule with the following properties:

    · To notify when a specific TS has succeeded:

      • Source: ConfigMgr Client
      • Site Code: site code
      • Message ID: 11143
      • Property: Package ID
      • Property Value: Package ID for the OSD Task Sequence to be monitored

    image

    · To notify when a specific TS has failed:

      • Source: ConfigMgr Client
      • Site Code: site code
      • Component: Task Sequence Engine
      • Severity: Error
      • Property: Package ID
      • Property Value: Package ID for the OSD Task Sequence to be monitored

    image

    · Actions for both cases:

      • Create 2 Powershell scripts on your local drive. In my case D:\scripts\TSSucceeded_Email_Notification.PS1 and D:\scripts\TSFailed_Email_Notification.PS1 with the following code snippets that are listed below.

    image

    **********Code Snippet – FAILED ***********

    param([string]$strComputerName)
    $erroractionpreference = "SilentlyContinue"
    $strSMTP = "Your SMTP server "
    $strSubject = $strComputerName+": OS Deployment FAILED"
    $strBody = @"
    The OSD Task Sequence "The name of your tasksequence" has

        * FAILED *

    op $strComputerName

    http://yourSCCMServer/SMSReporting_XXX/Report.asp?ReportID=143&AdvertID=90020066&ComputerName=$strComputerName&SortRs1Col=1&SortRs1Dir=2
    "@
    $MailMessage = New-Object System.Net.Mail.MailMessage
    $SMTPClient = New-Object System.Net.Mail.smtpClient
    $SMTPClient.host = $strSMTP
    $Sender = New-Object System.Net.Mail.MailAddress("zzz@Yourcompany.zzz ", "SCCM”)
    $Recipient = New-Object System.Net.Mail.MailAddress( “zzz@Yourcompany.zzz, "ZZZ")
    $MailMessage.Sender = $Sender
    $MailMessage.From = $Sender
    $MailMessage.Subject = $strSubject
    $MailMessage.To.add($Recipient)
    $MailMessage.Body = $strBody
    $SMTPClient.Send($MailMessage)

    ***********Code Snippet – FAILED ***********

    **********Code Snippet – SUCCEEDED **************

    param([string]$strComputerName)
    $erroractionpreference = "SilentlyContinue"
    $strSMTP = "Your SMTP server "
    $strSubject = $strComputerName+": OS Deployment Succeeded"
    $strBody = @"
    The OSD Task Sequence "The name of your tasksequence"" is

        * SUCCEEDED *

    op $strComputerName
    "@
    $MailMessage = New-Object System.Net.Mail.MailMessage
    $SMTPClient = New-Object System.Net.Mail.smtpClient
    $SMTPClient.host = $strSMTP
    $Sender = New-Object System.Net.Mail.MailAddress("zzz@Yourcompany.zzz ", "SCCM")
    $Recipient = New-Object System.Net.Mail.MailAddress("zzz@Yourcompany.zzz ", "ZZZ")
    $MailMessage.Sender = $Sender
    $MailMessage.From = $Sender
    $MailMessage.Subject = $strSubject
    $MailMessage.To.add($Recipient)
    $MailMessage.Body = $strBody
    $SMTPClient.Send($MailMessage)

    **********Code Snippet – SUCCEEDED ***********

     

      • Run a program: path to program with optional parameters !! DO NOT USE "QUOTES" !!

             image

             In this Case : c:\windows\system32\WindowsPowerShell\v1.0\powershell.exe -file D:\scripts\TSSucceeded_Email_Notification.PS1 %msgsys

     

    Status filter rules can be used to perform an action when an event has occurred, for instance when an OSD Task Sequence has completed successfully or has failed, an email can be sent out to the OS staging team to inform them as shown above . Don’t let it stop you doing it for other tasks as well . Special thanks to my colleague Merlijn Vanwaeyenberghe for sharing this with us .

     

    Hope it Helps ,

     

    Kenny Buntinx

    Configmgr : Connecting Primary Child Sites To Central Primary parent site in and out of same domain

    1:45 pm in Asset intelligence, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, migration, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script by Kenny Buntinx [MVP]

    Today I was at a customer doing a migration from a Configmgr 2007 with site code APL to a new Configmgr 2007 site with site code ICT. I couldn’t get my new Configmgr site with Site code ICT attached to the central primary. The button for “ set parent site “ was grayed out. I hereby give you my checklist I followed to discover the error . I was stuck for an hour before I realized what was going on .

     

    So here are my tips for troubleshooting it :

     

    1. Install your new SCCM 2007 SP(X) as a new primary server to match what you currently have as a SMS 2007 SP(X) Central Primary. Service Pack levels are important and must be thesame !! Releases however could be different ( one could have R2 and the other can be without R2 ).
    2. Add the Server$ account name to the local admin group on each server and give the new server permission as required on the System container in AD.
    3. Make sure that your AD schema is extended.
    4. Check the following settings are enabled (from Advanced tab in site properties) :
    5. · Publish this site in Active Directory Domain Services

      · Require secure key exchange between sites

    6. If these sites are NOT configured with these options ,then you should manually exchange the public keys :
    7. To manually transfer the child site public key to the parent site

      1. While logged on to the child site, open a command prompt and navigate to the location of Preinst.exe.

      2. Run the following command to export the child site’s public key: Preinst /keyforparent

      3. The Preinst /keyforparent command places the public key of the child site in the <site code>.CT4 file located at the root of the system drive.

      4. Move the <site code>.CT4 file to the parent site’s <install directory>\inboxes\hman.box directory.

      To manually transfer the parent site public key to the child site

      1. While logged on to the parent site, open a command prompt and navigate to the location of Preinst.exe.

      2. Run the following command to export the parent site’s public key: Preinst /keyforchild.

      3. The Preinst /keyforchild command places the public key of the parent site in the <site code>.CT5 file located at the root of the system drive.

      4. Move the <site code>.CT5 file to the <install directory>\inboxes\hman.box directory on the child site

    8. On the primary site server, Add the central site server computer account to the local Site to Site connection group Ex. SMS_SiteToSiteConnection_ICT. Then on the central site server, Add the primary site server computer account to the local Site to Site connection group Ex. SMS_SiteToSiteConnection_APL.
    9. And last but not least : If that button “ set parent site “ ïs grayed out , Make sure that there isn’t any Asset intelligence synch point installed on you Primary Child site installed . I was way to quick and was reading over it , as I was thinking that something else was wrong . Dumb Dumb .

     

    After removing the AIS point in my hierarchy , the button finally came available .

     

    Hope it Helps ,

     

    Kenny Buntinx

    Configuration Manager 2007 R3 RC Update now available

    5:48 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Power Management, R3, sccm, SCCM 2007, SCCM 2007 R3, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

    Hi SCCM guys & Girls,

    I just wanted to let you know that the Release Candidate for ConfigMgr 2007 R3 was been signed off. 

    The update is now available through the Connect Beta Program on https://connect.microsoft.com 

    RTM is getting closer !

    What’s changed/added in the R3 Release Candidate ? :

    • Changes in Power Computer Activity Report flow which helps admin to better understand trends between computer and user activity and associated drilldowns
    • New report Power Insomnia Report which reports most common insomnia reasons based on number of machines impacted for Vista/Win7 machines not sleeping
    • New report Power Computer Details Report to view all power data for a specific machine (plans applied, capability, inventory..)
    • Admin console improvements

    Soon I will write a small blog post on how to go from Beta1 to RC , so have a look in a few days .

     

    Hope it Helps ,

    Kenny Buntinx

    ConfigMgr 2007 R2 & R3 : How to back up SCCM 2007 SQL Reporting Services

    1:22 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, R3, Reporting, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, SQL Reporting services, SRS by Kenny Buntinx [MVP]

    A recent implementation at my ConfigMgr 2007 R3 TAP customer of R3 and SQL reporting services  put me thinking ahead for our disaster recovery procedure .

    SRS Reporting role needs to be installed in the DEFAULT Instance ! Named instances are not supported !!

    The standard ConfigMgr 2007 backup task does not back up the SSRS reports or the SRS configuration.You need to take this into consideration if you :

    • you have created any custom reports
    • you have created any custom report models
    • Set some custom security
    • etc

    I am not going to claim any credit for this , as I found one of my fellow MVP’s Steve Thompson ( in fact a great SRS report Guru ) has created an awesome blog post about it right here : http://myitforum.com/cs2/blogs/sthompson/archive/2009/06/16/how-to-back-up-sccm-2007-r2-reporting-services.aspx

     

    Hope it Helps ,

     

    Kenny Buntinx

    SCCM R3 : Power Management In Practice (how-to) Part 1

    9:33 am in ConfigMgr, ConfigMgr 2007, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Power Management, R3, Reporting, sccm, SCCM 2007, SCCM 2007 R3, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

    Hi there ,

    I have recently deployed Configuration Manager 2007 R3 beta (refresh) in production at my TAP customer.In my previous blog post I highlight the R3 the beta installation on your SCCM 2007 SP2 lab environment .

    See “http://scug.be/blogs/sccm/archive/2010/05/14/sccm-2007-r3-beta-refresh-installation-howto.aspx

    Disclaimer: You are not allowed to install any beta products in your production environment!!! This is only allowed for selected TAP Customers !!! Always install beta products in lab environments !!!

    This blog post highlights the R3 Powermgmt feature ; how to use it in your environment and start using reporting on your powerconsumption.

     

    Prerequisites :

    First you need to start rolling out the R3 Client mgmt hotfix to your clients.When done the SCCM client will show up with a newer version build.The current version is 4.00.6487.2125.

    image 

    Enable your Power management client under “Client Agents”:

    image

    Configuration Manager 2007 R3 beta Client upgrade Validation Report

    After you have deployed the R3 beta Client hotfix, you can use the below query to create a web or SQL SRS report for tracking the R3 beta Client upgrade status

    SELECT  CASE sis.Client_Version0
                 WHEN ‘4.00.6487.2000’ THEN ‘ConfigMgr SP2 RTM’
                 WHEN ‘4.00.6487.2125’ THEN ‘ConfigMgr SP2 R3 beta’
            END AS [ClientVersion]
           ,COUNT(1) AS [Total]
      FROM v_R_System sis where
             sis.Client0 = 1
             AND sis.Obsolete0 = 0
             AND sis.Client_Version0 IN (‘4.00.6487.2000′,’4.00.6487.2125′)
    GROUP BY CASE sis.Client_Version0
                   WHEN ‘4.00.6487.2000’ THEN ‘ConfigMgr SP2 RTM’
                   WHEN ‘4.00.6487.2125’ THEN ‘ConfigMgr SP2 R3 beta’
              END

    Collections :

    You basically need 3 collections :

      • A Baseline collection : This collection contains the members that have will be in scope for Powermgmt.
      • An Enforcement collection : This collection are going to have a Powermgmt plan applied.
      • An Opt-Out collection : This collection will never have a Powermgmt plan applied.

    Some people have different requirements for implementing power plan: some people will have longer work hours (eg. From 6 am – 11 pm), some branch office may have different working hours, etc. To define different power policy, people need to communicate with different teams and make different power settings for different requirements. So you will define different PowerMgmt collections to meet different needs.
    In this blog post example, we will only enforce power policy for one set of regular working hours.

    This is how my collection structure looks like :

    image 

    Like you see here , I have made the difference between laptops/Desktops . This has been done to monitor more closely of what the consumption/savings would be , but also with in the back of my mind for later enabling different powerplans between desktops/laptops.

    [PC-DESKTOP-POWERMGMT-SITE] PowerPlan Baseline Collection query :

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_POWER_MANAGEMENT_CAPABILITIES on SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.ResourceId = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation %" and SMS_R_System.Name not like "OCHP%" and SMS_R_System.Client is not null  and SMS_R_System.ADSiteName = "CDM-Hoofdzetel" and SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.PreferredPMProfile = 1

    It looks like this :

    image 

    As you can see I use the “Power Capabilities.PreferedPMProfile” .

    This value is been returned from your HW inventory that reads out the value from the BIOS that have the ACPI v2.0 Specification  The set of values is currently:

      • 0–Unspecified
      • 1–Desktop
      • 2–Mobile
      • 3–Workstation
      • 4–Enterprise Server
      • 5–SOHO Server
      • and more

     

    [PC-DESKTOP-POWERMGMT-SITE] PowerPlan Disabled Collection query :

    This is right now a static collection membership as I want to add different computers quickly

    [PC-DESKTOP-POWERMGMT-SITE] PowerPlan Enabled Collection query :

    I had the need to make a collection that toke all the members from my baseline “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Baseline Collection” collection and exclude members from my “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Disabled” collection.I needed to seperate several custom machines that I don’t want to be treated by my powermgt plan . I had a really hard time trying to find and/or build a query that actually worked.

    The query to use :

    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client = 1

    and SMS_R_System.ClientType = 1

    and SMS_R_System.ResourceId in (select ResourceID from SMS_CM_RES_COLL_xxxxxxx)

    and SMS_R_System.ResourceId not in (select ResourceID from SMS_CM_RES_COLL_yyyyyyy)

    Replace the item in red with the Collection ID of the baseline collection : “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Baseline Collection” and replace the item in Blue with the Collection ID of the collection : “[PC-DESKTOP-POWERMGMT-SITE] PowerPlan Disabled” you are trying to exclude, which is located under the General tab of the properties window.

    It looks like this :

    image

    Power Plans :

    Before enabling Powerplans to your collections , you need to know about which clients are capable to apply any of your powerplan settings and eventually at that moment take corrective measures.

    To do that we will use SRS reporting  and I will explain that in my other blog post next week . So stay tuned to see my next blog post on how to indentify machines that will need different powerplans and actions taken to resolve some of the issues found.

     

    Hope it Helps ,

    Kenny Buntinx .

    SCCM 2007 R3 Beta (refresh) Installation (Howto)

    6:45 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, R3, Reporting, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, SQL Reporting services, SRS by Kenny Buntinx [MVP]

    I have recently deployed Configuration Manager 2007 R3 beta (refresh) in production at my TAP customer. Below I will outline the steps for deploying Configuration Manager 2007 R3 beta.

    Disclaimer: You are not allowed to install any beta products in your production environment!!! This is only allowed for selected TAP Customers !!! Always install beta products in lab environments !!!

    This blog post highlights R3 the beta upgrade preparation on your SCCM 2007 SP2 environment . You need SP2 in order to be allowed the installation of R3, so if you did not upgraded your environment , this is the first step !

    We talk further about the actual server upgrade and validation tasks.

     

    1. Prerequisites :

    SCCM 2007 SP2 only environment

    Below a table with the site roles where this R3 upgrade is applicable if you have SCCM 2007 SP2 installed :

    Role

    Needed Installs Comments Specific Comments
    Site Server (Central Site) Hotfix KB977384 & R3 Installation Always install This site needs to be upgraded first.
    Site Server (Primary Site) Hotfix KB977384 & R3 Installation Always install These sites needs to be upgraded secondly.
    Site Server (Secondary Site) Hotfix KB977384 & R3 Installation * Always Install These sites needs to be upgraded after the primary sites because you will need certain included R2 features.
    Admin Console R3 Installation to make sure that all functionality is present
    DP, SUP, SQL DB Server (if remote) Not applicable none
     

    SCCM 2007 SP2 R2 environment

    Below a table with the site roles where this R3 upgrade is applicable if you have SCCM 2007 R2 already installed :

    Role Needed Installs Comments Specific Comments
    Site Server (Central Site) Hotfix KB977384 & R3 Installation none This site needs to be upgraded first.
    Site Server (Primary Site) Hotfix KB977384 & R3 Installation none These sites needs to be upgraded secondly.
    Site Server (Secondary Site) Hotfix KB977384 & R3 Installation * Hotfix must always be installed ! Look below for additional information if you really need to install R3 on your secondary’s
    Admin Console R3 Installation to make sure that all functionality is present
    DP, SUP, SQL DB Server (if remote) Not applicable none

    * Site Server (Secondary Site) :

    If you have SCCM 2007 R2 installed on your secondary sites and then :

    1. You don’t need to install R3 on secondary sites if you do not use any "Proxy MP" or "AD discovery" feature at your secondary sites if you only use the "Power Mgmt" feature through your organization & run "AD discovery" on your Central or Primary sites.
    2. You do need R3 on your secondary sites if you do use the "Proxy MP" functionality or "AD discovery" at your secondary sites.

    If you are planning to use these features in secondary sites you need to install R3. Since most customers do use proxy MP role on secondary ,you need to install R3 there as well.

    2. Pre-Flight Checks for R3 Beta (refresh) Upgrade

    • Take a  ConfigMgr Site Backup and verify that it is successful.
    • Make sure that ConfigMgr 2007 SP2 is installed correctly and that all site server components are healthy

     

    3. Configuration Manager 2007 R3 Beta (refresh) Server Upgrade

     

    • Install the server side hotfix (KB977384) (included in the dowload of the R3 media) .This hotfix, which comes with the R3 of SCCM 2007, is a prerequisite for SCCM 2007 R3. During the installation it also creates a SCCM Package/Program containing a MSP file allowing to update SCCM Advanced Clients Components. This client hotfix package has to be deployed to all ConfigMgr 2007 SP2 clients before power policies can be managed.

    image

    Click “Next”to continue.

    TRUVO-0083

    Click “I accept …”to continue and select “Next”to continue.

    image

    Hit the Ïnstall” button.

    TRUVO-0085

    The Hotfix starts to install.

    image

    It will prompt you to create a Package & Program for later deployment to your Configmgr 2007 SP2 clients.

    image

    During the installation process, when prompted to create a software distribution package for client hotfix deployment, Provide a name for the ConfigMgr package & Program. However your package & program needs to be done thru conformity of your production naming convention & deployment standards. This client hotfix package has to be deployed to all ConfigMgr SP2 clients in the environment before their power policies can be managed

    image

    Specify the package source & click “Next” to continue.

    image

    Click “Next” to continue.

    image

    Click “Finish” to exit.

    • During the hotfix KB977384 installation, the source bits for the client hotfix package will be copied into the client\i386\hotfix\KB977384Beta folder. Look if the bits exists in that folder.

    image

    • After successful installation of hotfix KB977384 pre-requisites, execute R3 beta (refresh) installation from the installation source location using SPLASH.HTA. Follow the screenshots below to complete the installation.

    image

    Click “Next” to continue.

    image

    Accept the license agreement and Click “Next” to continue.

    image

    Click “Next” to continue.

    image

    Click “Next” to continue.

    image

    image

    Click “Finish” to exit.

     

    4. Post Configuration Manager 2007 R3 Beta (refresh) Server tasks

    • Open SCCM Console & navigate to Site Database – Site Management – <Site Code> – <Site Name> and view properties to confirm that R3 Installed is “Yes” as shown below

    image

    • Verify that the SMS_Def.mof has been appended with R3 specific WMI classes, without any changes to the pre-existing class definitions.

    image

    image

    • Go to the ConfigMgr Console, navigate to [Site Database] – [Site Management] – [Your site code] – [Your site name] – [Site Settings] – [Client Agents].You will see a new item called “Power Management Client Agent”. Go to the “Power Management Client Agent” properties and check the box “Enable Power Management on Clients”.

    image 

    • Install SCCM Reporting Services Point. Power Management in SCCM 2007 R3 contains a number of reports to help you to analyze power consumption and computer power settings in your organization. These Reports require SQL Reporting Services which was introduced in SCCM 2007 R2.If you never worked or used SRS reporting , get used to it , because it will be the only reporting functionality left in Configmgr V.next.

    Note : I am not going to explain how to set-up SRS reporting . You can find guidance on Technet or the online help .

    image 

    Copy SCCM Reports to Reporting Services. Power Management in SCCM 2007 R3 gives you 17 new reports.

    image

    Click “Next” to Continue.

    image

    Fill in your credentials and Click “Next” to Continue.

    image

    Select “Import Report Definition Language Files From Microsoft Signed Cabinet File”.

    image

    Browse to the "%SCCM installation folder%\Reports\Power Management" folder and select the MicrosoftReportPack.cab file. Click "Open” to Continue.

    image

    Look if all reports are selected and Click “Next” to Continue.

    image

    Click “Next” to Continue.

    image

    Look at the status and see that all reports are imported successfully. Click “Next” to Continue.

    image

    Look in the SCCM console if the reports exists.You can run all Reports from the SCCM Console now.

     

    5. Deploy the MSP file contained into the SCCM Package created by installing the hotfix onto you SCCM 2007 SP2 Clients

    After the R3 installation is completed on the site server, the next step is to deploy R3 hotfix to all SP2 clients to use all R3 features.Look for the Client hotfix package & program that where created during installation and must be available under ‘Software Distribution’ and then look for the Packages Node.

    • Validate your Package & Program Properties

    TRUVO-0092

    • Deploy your package to all your Distribution points, before deploying the package to all clients.

    TRUVO-0093

    • Create your deployment collection(s).Deployments should be done in multiple phases.Start with a Test/Pilot group and the second wave should be per site/region.You could use “Link to Collection” for avoiding creating to much collections.

    TRUVO-0094

    • Creation your Advertisements.There are no special requirements in creating advertisements for this deployment.

    TRUVO-0095

     

    Hope it Helps ,

     

    Kenny Buntinx