Advertisement

Download and Upgrade SCCM 2012 R2 SP1 and SCCM 2012 SP2 without any Confusion

Microsoft has released SCCM 2012 R2 SP1 and SCCM 2012 SP2. Now you can download and upgrade your SCCM 2012 and SCCM 2012 R2 infrastructure servers to SCCM 2012 SP2 and SCCM 2012 R SP1. In this post, I’m trying to explain the difference between two installers available for SCCM 2012 SP1 and R2. It seems most of the people (including me) are getting confused about which installer needs to be used to upgrade the existing SCCM 2012 SP1 or R2 environment.

SCCM 2012 SP2-2

Before start downloading the SCCM 2012 SP2 installer files (SC2012_SP2_Configmgr_SCEP.exe, SC2012_R2_SP1_Configmgr.exe), you need to understand which installers are actually needed for your existing SCCM 2012 SP1 or R2 environment. You don’t need to download the installer SC2012_R2_SP1_Configmgr to upgrade SCCM 2012 R2 to SCCM 2012 R2 SP1. Rather you may need to download the SC2012_SP2_Configmgr_SCEP.exe. So, the binaries of SCCM 2012 SP2 and SCCM 2012 R2 SP1 are same. More details about this topic is available here in Jason’s post.

So, what is the reason for having SC2012_R2_SP1_Configmgr.exe (1,128 KB) installer? If you’re a SCCM 2012 SP1 customer and you don’t have R2 features enabled. Now, you are planning enable R2 features then you need to download and install SC2012_R2_SP1_Configmgr.exe.

SCCM2012R2-SP1

Johan had tweeted about the confusing error if you download and install “SC2012_R2_SP1_Configmgr.exe” in your existing SCCM 2012 R2 environment.The funny error is “To run this software, the computer must run System Center 2012 Configuration Manager with Service Pack 2.

Download SC2012_SP2_Configmgr_SCEP.exe (780,310) from here.

Download SC2012_R2_SP1_Configmgr.exe (1,128 KB) from here.

More details about the new Features and improvements of SCCM 2012 R2 SP1 and SP2 are available in technet documentation.

Also, More details about strategy behind SPs (Service Packs) for SCCM (ConfigMgr) is explained here.

About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: ConfigMgr (SCCM)

8 Comments

  1. Shilpy says:

    Hi Anoop,

    Thanks for the detailed post. Can you please clarify when I try to download it says eval period 180 days? We have SCOM 2012 R2 in our environment.

    Thanks,

  2. vm8x says:

    I believe the information in this post is wrong. For correct information check http://blog.configmgrftw.com/service-pack-madness/

  3. HI , I got your url from below blog post

    , I was reading “After sccm sp1 install – SMS notification server component critical with BGBISAPI.msi could not install”

    I am facing the same issue with SCCM 2012 R2 …. Bad Luck 🙁 …. I would greatly appreciate if you could help me in this …

    Thanks .

    Sajan Nair

    • Anoop says:

      Probably you can try to search the MSI log file with the string “return value 3”. Few lines above this string you may get the exact reason for failure.

  4. Thalha says:

    Hi Anoop

    I got a question. Our environment is running SCCM 2012 SP1(Both CM & Primary Site). I need to upgrade to version SCCM 2012 R2 SP1. So should I need to upgrade from SCCM 2012 SP1 to SCCM 2012 SP2 (running SC2012_SP2_Configmgr_SCEP.exe) and then run the R2 upgrade (running SC2012_R2_SP1_Configmgr.exe)?

  5. Yaser says:

    Thalha, the steps you mentioned is right.

  6. Ritesh Aggarwal says:

    I am upgrading SCCM 2012 SP1 CU5 to SCCM 2012 R2 SP1 CU2. Is it possible to upgrade the SCCM Client agent on workstations using any SCCM Client Patch, as it is not created by default after the upgrade. When I created it manually and tried the deployments for hotfix KB3100144, it throws an error code 1642 that related product is not installed. When I tried client Install for one machine, it successfully upgraded the client version.
    Is there any other method for upgrading the client agent instead of FULL client upgrade like using patch (.msp).

Leave a Comment and Contact Anoop