Archive

Posts Tagged ‘CU4’

Implementing Configuration Manager 2012 R2 Cumulative Update 4

February 4, 2015 Leave a comment

Earlier on I have installed the newly released Cumulative Update 4 for Configuration Manager 2012 R2 in my lab. This blog post outlines the steps done during this implementation and can be used as a step by step guide.

First step is to get the sources for the CU here. The KB article also gives a full overview of the fixes and improvements in this update. As the name indicates, this update also contains all elements fixed or added in one of the previously released CU’s.

Note that this update is only applicable to Configuration Manager 2012 R2 – if you are currently still running Configuration Manager 2012 SP1 the latest available cumulative update is CU5.

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 wizard kicks off.

clip_image001

On the welcome screen, click next.

clip_image002

Accept the License Agreement and click Next.

clip_image003

Verify the prerequisite checks and click Next.

clip_image004

Leave the option to update the locally installed console.

clip_image005

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

clip_image006

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.

clip_image007

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

clip_image008

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

clip_image009

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

clip_image010

Review the setup summary and click Install when ready.

clip_image011

Progress is shown for each action.

clip_image012

Install completed! Click Finish to close the wizard.

Notice the mention that a reboot is required.

clip_image013

If you are interested in the more technical details about the installation and would like to see what is happening behind the scenes, have a look at the log file cm12-r2cu4-kb3026739-x64-enu.log  located in the %windir%\temp folder.

After the installation you can do a few verification checks to see if the CU got implemented.

First one is to look for the following entries in Programs & Features > View Installed Updates.

clip_image014

Second one would be to look in the registry in HKLM\Software\Microsoft\SMS\Setup

image

And lastly you can also check the version in the console (see About Configuration Manager):

image

 

As we opted to have some packages created to support implementing the CU in our environment these should now also be visible in the console. Go to the software library and select packages. Select the Configuration Manager Updates folder and then type CU4 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

    Last but not least we also need to get the CU installed on our clients. 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 CU4:

  • 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.1501" 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 CU4 installed will display the following version in its properties:

image

Version numbers for some of the components are also updated:

imageimage

 

As you can see the experience for implementing this CU is pretty straightforward and identical to the previously released CU’s.

Until next time!

Tim

Advertisements

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

February 3, 2015 Leave a comment

metrofixMicrosoft has released Cumulative Update 4 for System Center 2012 R2 Configuration Manager.

This CU includes a large list of fixes for various issues. Details on those fixes and information on added functionality can be found in KB3026739.

PowerShell changes are documented in a separate KB article KB3031717. Additionally the update includes performance optimizations for data replication, an Endpoint Protection platform update (KB2998627) and OS Support for Max OSx 10.10 and Suse Linux Enterprise Server 12.

A few interesting reads about this CU which were published earlier today:

Until next time!

Tim

Implementing Configuration Manager 2012 SP1 Cumulative Update 4

January 30, 2014 3 comments

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

      Cumulative Update 4 for System Center 2012 Configuration Manager Service Pack 1 released!

      January 29, 2014 Leave a comment

      Metro-FixYesterday Microsoft has released Cumulative Update 4 (CU4) for Configuration Manager 2012 Service pack  1. When looking at the contents of the CU at a glance this CU seems to focus on fixing issues, additionally it adds support for Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2).

      Full details and download link can be found here: http://support.microsoft.com/kb/2922875

      Note that the link in the article pointing to the November 2013 anti-malware platform update for EP is broken. This is the working one: http://support.microsoft.com/kb/2907566