As excited as I am to get the call, it's also daunting to listen to the way engineers plan on doing the upgrade. So here I thought I would put together some information on HOW to best get this done the quickest way with as little downtime as possible.

Establish Where to Start

Scenario

Move from a Primary Site Server that is on Server 2008 R2 and SQL Server 2008 R2.

Options:

1. Site Restore (Restoring to New Hardware)
2. Migration to new Infrastructure

In this blog, I will be covering option 1. Site Restore!

Once you recover from the SHOCKED FACE!!!! We can get down to business.

The Needs

The 1^st thing we need to know is HOW to do a restore of 2012 R2 and what's the process! This question will make you go through the mental workflow, ask other questions, and help determine what is the RIGHT workflow. I know I need to RESTORE 1^st because below I LIST WHAT YOU CANNOT DO. And the 1^st thing I mention is you CANNOT restore to a higher version of Configuration Manager.

What you CANNOT do?

• You cannot restore to a higher version of Configuration Manager!
  • Example, you cannot restore 2012 R2 to a higher version of Configuration Manager.
• You cannot restore to a higher version of SQL!
  • Example, you cannot restore SQL Server 2008 R2 to a higher version of SQL Server.

APPLES TO APPLES when it comes to restore.

• Notice above I called out PRODUCT versions NOT Operating System Versions.

What can you do?

• Restore 2012 R2 to a higher Operating System.
  • Example, you can restore Configuration Manager 2012 R2 to a NEWER Operating System.

The Destination

When it's all said and done I want to end up on Windows Server 2012 R2 & SQL Server 2014 and Configuration Manager 1702 with the latest HOTFIX (KB4019926). Below I will explain how and why I choose that as the destination.

What's the Path Forward?

Let's get started

1^st things 1^st, since I know I can't restore to higher levels of SQL or Configuration Manager I need to know EXACT Versions I am on with 2012 R2.

Now:

Now let's figure out what 1702 supports and what 2012 R2 Supports!

Now we know Configuration Manager Current Branch 1702 does not support Windows Server 2008/R2 Operating System nor does it support the SQL Server 2008/R2 we cannot achieve anything from backing up and restoring what we have. Through the process of elimination, we know I need to upgrade 1^st.

So, what to upgrade?

1702 supports what Operating systems and SQL Server?

From this link (https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers) we see 1702 supports Windows Server 2012/R2 & Windows Server 2016 as the Operating System, So we have options for the OS restore right? Windows Server 2012/R2 or Windows Server 2016 (We will narrow this down later). Looking at the SQL Server Version screenshot below 1702 supports SQL Server 2012 up to SQL Server 2016. So, now let me put in a server request for Server 2016 so I can install SQL Server 2016 and Restore Configuration Manager 2012 R2 to it.

WAIT!!!!!!! WAIT!!!!!!! WAIT!!!!!!!

Why Wait you say?

Does Configuration Manager 2012 R2 support Windows Server 2016? NOPE!!!!! (Link). The highest Operating System Configuration Manager 2012 R2 Supports is Windows Server 2012/R2

So, what is the happy medium here?

• Server 2012 R2

We need a Windows 2012 R2 Server for the Operating System! To be clear I need Server 2012 because that's where the overlap between 2012 R2 and 1702 is.

Now for SQL. We need to do the same with the SQL Version (Find the overlap). Now what versions of SQL does 1702 Support (Review the above image)?

SQL Server 2012 to SQL Server 2016!

Obviously, we want to get as HIGH as SQL as possible. Does Configuration Manager 2012 R2 Support SQL 2016?

Why yes it does!!!!!!

But, does Server 2016 Support Windows Server 2008/R2? Nope!

Now back to that Happy medium! SQL Server 2014 is my highest SQL for Configuration Manager 2012 R2 because SQL Server 2014 is supported for Configuration Manager 2012 R2 & Configuration Manager Current Branch 1702.

Supported versions of SQL Server (Configuration Manager Current Branch)

• https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-sql-server-versions

  

Configurations for the SQL Server Site Database

• https://technet.microsoft.com/en-us/library/gg682077.aspx#Configurations for the SQL Server Site Database

  

Why do I care about that? Because Remember from earlier, we need to do an upgrade 1^st.

Now we have "The Path Forward"

• What version of Configuration Manager 2012 R2 Supports SQL Server 2014?
  • System Center 2012 R2 Configuration Manager with a minimum of cumulative update 1
  • 5.00.7958.1203
