Archive

Posts Tagged ‘CU2’

Implementing Configuration Manager 2012 R2 Cumulative Update 2

July 7, 2014 Leave a comment

This blog post outlines the installation of Cumulative Update 2 for Configuration Manager 2012 R2 in our lab. Details about this update are documented in KB2970177. Note that this CU introduces some changes to Windows PowerShell which are documented in a separate KB article KB2962855. Additionally CU2 also adds support for Ubuntu v14.04 – details about this update for the Linux/Unix Client are documented in a third article KB2976481.

Note that this update is applicable for Configuration Manager R2 only, if you are currently still running Configuration Manager 2012 SP1 please refer to my previous blog post on implementing Cumulative Update 4 for ConfigMgr SP1.

Before we begin we need to get the sources for the CU here.

The CU is applicable directly to the following components:

    • CAS
    • Primary Sites (standalone or in a hierarchy)
    • Secondary Sites
    • SMS Provider(s)
    • Console(s)

    Additionally it contains updates for the following components:

    • CAS
    • Primary Sites
    • Secondary Sites
    • SMS Provider(s)
    • Consoles
    • Clients

    The lab we are upgrading does not contain all the components listed above, a CAS and Secondary Site(s) are not present.

        Primary Site

      Cumulative Updates for Configuration Manager are implemented top-down so we start with the site server of the standalone primary site. Before running the installer with elevated privileges ensure there are no more console connections.

    image

        The installation is started.

      image

        Click Next on the welcome screen.

      image

      Accept the license terms and click Next.

      image

      Verify all prerequisite checks were passed and click Next.

      image

      Leave the option to update the (locally installed) console.

      image

      Leave the option to update the site database and click Next.

      image

      During the setup process we can opt to create packages to support updating other components in the infrastructure. Leave the options to have these packages created and click Next.

      image

      Leave the default settings for the servers package and click Next.

      image

      Leave the default settings for the console package and click Next.

      image

      Leave the default settings for both the x86 and x64 client package and click Next.

      image

      Review the setup summary and click Install when ready.

      image

      Installation progress is shown.

      image

      Click next when the installation is finished. In our small lab it took about 10 minutes.

      image

      Click Finish to close the installation wizard. As indicated we will need to do a reboot.

      image

      More details about the installation and what is happening under the hood can be found in the log file located in the %windir%\temp folder. The last lines of the log should also state successful installation and the reboot requirement.

      Once the system is back online there are a few ways to verify the CU2 installation. First method is to look for the following entries in Programs & Features > View Installed Updates.

      image

      In the registry we can also verify the CU level (in HKLM\Software\Microsoft\SMS\Setup)

      image

      And also the Console

      image

       

      During the setup we opted to have some packages created to support implementing CU2 on other components in our infrastructure. These packages should now be visible in the Software Library. Browse to packages and type R2 CU2 in the search box to quickly locate those packages.

      image

      Important: Do not forget to distribute the content of these packages to your Distribution Points!

      Important (2): Do not forget to update your boot images. This can be done by selecting a boot image, right-clicking it and then selecting the action to Update Distribution Points.

      Secondary Sites

      If there are any Secondary Sites in your environment the next step is to implement the CU on those sites. The server update package can be used to automate this. To target the site servers a collection can be built which is populated based on the following 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_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName = "System Center 2012 R2 Configuration Manager Secondary Site Setup"

        Consoles

        As part of the implementation process on the site server the locally installed console was updated. Any remaining remote consoles in the environment can be updated using the console upgrade package.

        To build a collection containing the machines with the console installed the following query could be used:

      • 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_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "System Center 2012 R2 Configuration Manager Console"

      Clients

      Also our clients within the environment need to be brought up to the level of the Cumulative Update. There are multiple approaches to accomplish this; one method could be to deploy the client update packages created automatically during the implementation process.

      As there is a package per processor architecture we will also create matching collections to target our deployments. This is an example query for a collection containing all 64-bit clients with a client version not equal to CU1:

      • 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_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientVersion != "5.00.7958.1303" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"
        The query for the collection with 32-bit clients is identical; just replace “x64-based PC” with “x86-based PC”.

      A client with CU2 installed will display the following version in its properties:

      image

      Also the component version numbers are updated, looks like the same components were in scope as with CU1 a few months ago.

      imageimage

       

      That’s it for now in our lab.

      Good luck with your CU2 implementation!

      Tim

      Week in Review – CW26

      June 29, 2014 Leave a comment

      A few highlights of the past week:

      Enjoy the weekend and see you next week.

      Tim

      Cumulative Update 2 for System Center 2012 R2 Configuration Manager released!

      June 27, 2014 Leave a comment

      Just before the weekend kicks off Microsoft has released Cumulative Update 2 for System Center 2012 R2 Configuration Manager. This update contains all previously released updates and hotfixes for Configuration Manager R2.

      Details about the issues fixed in this Cumulative Update and also download information can be found here: http://support.microsoft.com/kb/2970177

      Note that, similar to CU1, the Powershell changes in Cumulative Update 2 are outlined in a separate KB Article: http://support.microsoft.com/kb/2962855 . To coincide with the release of CU2 a new version of the Windows Phone 8.1 extension has also been made available. More details about that can be found here.

      Stay tuned for more information as soon as I have had the chance to implement this CU in my lab environment.

      In the meantime: enjoy the weekend!

      Tim

      Implementing Configuration Manager 2012 SP1 Cumulative Update 2

      July 3, 2013 Leave a comment

      Previously I had already published a post on implementing CU1, this is a similar post describing my experiences and findings while installing Cumulative Update 2 for Configuration Manager 2012 Service Pack 1 in my lab environment.

      Important: there is a bug in CU2 which prevents you from installing additional Secondary Sites once the CU has been applied. Just now Microsoft has published a blog post on the issue which confirms the issue and also lists possible workarounds.

      The installation binaries for the Cumulative Update can be found here: http://support.microsoft.com/kb/2854009

      As per the documentation, this CU is applicable directly to the following components:

      • CAS
      • Primary Sites
      • Secondary Sites
      • SMS Provider
      • Console

      Additionally it contains updates for the following components:

      • CAS
      • Primary Sites
      • Secondary Sites
      • SMS Provider
      • Consoles
      • Clients

      Once we have reviewed the documentation and obtained the binaries we are ready to proceed with the installation. The lab environment infrastructure is rather simple: a standalone server with the site database and all roles hosted on a single (virtual) machine. No secondary sites at implementation time of this CU.

      Site

      Log on to the site server and make sure all open console connections are closed before running the installer:

      image

      Click Next on the Welcome Screen.

      image

      Accept the license terms and click next.

      image

      Make sure all prerequisite checks are successful and click Next

      image

      Enable the box to also update the console and click Next. Note this is new in CU2 – previously in CU1 the console update package had to be redistributed to the site server to update the locally installed console.

      image

      Select the option to update the site database and click Next.

      image

      Leave the default setting to create the server, console and client packages and click Next. These packages will be useful later on for updating the remaining components in our infrastructure.

      image

      Provide package and program names for the Server package and click Next.

      image

      Provide package and program names for the Console package and click Next.

      image

      Provide package and program names for both Client packages and click Next.

      image

      Review the setup summary and click Install.

      image

      Click Next when the installation steps have been completed successfully.

      image

      Click Finish to close the installation wizard.

      image

      Note that more detailed information on the installation process can be found in the log file located in the Windows\Temp folder.

      image

      CU2 Installations are properly registered in ARP.

      Entry for the site server:

      image

      And for the console:

      image

      In the Software Library workspace the packages for further distributing the CU2 have been created:

      image

      Do not forget to distribute the content to your distribution points. This is not done automatically during the implementation of the CU.

      Consoles

      My console on the site server has been updated already as part of the CU2 installation process. See above for details.

      Any remaining remote consoles I could easily upgrade using a deployment and a query based collection containing machines with a console installed. This is the query I will 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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Microsoft System Center 2012 Configuration Manager Console"

      Once the update is installed it is visible in ARP:

      image

       

      Clients

      Upgrading any existing clients in the environment can easily be done using the pre-created packages. We will created query based collections for targeting the deployments. This is an example query for all x86 SP1 clients:

      • select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ClientVersion = "5.00.7804.1000" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

      For the x64 clients we can use the same query but we need to replace “X86-Based PC” with “X64-based PC”.

      Once the CU2 has been applied the client version number is changed to 5.00.7804.1300.

      image

      Some of the client components also get the 1300 build number:

      image image

      If you would like to build additional collections for the SP1 CU2 clients you can use this query:

      • select * from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ClientVersion = "5.00.7804.1300" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

      Again replace the "X86-based PC" with "X64-based PC" for the 64 bit clients.

      The implementation of Cumulative Update 2 in our lab environment is now completed.

      Until next time!

      Tim