Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Enterprise Mobility»Configuration Manager»Installing SCCM 2012 SP2/R2 SP1 – Quick Start Guide

    Installing SCCM 2012 SP2/R2 SP1 – Quick Start Guide

    12
    By Ronni Pedersen on May 16, 2015 Configuration Manager, Enterprise Mobility

    Introduction

    Installing this service pack is very similar to previous service packs and CU updates but there are a few things you should be aware of. In this blog post, I’ll walk you through the upgrade process step-by-step in a SCCM 2012 R2 standalone primary scenario.

    As always, you should start by checking the health of the system, verify the backup, etc.

    At a minimum, you should check the following:

    • Install any missing updates (security, critical and important).
    • Verify you don’t have a pending restart.
      • https://gallery.technet.microsoft.com/Get-PendingReboot-Query-bdb79542
    • Verify that you have a valid SQL backup.
      • Guide: https://stevethompsonmvp.wordpress.com/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/
    • Test that the site database can be upgraded (Setup.exe /TESTDBUPGRADE)
    • Verify that the current installation of ConfigMgr is healthy.
    • Verify that ConfigMgr 2012 R2 has been installed.
    • Verify that Windows ADK for Windows 8.1 is installed.

    Download the update

    After we have checked that the system is healthy, we need to download the update. SCCM 2012 SP2 / R2 SP1 is available for download here: https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-2012-r2-configuration-manager-and-endpoint-protection.
    The only version available today is the “Evaluation version”, but Microsoft doesn’t make dedicated Eval editions of Configuration Manager, so if you plan to upgrade an existing environment, you should be just fine using this version.

    This update can be applied directly to the following Systems/Roles:

    • The Central Administration Site (CAS)
    • Primary Site
    • Secondary Site
    • SMS Provider
    • Configuration Manager Console

    Update the Site Primary Site Server

    To start the installation, log on to the Primary Site Server and run “Splash.hta “. The default settings should be ideal for most customers.

    Note: You can follow the installation process in the “C:\ConfigMgrSetup.log” file.

    clip_image001

    On the Welcome Screen, click Install.

    clip_image003

    Review the “Before You Begin” Page and click Next.

    clip_image005

    On the Getting Started page, verify that “Upgrade this Configuration Manager site” is selected, and click Next.

    clip_image007

    Accept the license terms and click Next.

    clip_image009

    Accept all the license terms for the additional software and click Next.

    clip_image011

    On the Prerequisite Downloads, click Browse, and specify the path where you want to save the prerequisite files. Click Next.

    clip_image013

    Grab some coffee while the updated files are downloading.

    clip_image014

    On the Server Language Selection page you should just accept the default settings. Since this is an upgrade, your existing configuration should be the default selection. Click Next.

    clip_image016

    That’s also the case for the Client Language Settings, so just accept the default selection, and click Next.

    clip_image018

    Hey… It looks like we’re finally ready to get this thing started… Click Next.

    clip_image020

    Well… Almost. First we need to make sure that our system is healthy and is ready to upgrade. In my case I’m a little low on memory, but since this is my test lab with less than 10 clients, I’m really not worried, so I’ll click Begin Install.

    clip_image022

    On the Upgrade page, make sure to click “View Log”. This will open the setup log file and allow you to monitor the process as we move forward.

    clip_image024

    As promised… Much more fun in here Smiley

    clip_image026

    Finally the upgrade is complete (In my lab, it took 49 minutes) and so far everything looks great. Looking in the log file we can see that the process is complete, but the UI is not always (rarely) updated when the Upgrade is complete. After reviewing the log file, click OK.

    clip_image028

    Verify that the setup was successful

    After the setup is complete, there are a few things you can and should do to verify that the setup was successful.

    The first thing you should do is check the log file. But if you followed this guide, you have already done that. Smiley

    The next thing you should do is Launch the System Center 2012 R2 Configuration Manager Console directly on the Site Server and verify the build number of the console. If the upgrade was successful, the build number should be 5.0.8239.1000.

    Also note that you can now see the version number of the site server here too.

    clip_image030

    If you right-click and select “Properties” of the Primary Site to check the version number, you will notice that the build number is 5.00.8239.1000 (R2 SP1 RTM).

    clip_image031

    An overview of all versions and build numbers can be found here: https://www.ronnipedersen.com/2014/07/configmgr-2012-versionbuild-numbers/

    For additional verification, you may also check the CULevel registry data under HKLM\Software\Microsoft\SMS\Setup\. If the upgrade was successful, the value should now be “0”.

    clip_image033

    Updating Clients

    You can upgrade the clients using many different methods, but in this example, I’ll go for the Automatic Client Upgrade feature. Since this is a very small lab, I’ll set the maximums days to 1.

    If you want to learn more about this feature and how it works, you should check out this blog post:
    https://www.ronnipedersen.com/2014/08/sccm-2012-how-does-automatic-client-upgrade-work/

    clip_image034

    Monitoring the client upgrade process

    There are many ways to monitor the client upgrade process, but I prefer to use the built-in report that shows the count of System Center Configuration Manager Clients by Client Version.

    clip_image036

    That’s it…

    Next week, I’ll start to upgrade customers to this new Service Pack. As I move along and learn more, I’ll update this post with my newfound knowledge.

    Until next time….

    +Ronni Pedersen

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Speaking at Nordic Virtual Summit

    Workplace Ninja User Group Denmark February Meetup

    Speaking at Modern Endpoint Management Summit 2022

    12 Comments

    1. Torsten on May 17, 2015 08:04

      I would definitely run setup.exe /testdbupgrade before kicking off the installation of the SP.

      Reply
      • Ronni Pedersen on May 17, 2015 12:56

        Oh yes!
        That’s part of the “Verify that the current installation of ConfigMgr is healthy” step 🙂
        I did think about going through all the steps in details, but rand out of time.
        If I get enough time next week, I might do it 🙂

        Reply
    2. Kenneth on June 15, 2015 19:58

      I would wait upgrading clients til somebody have figured this one out
      https://social.technet.microsoft.com/Forums/en-US/90ead8bd-9f13-40f4-999d-e7aca1b78156/sccm-2012-r2-sp1-after-upgrade-clients-no-certificate-sms-provider-error?forum=configmanagergeneral

      I have the same errors after an otherwise uneventfull upgrade.

      Reply
    3. Tony on July 17, 2015 20:56

      Could you post how you would create a packageprogram to upgrade the client instead of the automatic process?

      Reply
    4. Vaalu on July 23, 2015 13:31

      Hi,

      Good article. i have tested with my lab & ran setup.exe /testdbupgrade, it ran successfully. but in setup setting “Upgrade this Configuration Manager Site” is grayed out. its not enable. I searched for solution, but i unable to get it.
      Please give me your suggestion.

      Reply
    5. Jorin on August 17, 2015 12:51

      When I run splash.hta I only get 1 empty window. No install button for me, how can I fix this?

      Reply
      • Jorin on August 17, 2015 13:03

        extracting the files at the server itsself fixed the issue.

        Reply
        • Ronni Pedersen on August 17, 2015 16:19

          Thanks for sharing the solution/fix here 🙂

          Reply
      • Ronni Pedersen on August 17, 2015 16:18

        Sounds like an explorer or browser problem. Never seen that before. Try to run the hta as an Admin.

        Reply
    6. Jorin on August 18, 2015 09:30

      After installing SP1 should I also install Cumulative Update 1 (CU1)?

      Reply
    7. SteveB on October 9, 2015 09:05

      Just upgraded my sites with SP2 – had to upgrade secondary sites from primary site as running from splash.hta gave no option to upgrade. Otherwise went smoothly. Applied CU1 afterwards with no issues.

      Reply
    8. Matt on October 21, 2015 01:32

      I have looked everywhere and cannot find anyone else having this problem:

      I am trying to install SCCM 2012 SP2 from scratch before upgrading to SCCM 2012 R2 SP1. All pre-reqs are in place but the pre req checker flat out fails every time it checks for ADK 8.1. I have uninstalled and re-installed, re-downloaded from Microsoft but no matter what I’ve tried, it still fails on USMT, Deployment Tools and Windows Pre-installation environment checks. its ADK 8.1 version 8.100.26866, I can’t find any previous versions in case it’s the build that’s broken and I really don’t want to rebuild the server from scratch..
      I’m installing SCCM on a separate drive to C: and in an SQL instance. It is a standalone primary site all on the same server. I have the no sms drive files on all drives except the one I want it to be installed on. I honestly have no idea what’s wrong with it.

      Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • Setting OSDComputerName using CustomSettings.ini
    • Find the TimeZoneName for your SCCM/MDT Deployments
    • SCCM 2012 R2: Where is the SMSTS.log located?
    • SCCM: Failed to Get Client Identity (80004005)
    • Updating the Windows Update Agent on Windows 7 clients
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.