• Stop all Configuration Manager Services as per the Documentation.

   

  

   

  Before

   

  

   

   

  After (As you can see from this I went a step further to stop & disable the services)

   

  

   

• Upgrade the current Configuration Manager 2012 R2 from SQL Server 2008/R2 to SQL Server 2014.

   

  

   

  

   

  

   

  

   

  

   

  

   

  

   

  

   

  

   

  

   

  

   

  

   

• After the SQL Server version has completed the upgrade, I recommend restarting the server.
• Once the server comes back up I put the services back to the way they were and restarted the server again.

   

  

Part 1 is complete! Upgrade of SQL 2008 R2 to SQL 2014 Complete

In Part 2 we will work through the backup and restore process. We will Destroy this Virtual Machine and restore to Windows Server 2012 R2 and SQL Server 2014.

@SCCMAvenger

Now that we have gotten Configuration Manager 2012 R2 to a point where we can restore the backup to supported version of a higher Operating System and the same SQL version (2014) we can go through the next phase.

As stated before we will be restoring Configuration Manager 2012 R2 to the below specifications

• SQL Server 2014
• Windows Server 2012 R2 (Fully Patched)

Let's Get started

The Backup

Backup Configuration Manager 2012 R2 with the maintenance task built into Configuration Manager

• Copy the backup to a new location
  • In my case, I copied it to a network location on another PC
• Replace the CURRENT Configuration Manager Server (SCACM01)
  • In my case, I just shut off the virtual server and deleted it.
  • I built another VM, gave it the same name (SCACM01) and joined it to the domain (sccmavenger.com).
• The new server that I will restore to will be a Windows Server 2012 R2 (Fully Patched of Course)
  • Also, the server needs to have the SAME FQDN of the prior server (SCACM01)
• Install SQL Server 2014
  • After the install of SQL Server 2014, go ahead and run Windows Update again. (Until there are no more patches needed.)

Actions External to the Restore Process

2 Key Important things to take note of:

• Install the same ADK you had from the prior server.
• You will need to use a hotfix on the SCCM 2012 R2 Media (See Below)

Hotfix Download and Information:

• Restore fails when the site database uses SQL Server 2014 on a server that is running System Center 2012 Configuration Manager
• https://support.microsoft.com/en-us/help/3020755/restore-fails-when-the-site-database-uses-sql-server-2014-on-a-server

Hotfix Directions:

• Download the Hotfix
• Installation instructions
  • Create a copy of the System Center 2012 R2 Configuration Manager installation media.
  • Run the self-extracting hotfix executable to extract the Prereqcore.dll and Setupcore.dll files.
  • Replace both of the .dll files in the installation folder by using those from this hotfix.

The Restore

Now that the server is up and patched let's go through the restore process.

Make sure the server has the Correct Version of SQL 2014 (Remember from the last step we upgraded SQL Server 2008 R2 to SQL Server 2014).

SQL Server Versions

https://social.technet.microsoft.com/wiki/contents/articles/783.sql-server-versions.aspx

Copy the extracted & HOTFIXED media to the server and open the Splash Application.

When the Splash application opens click install.

Right after "Install" you should be presented with the next few screens throughout the restore process.

Click "Next".

This is where your presented with the restore option.

In this step, I am referencing the backup location from my maintenance task. I copied the backup from the share and back to the new server that I will be restoring configuration manager to.

Select Recover Primary Site.

Yeap, in my case I am using the evaluation.

"Next".

Accept the Licensing Terms.

I predownloaded the files. Here I am just pointing to the location. If you haven't downloaded the files then go ahead and chose the 1^st option and download the files to a location.

This section is prepopulated, though you could change the installed path if desired. in this scenario, I will not be changing anything.

Prepopulated with my database server, name, and Service Broker Port.

Prepopulated with SQL Server data file and transaction log path.

And the restore is complete. Now real world. I like to let this cook for a day are two. Check your site status and components, use the product, make sure it is fully functional before upgrading to Configuration Manager Current Branch. In some cases, after you restore, you might need to apply CU's, are other performance based tweaks, but your Configuration Manager 2012 R2 is restored to a Windows Server 2012 R2 with SQL Server 2014.

Post Recovery

Don't forget the POST restore processes as documented here.

Key things to remember after the restore:

