Essential Configuration Manager 2012 R2 Hotfixes
After the release of SCCM 2012 R2, Microsoft released Configuration Manager 2012 R2 hotfixes. These hotfixes addressed some of the major issues in Configuration Manager 2012 R2. Please read the hotfix information carefully before installing it. Lets look at what issues do these SCCM hotfix resolve and we will also install them on SCCM 2012 R2.
Configuration Manager Hotfixes
An update is available for the “Operating System Deployment” feature of System Center 2012 R2 Configuration Manager
This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.
Issue 1 – After you enable the PXE Service Point role on a distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running.
Following are the lines from Windows Application log: (Note:- This problem affects only distribution points that are installed on site servers)
Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3 Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a Exception code: 0xc0000005 Fault offset: 0x000000000005f61a Faulting process id: 0xae4 Faulting application start time: 0x01cec5d767184634 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll
Issue 2 – When operating system image files are downloaded to SCCM clients, you may find that the download takes longer time. While it took less time in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows OS.
Installing Hotfix (KB2905002)
To install Configuration manager hotfix, log in to SCCM server. Extract and run the hotfix (CM12-R2RTM-QFE-KB2905002-X64-ENU) file.
You will see the setup wizard Software Update for System Center 2012 R2 Configuration Manager. Click Next.
Click I accept these license terms and click Next.
All prerequisite checks passed. Prerequisite check complete. Click Next.
This hotfix will install the update for the Configuration Manager 2012 R2 console. Click Next.
Select all options here and click Next.
The name of the package for CM servers would be KB 2905002-server update-Site Code. Click Next.
The name of the package for CM consoles would be KB 2905002-console update-Site Code. Click Next.
Update package for CM clients(x86 and x64 respectively) would be KB 2905002- x86 client update-Site Code and KB 2905002- x64 client update-Site Code. Click Next.
On Setup Summary page click Install.
The hotfix installation is complete. You can view the setup log file by clicking on View Log. Click Next.
Click Finish.
The hotfix setup log file.
Launch the Configuration Manager 2012 R2 console, click on Software Library. Expand Overview, expand Application Management, expand Packages. Now click Configuration Manager Updates. We see some packages now.
Per-computer variables for imported computers are not read in System Center 2012 R2 Configuration Manager
Per-computer task sequence variables that are defined for imported computers are filtered out of client policies. This prevents the variables from being read during task sequence execution. This problem does not affect per-computer variables that are defined for existing clients. This update applies only to Primary sites.
Click here to download the hotfix.
Installing Hotfix (KB2907591)
Log in to the primary site server. Extract the hotfix (CM12-R2RTM-QFE-KB2907591-X64-ENU) that you have downloaded and run the hotfix file. You will see the setup wizard Software Update for System Center 2012 R2 Configuration Manager. Click Next.
Accept the license terms and click Next.
This hotfix updates only for Site servers and computers that run SMS provider. Click Next.
The name of the package for CM servers would be KB 2907591-server update-Site Code. Click Next.
Now click Install.
Click Next.
Click Finish.
- Launch the Configuration Manager 2012 R2 console.
- Click Software Library, expand Overview.
- Expand Application Management.
- Expand Packages.
- Click Configuration Manager Updates.
On the right hand side of console you will see the packages created by this hotfix. In the below screenshot we see a new package KB 2907591 – server update-IND.
After the update is installed on site servers, any operating system boot images should be updated.
To update boot images
- Launch Configuration Manager console.
- Click Software Library expand Operating Systems
- Click Boot Images, select the boot image that you want to update.
- Right-click and then select the Update Distribution Points action.
Hi!
Are these hotfixes this necessary with version 1802?
Thanks for your reply.
No these hotfixes are applicable only to 2012 R2. You can skip installing these packages and upgrade to current branch.
Hi,
What about the similar error in SCCM 1810 and Windows Server 2016?
Faulting application name: svchost.exe_WDSServer, version: 10.0.14393.0, time stamp: 0x57899b1c
Faulting module name: ntdll.dll, version: 10.0.14393.2608, time stamp: 0x5bd133d4
Exception code: 0xc0000374
Fault offset: 0x00000000000f7b43
Faulting process id: 0x23c4
Faulting application start time: 0x01d4e3bf6988eb85
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Hi,
We want apply the current branch 1706 to our current System Center Platform wich is System Center 2012 R2 (Version 5.0.7958.1401). The reason is that we can’t deploy updates towards Windows 10 clients.
The questions are:
Is possible do this migration in parallel without affect the current productive enviroment?
Is possible have two sites or two Sytem Center server in the same domain?
Wich is the recomended procedure for this migration?
Thanks
Are these neccessairy for SP2 also? Edit: should have read further
Prajwal Desai,
Hi, I installed SCCM 2012 SP2. please advise is the hotfix suit for this version, thx.
Hi, why do you need to install hotfix ?. If your ConfigMgr is working fine then no need to install hotfix. I guess MS has fixed many issues in the SP2.
I am a freshman to SCCM. I would like to know more info about it, please guide me.
1. SCCM 2012 SP2 or SCCM 2012 R2 SP1 which is the latest version. I would like to install 2012 R2 in the first place, but can’t found it in MS software licensing web portal. Please advise.
Hi,
These Hotffix are included in SCCM CU4 ?
If I install CU4 after installation of server, it replace the Hotflixe that you speak ?
Thanks
Yes it will.
I am able to Install sccm2012 on MS server 2008…do i need to run all these (3)hotfixes.
1-5002
2-7566
3-6611…?????
If you are referring to the CM hotfixes for R2, then I would say that you install these hotfixes only if it’s required. Read the hotfix description and then install it if required.
Thanks a Ton mate…may i get you number…i need a training on sccm 2012 . Kindly mail me on (rohan.sccm@gmail.com)
Hi Rohan, please don’t mind, I usually don’t share the number. I take the SCCM trainings online during the weekends. It’s only when people require I train them. You can connect and be in touch with me through skype or hangouts.
I understand Sir, i just wish to Learn Sccm more professional way…..to get a better job…..Plz share your Skype id
After i run both hot fixes, i get a warning on the create server package action. In the log file it states: failed to read registry key softwaremicrosoftsmsproviders
Prajwal,
There are two more of hotfixes for SCCM 2012 R2:
KB2907566 – This for SCEP 2012
KB2916611 – This for Proxy Authentication (if the company is using Proxy to authenticate).
I’m hoping that you could add these in your documentation.
Thanks,
Reza
Thank you Reza, I will update the post soon..
As part of SCCM set up, I wanted to know, is it mandatory to install the hot fixes in this list or to proceed only if we face issues in the respective areas?
thanks, appreciate your work.
Its not mandate, you can install it as per requirement. For example if you are using SCCM 2012 R2 to deploy OS you will need to install one of the hotfix that resolves the WDS service issue.
Dear Prajwal, I have recently install SCCM 2012 R2 SP, but when I see the version there is no R2 only SP1 showing, I thing there is hotfix should be apply to see R2. Kindly what is cumulative name?
Recently I have posted the build and version numbers here – https://www.prajwaldesai.com/sccm-configuration-manager-build-version-numbers/