You are browsing the archive for Cumulative Update.

Avatar of timdk

by timdk

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

9:30 pm in Configuration Manager by timdk

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.

Enjoy the weekend!

Tim

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 R2 Cumulative Update 1

12:46 pm in Configuration Manager by timdk

This post outlines the implementation of Cumulative Update 1 for Configuration Manager 2012 R2 in a lab environment. Note that this update is applicable for 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.

The detailed description and download link for this Cumulative Update  are available here: http://support.microsoft.com/kb/2938441/en-us .

The 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

    The lab infrastructure on which we will implement the CU is rather small: a standalone primary site with the site database and all site system roles installed on a single server. Additionally there is one remote Distribution Point. There are no secondary sites.

Primary Site

A CU implementation needs to be done from top to bottom so we start with the site server first.  Make sure there are no console connections open and then run the installer with elevated privileges.

image

The installation wizard is started:

image

Click Next on the welcome screen.

image

Accept the license terms and click Next.

image

Review all checks and click Next.

image

Leave the option to install the update for the console and click Next.

image

Leave the option to update the Site Database and click Next.

image

As part of the setup process Configuration Manager can create packages to update other components part of the environment. Leave the options to have these packages created and click Next.

image

Leave the default options for the first Update Package and click Next.

image

Leave the default options for the update package for consoles and click Next.

image

And finally also leave the default options for the remaining packages for clients. Click Next.

image

Review the setup summary and click Install to kick off the installation.

image

Installation progress is shown.

image

If you are interested in what is happening under the hood make sure to have a look at the installation log files in the %windir%\temp directory.

image

Click Next once all steps have been completed successfully.

image

Click Finish and restart the server.

In ARP there should be two entries indicating that the Cumulative Update was installed on the system: one for the site server and one for the console. Both are shown in the screenshot below:

image

Also in the registry the CU level for the site can be verified:

image

When opening the About Configuration Manager window from the console the version should show 5.0.7958.1203

image

Remember that at one point we opted to have packages created to implement the CU on other components. These packages are now available in the Software Library workspace:

image

Do not forget to distribute the content for these packages to your Distribution Points. This is not something that is done automatically!

 

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 as well. Any remote consoles in the environment can be updated using the console upgrade package which was automatically created during the installation process.

    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 also the 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 which were also 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.1203" 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 the CU installed should have the following version displayed in the properties:

image

 

And the updated components:

image  image

 

That’s it! I hope this post gives you a good overview on how you could implement the Cumulative Update in your environment.

See you around!

Tim

Avatar of timdk

by timdk

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

5:42 pm in Uncategorized by timdk

Microsoft has released Cumulative Update 1 for System Center 2012 R2 Configuration Manager. This update contains all previously released updates and hotfixes for Configuration Manager R2.

Full details and download information can be found here: http://support.microsoft.com/kb/2938441/en-us 

Note that next to fixing issues, the CU also introduces some changes for Windows Powershell. These changes are documented in a separate KB: 2932274

I will be test driving this CU in my lab shortly so stay tuned for more information.

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 SP1 Cumulative Update 4

