Posts Tagged ‘CU’

UDM with ConfigMgr and Intune – why CU’s Matter

February 27, 2015 Leave a comment

When delivering sessions on Unified Device Management (UDM) with Configuration Manager and Intune we have always stressed the fact that running on the latest CU level is really important. If you attended our most recent session in Zurich you may recall the following slide header:



A post that was published on the Configuration Manager Team Blog yesterday now gives a perfect overview on why those CU’s matter: as of CU2 there were a lot of fixes and improvements included related specifically to Mobile Device Management.

First there was CU2 which included fixes and improvements related to policies. CU3 included Simple Certificate Enrollment Protocol (SCEP) related fixes and the latest CU4 added the following:

  • Attempts to enroll a device in a user collection containing security groups will fail with an access denied error.
  • Inventory data collected from mobile devices and the Windows Intune connector may be for the wrong device if two devices synchronize simultaneously.
  • Hotfix extends client notification in System Center 2012 R2 Configuration Manager to MDM devices
  • Mobile Device Management settings are not applied to cloud-managed users in System Center 2012 R2 Configuration Manager

For a full history and overview of what was included in which CU have a look at the original post. Remember that these updates are cumulative so installing CU4 is sufficient as it includes everything from previous releases.

So our recommendation remains: apply the latest available Cumulative Update to your Configuration Manager environment as soon as possible!

Until next time!


Implementing the Configuration Manager Servicing Extension

December 23, 2014 1 comment

In the beginning of this month Microsoft has released the Configuration Manager Servicing Extensions. In this blog post we will have a look at the implementation process and which features these extensions can offer.

Before we begin we must get the installation binaries from the Microsoft website, here.

Note that the extensions can be installed on systems running the SP1 Configuration Manager console or a higher version. Based on the requirements page only Windows 7 and Windows Server 2008 R2 are supported Operating Systems.

I installed the extensions manually as in my lab I only have one console running. This is on a 2012 R2 server so I’m not sure how strict (or correct) the requirements on the download page are. The installation took 5 seconds as there are only a few steps to go through:

  1. Run the Configuration Manager 2012 Servicing Extension.msi
  2. Accept the license agreement and click Install
  3. Click Finish

Next time you start the console you should see the Site Servicing node in the administration workspace.



Now lets have a closer look at what else actually became available.

The releases node gives an overview of updates that have been released for Configuration Manager. The release category drop-down allows to filter on specific products.



Next entry we see are the site versions. This gives an overview of all sites in the environment and what version they are running on. Additionally it displays information about installed Cumulative Updates (CU’s).



The third one is Client Targeting. In this node you can get an overview of client versions that are available.


By clicking the create query link at the bottom pane (or from the column in the top pane) you can create queries to list clients with that specific version or a higher one; or to create one for those running a lower version.


The result of this is visible in Queries in the monitoring workspace:



The fourth and last one is Blogs. This can be used for catching up on blog feeds. From the dropdown you can initially only select feeds from the Configuration Manager Team blog or the Configuration Manager Support Team blog. It is possible to add custom feeds as well – I will come back on this in a small follow-up post later on.



That’s all! As you can see these extensions are really easy to implement and they can provide some additional helpful features and information to the Configuration Manager admin.

Enjoy the holidays!


Cumulative Update 5 for System Center 2012 Configuration Manager Service Pack 1 Released

July 23, 2014 1 comment

After the release of Cumulative Update 2 for System Center 2012 R2 Configuration Manager end of June Microsoft has now also released the next CU for System Center 2012 Configuration Manager Service Pack 1: Cumulative Update 5. This update replaces any of the CU’s that were released earlier.

An overview of the issues that are fixed with this cumulative update and further download details can be found here.

The implementation process for this Cumulative Update will be identical to the previous ones, so until I post the implementation experience from our labs please use this blog post as a reference for implementing the CU.

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.


        The installation is started.


        Click Next on the welcome screen.


      Accept the license terms and click Next.


      Verify all prerequisite checks were passed and click Next.


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


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


      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.


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


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


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


      Review the setup summary and click Install when ready.


      Installation progress is shown.


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


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


      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.


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


      And also the Console



      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.


      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"


        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"


      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:


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



      That’s it for now in our lab.

      Good luck with your CU2 implementation!


      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.


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

      March 28, 2014 Leave a comment

      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: 

      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.

      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:

      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: