Configuration Manager 2012 R2 Hotfixes

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

1 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)

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

Click I accept these license terms and click on Next.

After the prerequisite check is done click Next.

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

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

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

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

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.

On Setup Summary page click on Install.

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

Click on Finish.

The hotfix setup log file.

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.

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.

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.

Click I accept these license terms and click on Next.

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

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

Click on Install.

Click Next.

Click on Finish.

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.

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.

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?

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 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.