Sunday, 6 October 2013

ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide : Install CU2

Back to main menu

This post describes how to install CU2 for Config Mgr 2012 SP1.

You can download CU2 here (you can also see the list of issues that are fixed by CU2).

Note that CU3 has also now been released. The installation process is the exact same.

You can download CU3 here (you can also see the list of issues that are fixed by CU3).

This is the CU2 installation file. Double-click to launch the executable.

You are presented with information about the update. Note that it is only required to install this on Site Systems (ie run the SMS Provider), CM Consoles and clients (you do not have to install on Distribution Points).

We will install the update on the Primary Site Server. During the process we are prompted to create packages that we can then deploy to other Site Systems, Consoles and clients. Note that this is NOT an automatic process.

Click Next to continue.

Accept the License Terms and click Next to continue.

Verify that all prerequisite checks have passed.

Check the box to install the updates for the Config Mgr console (selected by default).

Choose to "Update the site database".

Select all.

Configure a path for the Server Package.

Configure a path for the Console Package.

Configure a path for the Client Packages.

Review the summary and click Install.

Installation of CU2 has been completed on the Primary Site Server. Now you must deploy the update packages to the other site systems and your clients using traditional Config Mgr deployments.


  1. Hello Gerry,

    I am ruuning sccm 2012 sp1 (without Cumulative updates). can I upgrade directly to CU4 ?
    Thank you

    1. Yes, you can Zax. Why don't you go to straight to R2 though? You don't need a CU for this.

  2. Thanks for your reply Gerry,
    I still have hundreds of XP that I have to refresh to win 7 using sccm 2012.
    I was told that R2 is using Win PE version 5 which does not support XP.
    Thanks again

  3. Halo Gerry....

    First of All. Thank You So Much for the Informative Posts And Helps a lot. :))

    I have a question,

    Start with the Environment Overview:

    Single Forest environment , two domains
    Domain A : New Domain Created with SCCM 2012 R2 installed

    Domain B: Existing Domain with 500 Clients approx


    Created a totally new SCCM 2012 R2 environment in a new domain Domain A.

    OSD , App Deployment , S/W Patching working like a charm. :)

    But there is another requirement by company :

    Company's requirement is to Add Domain B to the SCCM 2012 R2 and manage it the same way as primary Domain A (i.e OSD, App Deployment, S/W Patching)

    But, they are hesitant for the making any changes in the second Domain (i.e AD Schema extension and System Management Container creation)

    Configuration done So far :

    - Added the Domain B to SCCM 2012 R2 , ran Forest Discovery successfully.

    - Have Discovered all the Client Machines in Domain B

    - Configured the Client settings for pushing the Client Agent to Domain B machines

    (Note that the SCCM Client Push Account has domain Admin rights on Domain B)

    But Unable to push Client on Domain B Machines

    Tried to test on 5-10 machines, but apparantely it is failing to create the ccmsetup folder

    due to privillege issue ( I Guess )

    Good thing


    Both MP (Domain A ) and DC (Domain B) can resolve each others DNS successfuly.

    As it is a same Forest, I assume don't have to set any trust relationship.

    So, I want to manage Domain B ( Old Domain Same Forest ) same way I am able to manage Domain A ( New Domain, Same Forest) without making any changes or extending the SCHEMA on Domain B

    Also, Please suggest
    How can I See the second Domain in the Task Sequence....
    While Creating a OSD Task Sequence and Adding the Deployed Machine to any of the Domain ( At the Moment, can see only new Domain )

    Please Help.....!!!!!!!

    Have been struggling with this issue for some days now :(

    Any suggestion would much appreciated...

    SCCM NewBie

    1. You only have to extend the schema once per forest.