6:03 pm in Configuration Manager by timdk

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

      The implementation of Cumulative Update 4 in this lab is now finished!

      Hope this is useful information!

      Tim

      Avatar of timdk

      by timdk

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

      3:37 pm in Configuration Manager by timdk

      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 mainly on fixing issues. It also 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

      Avatar of timdk

      by timdk

      Configuration Manager 2012 Agent installation fails on a Management Point with CU3 installed

      7:07 pm in Configuration Manager by timdk

      When attempting to install the Configuration Manager 2012 client on a site system hosting the management point (MP) role and that site system has CU3 installed, the installation will fail.

      To work around this issue you would have to:

      1. Uninstall the MP role first.
      2. Install the Configuration Manager client
      3. Reinstall the MP role.

      More details are documented in the following KB article: http://support.microsoft.com/kb/2905359

      Hope this saves you some troubleshooting time!

      Tim

      Avatar of timdk

      by timdk

      Post-CU3 update released for System Center 2012 Configuration Manager SP1

      10:23 pm in Configuration Manager by timdk

      Yesterday Microsoft has released an update to address issues that occurred with Cumulative Update 3 (CU3) for Microsoft System Center 2012 Configuration Manager Service Pack 1 (SP1).

      The issues the update resolves are the following:

      • The SQL Update part of the Cumulative Update 3 installation fails when the date format on the instance of Microsoft SQL Server is defined in the DD/MM/YYYY format.
      • The All Windows RT and All Windows RT 8.1 Preview entries should not appear in the supported platform list for new configuration items.
      • Task sequences that contain Windows 8.1 as a condition on the Options tab generate an exception when they are changed or accessed.

      Full details and download information can be found here.

      Avatar of timdk

      by timdk

      Implementing Configuration Manager 2012 SP1 Cumulative Update 2

      9:26 pm in Configuration Manager by timdk

      In the past 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 Secondary Sites once the CU has been applied. Together with 2 colleagues we have found a workaround for the issue, however this is not confirmed to be supported. At the moment of writing this post I am not aware of any supported workarounds or fixes for this issue. In the meantime 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 downloaded 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. This is no longer the case if this option is enabled.

      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

      Make sure to distribute the content to your distribution points. This is not done automatically.

      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 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 my lab is now completed.

      CU Around!

      Tim

      Avatar of timdk

      by timdk

      Implementing Configuration Manager 2012 SP1 Cumulative Update 1

      8:00 am in Configuration Manager by timdk

      A while back I had implemented Cumulative Update 1 (CU1) for System Center 2012 Configuration Manager Service Pack 1 in my lab environment. This post describes the implementation details and findings during the rollout of the CU. With the release of CU2 a few days ago, I am aware that I am running behind with posting this, but as the implementation process for this CU will be very similar I decided to still post this information.

      An overview of the issues fixed in this CU are outlined in the following article: http://support.microsoft.com/kb/2817245/en-us .
      This is also the location where you can download the installation binaries from.

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

      • CAS
      • Primary Sites
      • Secondary Sites
      • SMS Provider

      Additionally it contains updates for the following components:

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

      Let’s continue with the details on the actual implementation. Note that in the lab environment there is only a Standalone Primary site. There is no CAS or secondary sites to which the CU is to be applied.

      Site

      Make sure all open console connections are closed and run the installer:

      image 

      Click Next on the welcome screen.

      image

      Accept the license terms and click Next.

      image

      The prerequisite checker will run some initial checks. Click Next once all checks are successful.

      image

      Leave the option to update the database and click Next.

      image

      Leave the option to create the packages – these will come in handy for updating the other components in your Configuration Manager infrastructure.

      image

      Modify the Server package details if needed. Click Next.

      image

      Modify the Console package details if needed. Click Next.

      image

      Modify the details for the Client packages if needed. Click Next.

      image

      Review the installation summary and click Next to start installing.

      image

      Click Next once all installation tasks have completed successfully.

      image

      Click Finish. In my lab a reboot of the server was required.

      image

      Note that the site version remains unchanged after implementing CU1.

      image

      The CU1 is listed in Control Panel > Programs & Features.

      image 

      The packages for upgrading the other components have been created successfully.

      image

      At this point do not forget to distribute the content to your Distribution Points.

      This concludes the upgrade of the site itself. Now we can further upgrade the remaining components in our infrastructure.

       

      Consoles

      Note that you have to deploy the console update also to the site server if the console was installed locally.

      For deploying the CU1 to all consoles I had created a query based collection. This is the query that was 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 = "Microsoft System Center 2012 Configuration Manager Console"

      Deploy the console update package to the collection to update all remote consoles.

      Once the CU1 for the console is installed it is also listed in Control Panel > Programs & Features:

      image

       

      Clients

      Also for the clients I have created query based collections to deploy the CU1.

      This is the query for the collection containing 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 I used the same query but replaced “X86-Based PC” with “X64-based PC”

      Deploy the client update packages to the x86 and x64 client collections to update all existing clients.

      The client version is updated to 5.00.7804.1202 once the CU1 has been applied:

      image

      To keep track of different client versions and for easy targeting in the future (additional hotfixes and updates) I also created collections for my SP1 CU1 clients.

      image

      This is the query for the collection containing all x86 SP1 CU1 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.1202" and SMS_G_System_SYSTEM.SystemType = "X86-based PC"

      For the x64 clients I used the same query but replaced “X86-Based PC” with “X64-based PC”

      This concludes the implementation of System Center 2012 Configuration Manager SP1 Cumulative Update 1 in my lab environment.

      Until next time!

      Tim