Configuration Manager 2012 R2 Hotfixes

42064

Configuration Manager 2012 R2 Hotfixes Soon after the release of Microsoft System Center 2012 R2 Configuration Manager, Microsoft released Configuration Manager 2012 R2 hotfixes that addressed some of the major issues in Configuration Manager 2012 R2. Lets look at what issues do these hotfixes resolve and we will also install them on SCCM 2012 R2.

Configuration Manager 2012 R2 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 an instance of a specific 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 Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did 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 operating system

Download Hotfix

Installing Hotfix (KB2905002)

Log in to the machine where the Configuration Manager 2012 R2 is installed, extract the hotfix (CM12-R2RTM-QFE-KB2905002-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 on Next.

Configuration Manager 2012 R2 Hotfixes

Click I accept these license terms and click on Next.

Configuration Manager 2012 R2 Hotfixes

After the prerequisite check is done click Next.

Configuration Manager 2012 R2 Hotfixes

This hotfix will install the update for the Configuration Manager 2012 R2 console. Click on Next.

Configuration Manager 2012 R2 Hotfixes

The hotfix also creates packages which can be deployed to other configuration manager systems, click on Next.

Configuration Manager 2012 R2 Hotfixes

The name of the package for CM servers would be KB 2905002-server update-Site Code. Click on Next.

Configuration Manager 2012 R2 Hotfixes

The name of the package for CM consoles would be KB 2905002-console update-Site Code. Click on Next.

Configuration Manager 2012 R2 Hotfixes

The name of the 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 on Next.

Configuration Manager 2012 R2 Hotfixes

On Setup Summary page click on Install.

Configuration Manager 2012 R2 Hotfixes

The hotfix is installed successfully. You can view the setup log file by clicking on View Log. Click on Next.

Configuration Manager 2012 R2 Hotfixes

Click on Finish.

Configuration Manager 2012 R2 Hotfixes

The hotfix setup log file.

Configuration Manager 2012 R2 Hotfixes

Launch the Configuration Manager 2012 R2 console, click on Software Library, expand Overview, expand Application Management, expand Packages and click on Configuration Manager Updates. On the right hand side of console you will see the packages that were created by this hotfix.

Configuration Manager 2012 R2 hotfixes

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.

Download Hotfix

Installing Hotfix (KB2907591)

Log in to the machine where the Configuration Manager 2012 R2 is installed, 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 on Next.

Configuration Manager 2012 R2 Hotfixes

Click I accept these license terms and click on Next.

Configuration Manager 2012 R2 Hotfixes

 

This hotfix updates only for Site servers that run SMS provider. Click Next.

Configuration Manager 2012 R2 Hotfixes

The name of the package for CM servers would be KB 2907591-server update-Site Code. Click on Next.

Configuration Manager 2012 R2 Hotfixes

Click on Install.

Configuration Manager 2012 R2 Hotfixes

Click Next.

Configuration Manager 2012 R2 Hotfixes

Click on Finish.Configuration Manager 2012 R2 Hotfixes

Launch the Configuration Manager 2012 R2 console, click on Software Library, expand Overview, expand Application Management, expand Packages and click on Configuration Manager Updates. On the right hand side of console you will see the packages that were created by this hotfix. In the below screenshot we see a new package KB 2907591 – server update-IND has been created.

Configuration Manager 2012 R2 Hotfixes

After the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix is applied, open the Configuration Manager console, click Software Library expand Operating Systems, and then click Boot Images, select the boot image that you want to update, right-click and then select the Update Distribution Points action.

  • SK

    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.

  • Reza Prawirasatya

    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

  • Jeremy Densmore

    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

  • Rohan Malhotra

    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.

      • Rohan Malhotra

        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.

  • Arno

    Hi,

    These Hotffix are included in SCCM CU4 ?
    If I install CU4 after installation of server, it replace the Hotflixe that you speak ?

    Thanks

  • boris boris

    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.