Home > System Center Configuration Manager > Implementing Configuration Manager 2012 SP1 Cumulative Update 4

Implementing Configuration Manager 2012 SP1 Cumulative Update 4

Previously I have blogged about the implementation of CU1 and CU2 for Configuration Manager 2012 Service Pack 1. This post is similar and will cover the implementation of CU4 in a lab environment. Due to time constraints CU3 was not implemented in this lab earlier, so we will upgrade directly from CU2 to CU4. This is supported and should not be an issue.

First we need to get the installation binaries here: http://support.microsoft.com/kb/2922875

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

  • CAS
  • Primary Sites
  • 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

Once we have reviewed the documentation and obtained the binaries we are ready to proceed with the installation. The lab infrastructure where will implement the CU is rather simple: a standalone server with the site database and all roles hosted on a single (virtual) machine. Additionally there is one secondary site part of the environment.

We are now ready to start updating the components.

Primary Site

Implementing a CU is done top-down so we start with the primary site site server first. Close any open console connections and then run the installer with administrative permissions:

image

After the files have been extracted, the installation wizard will start.

image

Click Next on the welcome screen.

image

Accept the license terms and click Next.

image

Click Next once all prerequisite checks are passed successfully.

image

Leave the option to update the (locally installed) admin console. Click Next.

image

Leave the option to update the Site Database. Click Next.

image

Leave the options enabled to create the deployment packages. These will be needed later on to implement the CU on any remote components and clients.

image

Leave the defaults for the package for servers and click Next.

image

Leave the defaults for the package for consoles and click Next.

image

Leave the defaults for the package for clients and click Next.

image

Review the summary and click Install to start the actual installation.

image

Clicking the View Log button allows you to open the installation log using CMTrace. This way you can follow in detail what is happening behind the scenes during the installation of the CU. If you want to review this log post installation it remains in the %windir%\temp folder.

image

Click Next once all steps have completed successfully

image

Click Finish to close the wizard.

The CU4 entry should now be visible in ARP. This in the entry for the site server:

image

And this is the one for the local installed console:

image

Notice the console entry does not have the version property filled in.

In the Software Library workspace the CU4 packages for updating the other components are available. Do not forget to distribute the content for these packages to your Distribution Points. This is not done automatically.

image

 

Secondary Site(s)

As we also have a secondary site in our lab we will need to implement CU4 here as well.

To target secondary sites we will use the previously created server update package and deploy it to a collection with our secondary site servers. For populating this collection we could use 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 = "Microsoft System Center 2012 Configuration Manager Secondary Site Setup"

After deploying the server update package the CU4 will be installed and similar to primary sites this will be visible in ARP.

 

Consoles

The locally installed console on the site server has been updated previously. Any remaining remote consoles in the environment can be updated by deploying the console upgrade package.

To target these remote consoles we can use a query based collection. This is an example 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 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"
  • As indicated previously, the console update is also visible in ARP once it has been installed.

      Clients

      There are a few methods you can use to start upgrading the clients within the environment. One could be to use the pre-created packages and deploying them to query based collections containing your x86 or your x64 clients.

      To achieve this we will create a collection per processor architecture containing all clients not having CU4 installed. This way we are sure to target all clients, also those who may have not been updated during previous CU deployments.
      This is the collection query for the x64 clients:
    • 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.7804.1500" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"
      You can use the same query and replace "X64-based PC" with "X86-based PC" to build a similar collection for x86 clients.
      Looking at the client properties a CU4 client has version number 5.00.7804.1500:

    image

    And the updated components with the .1500 build number:

     image image

      That’s all for now! The implementation of Cumulative Update 4 in this lab is finished!

      See you next time!

      Tim

      Advertisements

      Leave a Reply

      Fill in your details below or click an icon to log in:

      WordPress.com Logo

      You are commenting using your WordPress.com account. Log Out / Change )

      Twitter picture

      You are commenting using your Twitter account. Log Out / Change )

      Facebook photo

      You are commenting using your Facebook account. Log Out / Change )

      Google+ photo

      You are commenting using your Google+ account. Log Out / Change )

      Connecting to %s

      %d bloggers like this: