attachments/mleach/media/windowslivewriter/installingconfigurationmanager2012sp1cu2_e631/image_thumb.png

Installing Configuration Manager 2012 SP1 CU2 Client Patch With an Application

When you install KB2854009 (CU2) on your Primary Server, it will automatically create packages for you to deploy to your clients.  You will then have to create a collection for each architecture using All Desktop and Server Clients as the Limiting Collection.  I prefer to use Applications whenever I can.  The logic is much better and they are easier to test and troubleshoot.  Using requirements for the Deployment Types, you only need to deploy to one collection, All Desktop and Server Clients.  Here’s how to do it:

After installing KB2854009, the client patches for x86 and x64 are copied to \\[Server]\SMS_[SiteCode]\hotfix\KB2854009\Client.  There is a folder for i386 and x64.  These 2 folders will be your content folders for your Deployment Types.

Some of of the work below can be taken care of by using the Package Conversion Manager to convert the packages KB2854009 created for you.  You will just have to create a second deployment type and set the requirements for the OS architecture using some of the steps below.  Otherwise, here are the manual steps:

1)  Create a new Application.  Select “Manually specify the application information.”  Name it.  Click Next.

 image

2)  This is not really an application you would deploy to the Catalog.  So, nothing to change on this screen.  Click Next.

3)  Here you will create 2 different deployment types.  One for x64 and one for i386.  Click Add.

4)  Select “Manually specify the deployment type information”.  Click Next.  Name your Deployment Type with the architecture in the name.  Click Next.

 image

5)  Enter the content location for the x64 patch:  \\[Server]\SMS_[SiteCode]\hotfix\KB2854009\Client\x64  (change the brackets to suit your environment)

Enter the command line in the Installation Program section:  msiexec.exe /p configmgr2012ac-sp1-kb2854009-x64.msp /L*v %TEMP%\configmgr2012ac-sp1-kb2854009-x64.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

Click Next.

 image

6)  The Detection Method is just as important as the installation command line.  The goal here is to detect the version 5.00.7804.1300.  But, we can’t simply look at the CCMExec.exe.  This file is not one of the components that gets patched to this version.  So, I had to look for a file that showed this version.  To do this, I browsed to the C:\Windows\CCM folder and added the column for File Version.  I sorted by the version and then looked for a file that showed 5.00.7804.1300.  In my environment, I used smsappinstall.exe.

image

Click Add Clause.

Make sure File System is chosen as the Setting Type and File is chosen as the Type. 

Click Browse.  Browse to C:\Windows\CCM and select this file. (Or type everything manually)

At the bottom, select “The file system setting must satisfy the following rule to indicate the presence of this application”.

Property:  Version

Operator:  Greater than or equal to

Value:  5.00.7804.1300

 image

Click OK.

NOTE:  If you are installing the Configuration Manager client on Site Servers, you will also need to create a Detection Method for the same exact file but in C:\Program Files\SMS_CCM.  The servers do not have a CCM folder in Windows.  The connector should be set to “Or”.  (See below)

 image

Click Next.

7)  Specify the User Experience as seen below.  Click Next.

 image

8)  We will need to add Requirements so that this Deployment Type only installs on 64 bit Operating Systems.  Click Add.

Select the options you see below.  In the list of Operating Systems, select all of the 64 bit Operating Systems you have installed (or will install) the client on.  For example, All Windows 7 (64-bit), All Windows 8 (64-bit), All Windows Server 2008R2 (64-bit), All Windows Server 2012 (64-bit). 

 image

Click OK.  Click Next.

9)  There are no dependencies.  Click Next.  Click Next at the summary.  Click Close.

10)  Now, you will need to create a Deployment Type for 32 bit Operating Systems.  Go back to #4 and follow the same steps.  But, use these settings:

Content:   \\[Server]\SMS_[SiteCode]\hotfix\KB2854009\Client\i386

Installation Program:  msiexec.exe /p configmgr2012ac-sp1-kb2854009-i386.msp /L*v %TEMP%\configmgr2012ac-sp1-kb2854009-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous

Requirement:  All of the 32 bit Operating Systems that you have the client installed on.  For example, All Windows 7 (32-bit), All Windows 8 (32-bit), All Windows Server 2003 (32-bit), All Windows Server 2008 (32-bit).

11)  Distribute the content to your Distribution Points.

12)  Test it on a smaller collection.  When verified to be working and totally silent, Deploy this Application to All Desktop and Server Clients.

 To deploy:  Right click on the Application and select Deploy.

Select your Collection.

 image

If you haven’t already, distribute the content to the DPs.  Click Next.

The Action should be Install.  Purpose is Required.  Click Next.

 image

Installation Deadline should be set to “As Soon as possible”.  Click Next.

 image

Choose the User Experience for this deployment.  You should choose “Hide in Software Center and all notifications”.  Click Next.

 image

Set Alert thresholds if you like.  Click Next.

Click Next at the Summary.  Click Close.

 

Enjoy!  Let me know in the comments if you have any questions.

6 Comments

  1. David Marks September 18, 2013
  2. David Marks September 18, 2013
  3. London September 25, 2013
  4. Mike Leach September 26, 2013
  5. Joe Gates March 4, 2015
    • Mike Leach May 29, 2015

Leave a Reply