• Re-Enter Sideloading Keys
• Recreate the Microsoft Intune Subscription
• Configure SSL for Site System Roles that Use IIS
• Reinstall Hotfixes in the Recovered Site Server
• Recover Custom Reports on the Computer Running Reporting Services
• Recover Content Files
• Recover Custom Software Updates on the Computer Running Updates Publisher
• User State Migration Data
• Update Certificates Used for Cloud-Based Distribution Points

Thanks for your time and attentiveness.

That is it for Part 2. Job well Done. 1 more step to go.

In part 3 we will in place upgrade our Configuration Manager 2012 R2 to our final resting place of 1706

@SCCMAvenger

So, we have finished the SQL In-Place Upgrade as well as the Backup & Restore to a new Site Server with Windows Server 2012 R2 & SQL Server 2014.

So now the last part – Upgrading to 1702.

Upgrade to Configuration Manager Current Branch 1702

Testing the database upgrade

To upgrade to 1702, we 1^st need to run the /testdbupgrade.

What's /testdbupgrade you say? Well, it's a process to test the actual database upgrade for success or failure, which I call the "Green Light" "Red Light" Check.

This will test the upgrade against the database and give you a sense of security that when you in place upgrade Configuration Manager 2012 R2 the database upgrade will be successful. This step is HUGHLEY recommended and part of the Configuration Manager Upgrade workflow.

Something I see all too often is that engineers try to shortcut the /testdbupgrade process. Either by not doing it or trying to clone systems. In order to do the /testdbupgrade, you need to copy the Configuration Manager database to ANOTHER SQL server that has NOTHING to do with the Configuration Manager Infrastructure. The /testdbupgrade also needs to be on the SAME SQL version that the production database is on. So, don't try to clone the Primary Site Server, don't try to run the /testdbupgrade on the production server. Build another Server OS virtual machine install SQL (same version that on production) and run the /testdbupgrade.

So, Step by Step

1. Build another Server
2. Install SQL 2014
   1. In my case, my SQL Server is 2014 so I install 2014 to run the /testdbupgrade
3. Backup the Production database
4. Restore the Production database the Newly Built Server

    

   

    

5. Execute setup.exe /testdbupgrade CM_P01 (P01 is whatever your site code is. In my case it is P01)

    

   

    

   

    

6. Review the log file ConfigMgrSetup.log for the phrase "Configuration Manager Setup has successfully upgraded the database"

    

   

    

   Once you see the above text/image then you're ready to do the upgrade in production.

    

7. Delete the Newly Built Server

Yeap, I said delete it. There's no need for that server in my case to be used again. With the new Current Branch model, the upgrade process is all in the console and much more simplified than what we did above with the /testdbupgrade.

/testdbupgrade reference link:
Test the Configuration Manager Site Database for the Upgrade
https://technet.microsoft.com/en-us/library/jj865691.aspx#Test the Configuration Manager Site Database for the Upgrade

In-place Upgrade

So now that all that "green light" "red light" stuff is done time to get this upgrade done. The screenshots below show you the step by step of the upgrade process from Configuration Manager 2012 to 1706.

Client Upgrade

Notice that through out the upgraded series I never talked about client upgrade. Now that the upgrade is complete I can tackle the client upgrade. The client upgrade is fully supported from 2012 to 1702. So do not put your clients through two upgrade paths, just save the client upgrade until the infrastructure is up to 1702, then go forth and progress with client upgrade.

Upgrade Complete

Welcome to 1702 and the beginning of the Hybrid Cloud Management. I encourage you to take a look at the console. If you haven't looked into the whats new section of Configuration Manager, WOW, are you in for a treat. Most a lot of customers just know they need to upgrade for Windows 10 deployments but fail to see all the other hard work we have put into the tool. The worst thing you could do is ONLY use this product for a single feature.

This product has ENORMOUS value and potential to manage your On Prem and Cloud infrastructure With every update the Configuration Manager team brings various bug fixes, improvements to several features as well as new features. it's really overwhelming the amount of flexibility this product provides for various different Infrastructure management challenges. Some links below. Thank you for your time in going through this series and I hope you have found a good workflow for your upgrade.

Whats Next

Again thanks for the time reading this upgrade series and more to come soon. In my next few Blogs, I will start to cover Cloud Services and Cloud Integration, and talk about a few other new features and workflows.

@SCCMAvenger