You are browsing the archive for CU.

Avatar of timdk

by timdk

UDM with ConfigMgr and Intune – why CU’s Matter

6:35 pm in Configuration Manager, Microsoft Intune by timdk

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:

image

 

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 http://support2.microsoft.com/kb/2990658
  • Mobile Device Management settings are not applied to cloud-managed users in System Center 2012 R2 Configuration Manager http://support2.microsoft.com/kb/3002291

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!

Tim

Avatar of timdk

by timdk

Implementing the Configuration Manager Servicing Extension

4:05 pm in Configuration Manager by timdk

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.

image

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.

image

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).

image

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

image

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.

image

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

image

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.

image

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!

Tim

Avatar of timdk

by timdk

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

10:56 pm in Configuration Manager by timdk

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.

Avatar of timdk

by timdk

Implementing Configuration Manager 2012 R2 Cumulative Update 2

5:37 pm in Uncategorized by timdk

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 in the properties through 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

      Avatar of timdk

      by timdk

      Week in Review – CW26

      3:05 pm in Configuration Manager by timdk

      A few highlights of the past week:

      See you next week.

      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

      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

      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