SCCM 2012 R2 – KB2938441 – Cumulative Update 1

Rate this post

Hi All,

Microsoft has just published the Cumulative Update 1 for System Center 2012 R2 Configuration Manager

Information about this update can be found here and here

2938441: Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager
2932274: Description of PowerShell changes available in Cumulative Update 1 for System Center 2012 R2 Configuration Manager

Also note a recent blog update on our servicing strategy to address some common customer questions.

But now, how to install it?

1- Execute the CM12-R2CU1-KB2938441-X64-ENU.exe file you donwloaded and go to the Mirosoft License Terms. Click Accept and click Next

2- On the pre-requisites, click Next.

3- Select Install the update for the configuration manager console if not selected and click next

4- Select yes, update the site database and click next

5- leave all Deployment Assistance Options select and click Next. This basically means what packages are going to be created

6- 3 packages are going to be created, click next 3 times (yes, check what’s going on before)

7- On the Setup Summary, click Install

8- Once the installation is finished, click Next

9- On the installation completed, click Finish. note that you need to reboot the server to complete the installation

10- Once the server reboots, navigate to the folder \hotfix\kb2938441 and confirm that there are 4 folders and 1 sql script file

11- The console information will now show the version 5.0.7958.1203

12- you’ll noticed 4 packages under the Packages->Configuration Manager Updates

13-if you navigate to HKLM\Software\SMS\Setup you’ll noticed that CULevel is now 1

you can also check the logs c:\windows\temp\cm12-r2cu1-kb2938441-x64-*.log and c:\windows\temp\configmgr2012adminui-r2-kb2938441-i386.msp.log

now, don’t forget to update the clients (you can easily delete all Packages for the older updates from the Console) and you can replace the updated msp files and your task sequence like explained here

be aware that as best practices you should reboot the server prior doing any upgrade 🙂

%d bloggers like this: