Thursday, May 22, 2014


Upgrade for System Center 2012 Configuration Manager to Cumulative Update 1

Upgrading Central/Primary Server

  • Ensure all sites in the hierarchy run System Center 2012 Configuration Manager with R2.
  • Ensure the computing environment meets the supported configurations that are required for upgrading to System Center 2012 R2 Configuration Manager CU1.
  • Review the site and hierarchy status
  • Disable database replicas for management points at primary sites.
  • Back up the site database at the central administration site and primary sites.
  • Disable all site maintenance tasks at each site for the duration of that site’s upgrade.
  • Close an open Configuration Manager console before the upgrade. The installation process cannot upgrade an open console.
  • Run the Upgrade on the Primary Site to verify the prerequisite checks:
    • Verifying update applicability
    • Verifying Restart is not required
    • Verifying no active Configuration Manager Console is open
    • Verifying SQL connectivity

  • The update automatically upgrades the database
  • To manually update a site database, use SQL Server Management Studio to connect to the site's SQL Server, and then run the update script named update.sql on that site's database. When the update bundle installs, it extracts update.sql to the following location on the site server:

\\<Server Name>\SMS_<Site Code>\Hotfix\<KB Number>\update.sql.

Post Upgrade Activities

Automatic actions: Post upgrade the below actions are triggered automatically
  • To complete the Upgrade successfully the server needs to be rebooted.
  • The site performs a site reset, which includes a reinstallation of all site system roles.

Manual actions for the administrative user after an upgrade:

  • Distribute content for the new Configuration Manager client packages
  • Ensure that clients that are assigned to each primary site upgrade and install the client software for the new version.
  • Upgrade each Configuration Manager console that connects to the site and that runs on a computer that is remote from the site server.
  • At primary sites where the database replicas for management points runs, reconfigure the database replicas for System Center 2012 R2 Configuration Manager CU1. 

Upgrading Secondary Server

  • Ensure all Secondary Server are on SCCM 2012 R2
  • Review the site and hierarchy status and verify that there are no unresolved issues.
  • Disable all site maintenance tasks at each site for the duration of that site’s upgrade.
    • Backup Site Server
    • Delete Aged Client Operations
    • Delete Aged Discovery Data
  • It is advices to reboot every server post update installation.

Upgrading Client
  • Installation of the Update Bundle on the Primary creates packages for Client upgrade
  • The packages can be deployed to collection across environment.
  • The client updates can also be installed manually on individual clients

msiexec.exe /p \\<ServerName>\SMS_<SiteCode>\Hotfix\<KB Number>\Client\<Platform>\<msp> /L*v <logfile>REINSTALLMODE=mous REINSTALL=ALL

SCCM 2012 R2 Client Version 5.00.7958.1000

SCCM 2012 R2 CU1 Client Version 5.00.7958.1203

Cumulative Update 1 for SCCM 2012 R2

The redirecting page will be displayed and immediately replaced by “”. With this zero-delay, many users will not even notice the presence of the redirecting page.

Download and extract the CU1 for SCCM 2012 R2 from below location:

Run CM12-R2CU1-KB2938441-X64-ENU.exe with administrative rights.
Follow the default installation as per the screenshots below.

Prerequisite Check:

SCCM 2012 R2 Console update:

Updating Site Database: 

Update package Creation for Site servers, Console and Clients

Package for Site Servers:

These packages are created under Software Library>Application Management > Packages> Configuration Manager Updates

Package for SCCM 2012 R2 Console update:

Package for SCCM 2012 R2 Client:

Setup Summary

Install Process:

Installation logs can be found at: C:\Windows\temp\CM12-R2CU1-KB2938441-X64-ENU.log

Successful Completion of installation:

  • The CU1 requires a mandatory reboot.
  • The reboot is not a force reboot.

Below are the packages added automatically after the CU1 upgrade.
These packages can be used to deploy to all servers and clients