Quick Tip: Configuration Manager 2012 R2 + SQL 2014

May 6, 2015

Hi everyone,

A quick tip for all you guys wanting to install the Configuration Manager 2012 R2 site database on a server hosting SQL 2014.

When launching the installation and pointing to the SQL 2014 server, that version will be treated as unsupported and the installation won’t continue.

To get the installation to work you should do the following:

  • Download this Microsoft KB:  https://support.microsoft.com/en-us/kb/3020755
  • The KB contains 2 DLL files:
    • prereqcore.dll
    • setupcore.dll
  • Replace the 2 DLLs located in the Configuration Manager 2012 R2 installation source in the folder SMSSETUP\BIN\X64 with the 2 updated DLLs from the KB
  • Launch the installation from the modified installation source

The installation will now continue and you will be able to install the Configuration Manager 2012 R2 site database on SQL 2014.

Hope this helps!

Best regards,



Configuration Manager Client Push include Cumulative Update

April 29, 2015

Hi everyone,

I’ve always been wondering how it’s possible to easily include the latest Cumulative Updates with for example the Configuration Manager client push from the console.

A colleague of mine came up with an elegant solution, in this post I’ll describe shortly how the Cumulative Update can be included in the client push mechanism.

The latest Cumulative Update (CU4 for Configuration Manager 2012 R2) can be downloaded here: https://support.microsoft.com/en-us/kb/3026739 

After installing the CU on the Primary Site Server there is an extra folder created under the installation folder on the Configuration Manager site server, this folder is called hotfix and it contains some automatically created folders visible in the below screenshot


In this post I’ll be focusing on the Client folder which contains 2 subfolders, one for the i386 patch and one for the x64 patch.

I’ll start with the x64 patch, copy the msp file from the directory Client\x64.

Browse to the source of the client package that is used for client push. By default this is the path \\[FQDN Primary Site Server]\SMS_[SiteCode]\Client. There again you have 2 folders (i386 en x64). In the x64 folder create a folder named “ClientPatch” and copy the msp file into this folder.

For the i386 msp file repeat the previous steps and copy the other msp file to the “ClientPatch” folder in the i386 folder

The structure of the client package should look similar like this:


After the necessary files and folders are added make sure you update the package on the distribution points so the next time a client push is done the most recent files are used. All content located in the “ClientPatch” subfolders will be automatically installed.

The ccmsetup.log on the client should show extra info about the update being installed. Also an extra log is created, in this case called: “configmgr2012ac-r2-kb3026739-x64.msp”


In the future, when new CU’s are released simply follow the same procedure and replace the “old” msp-files with the “new” ones.

Extra benefit: When using the same package in your task sequences, the CU will also be applied automatically, without extra parameters. So after the task sequence has completed the client will be on the latest CU without having to update afterwards.

Hope this helps!

Best regards,




Application Approval Request Notification from Configuration Manager 2012 using Powershell

May 27, 2014

Hi all,


Today I was working at a customer and configuring the Application Catalog using Configuration Manager 2012 R2. The customer was interested in the application approval process but was a little disappointed that out-of-the-box it’s not possible to receive notifications when an approval request arrives in Configuration Manager.

As the customer only has Configuration Manager it’s not possible to use any other System Center product like Orchestrator or Service Manager to get things going.

I created an alternative under the form of a Powershell script that runs on a specific schedule (eg. Once every day) to gather all application requests that have a pending approval. This report is emailed to the IT mailbox of the customer. This also makes sure that an administrator doesn’t have to check every now and then in the approval request section of the Configuration Manager console to see if anything new has arrived.

What the script does is basically the following:

  • Reading all data from the WMI class SMS_UserApplicationRequest
  • Filtering all requests which have a current state of 1 ( which means requested)
  • Creating an HTML document which displays a table with all pending requests
  • Sending an email to the IT mailbox with the table as contents. The table contains per request: username, application name, comments and last modified date

The report looks as follows


Anyone that might be interested in this script can comment below and I’ll be happy to help.



Update Configuration Manager 2012 SP1 client with Cumulative Update 3

October 2, 2013

Hi all,

Today I’m going to talk about the Cumulative Update 3 of Configuration Manager 2012 SP1 and how to install the updated client to all Configuration Manager Clients. As you all might know this CU3 fixes some issues with Configuration Manager. For a detailed list, I recommend you to read the following Microsoft documentation: http://support.microsoft.com/kb/2882125/en-us

First of all the CU3 should be installed on the primary site server.

The installation generates a couple of packages that should be appropriately deployed:

–          Package to update the console
–          Package to update the server
–          Package to update clients (x86)
–          Package to update clients (x64)

The focus today is on  the client update and how to get it installed throughout the environment.


We first have to look at the different deployment scenario’s:

–          Upgrade existing Configuration Manager Client (example for x86 clients)

1. Create a collection called All x86 Systems with client using 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_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = “x86-based PC”

This collection has a limiting collection called “All Systems with Client”, this collection was created previously

2. Deploy the x86 client update to the “All x86 Systems with Client” collection using a required deployment

The same can be done for x64 clients

–          Integrating CU3 client with Operating System Deployment

In previous versions of SCCM when a cumulative update was installed, the update was added to the client installation source. Which means that the original client package only needed an update distribution points to include the update + add an additional parameter to the Setup Windows & Configmgr step in the task sequence.

Now the update is stored elsewhere, so a new client package should be created which contains the original client installation source and the cumulative update (.msp file)

1. Create an empty folder in your datastore where packages, applications, etc. are stored (eg. \\[fileserver]\DSL\Microsoft\SCCM_Client\2012_CU3\ML\MSI)

2. Copy the content from the installation folder of SCCM (eg. D:\Program Files\Microsoft Configuration Manager\Client into the new folder

3. Create an extra folder. Eg. Patches

4. Copy the contents of the folder where the update was installed (eg. D:\Program Files\Microsoft Configuration Manager\hotfix\KB2882125\Client) into the Patches folder

5. Create a package in Configuration Manager with the newly created folder as source (\\[fileserver]\DSL\Microsoft\SCCM_Client\2012_CU3\ML\MSI), No need to create a program for this package.

6. Copy the package to the distribution points available within your environment

7. Edit the task sequence where you want to apply the updated version of the Configuration Manager Client. Edit the existing “Setup Windows & Configuration Manager “ step and point it to the newly created package

8 Fill in the following command line at the installation properties field:



This is for the x86 client Operating Systems being deployed, for the x64 operating systems this is the right command line:


From now on clients being deployed with the edited task sequence will receive the latest version of the Configuration Manager Client

For future updates, the same way of working can be used.

Hope this helps!