In-place Upgrade to Configuration Manager 1511

27972

In this post we will see the steps for In-place upgrade to Configuration Manager 1511. With the release of Configuration Manager 1511, Microsoft allows you to run an in-place upgrade to configuration manager 1511 from a site and hierarchy that runs System Center 2012 Configuration Manager. Before upgrading from System Center 2012 Configuration Manager, you must prepare sites which requires you to remove specific configurations that can prevent a successful upgrade, and then follow the upgrade sequence when more than a single site is involved. In my previous post I have showed the steps to install Configuration Manager 1511. In this post we will see the steps for in-place upgrade to SCCM 1511. This includes the details about the upgrade paths available, upgrade checklists and the procedure to upgrade to configuration manager 1511. The SCCM 1511 can be downloaded from the Microsoft Evaluation Center, MSDN, and Volume Licensing Service Center.

Here are few links that will help you to understand more about SCCM 1511.

Plan for System Center Configuration Manager infrastructure – Use this information to plan for a new deployment of System Center Configuration Manager 1511.

Recommended hardware for System Center Configuration Manager – Use this information to plan for hardware that can meet the processing loads for clients and sites that use the available Configuration Manager features with the default configurations.

Supported operating systems for sites and clients for System Center Configuration Manager – Use this information to know about the supported OS, Prerequisites for site system roles, for SCCM 1511.

Support for SQL Server versions for System Center Configuration Manager – Use this information to decide which SQL server version you need to install for SCCM 1511.

The below table shows the in-place upgrade paths to Configuration Manager 1511. If you are running any other version of 2012 you must install a service pack before you can upgrade to 1511.

If your current installation is:Your options include:
A fully licensed installation that runs one of the following:

  • System Center 2012 Configuration Manager with Service Pack 1
  • System Center 2012 Configuration Manager with Service Pack 2
  • System Center 2012 R2 Configuration Manager
  • System Center 2012 R2 Configuration Manager with Service Pack 1
In place upgrade to System Center Configuration Manager is supported
An evaluation install of System Center Configuration ManagerIn place upgrade to a fully licensed version of System Center Configuration Manager is supported
A release candidate install of System Center Configuration ManagerIn place upgrade to a fully licensed version of System Center Configuration Manager is supported
Technical Preview for System Center Configuration Manager (any version)It is not supported to upgrade a Technical Preview for System Center Configuration Manager to a fully licensed installation.

It is supported to upgrade certain Technical Preview installations to newer Technical Preview versions. See the documentation for the new preview version for details or limitations.

Migration from a Technical Preview release is not supported

Upgrade checklists

The following check lists can help you plan a successful upgrade to System Center Configuration Manager

  • Ensure that your computing environment meets the supported configurations that are required for upgrading to System Center Configuration Manager.
  • Review the site and hierarchy status and verify that there are no unresolved issues.
  • Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles.
  • Uninstall the site system roles not supported by System Center Configuration Manager.
  • Disable database replicas for management points at primary sites.
  • Reconfigure software update points that use NLBs.
  • Disable all site maintenance tasks at each site for the duration of that site’s upgrade.
  • Run Setup Prerequisite Checker.
  • Download prerequisite files and redistributable files for System Center Configuration Manager.
  • Plan to manage server and client languages.
  • Review considerations for site upgrades.
  • Create a backup of the site database at the central administration site and primary sites.
  • Test the database upgrade process on a copy of the most recent site database backup.
  • Restart the site server and each computer that hosts a site system role to ensure that there are no pending actions from a recent installation of updates or from prerequisites.
  • Upgrade sites starting at the top-level site in the hierarchy and working down (CAS > Primary > Secondary).

Note – When you upgrade a site in a hierarchy, you upgrade the top-level site of the hierarchy first. This top-level site is either a central administration site or a stand-alone primary site. After the upgrade of a central administration site is completed, you can upgrade child primary sites in any order that you want. After you upgrade a primary site, you can upgrade that site’s child secondary sites, or upgrade additional primary sites before you upgrade any secondary sites.

Additional Prerequisites

  1. Windows 10 ADK must be installed. Microsoft says “we do not recommend that Configuration Manager customers use the 1511 version of the Windows 10 ADK”. This means you should continue to use the original release of the Windows 10 ADK, which is supported for OS deployments including Windows 10, version 1511. This older version of the Windows 10 ADK can still be downloaded directly from the Microsoft Download Center: http://download.microsoft.com/download/8/1/9/8197FEB9-FABE-48FD-A537-7D8709586715/adk/adksetup.exe.
  2. Download and install hotfix KB3095113 on your SUP before you start the upgrade. This hotfix enables Windows Server Update Services (WSUS) on a Windows Server 2012-based or a Windows Server 2012 R2-based server to sync and distribute feature upgrades for Windows 10. This hotfix is not required to enable WSUS to sync and distribute servicing updates for Windows 10.

Before we start the upgrade process, you need to perform 2 important steps.

  1. Backup – Before you upgrade a site, back up the site database to ensure that you have a successful backup to use for disaster recovery. Check this post for more info.
  2. Perform test upgrade of DB – Before you upgrade a site, test a copy of that site’s database for the upgrade. You can perform the below steps for testing the upgrade of DB.

Step 1 – Make a copy of the site database, and then restore that copy to an instance of SQL Server that uses the same edition as your site database and that does not host a Configuration Manager site. For example, if the site database runs on an instance of the Enterprise edition of SQL Server, make sure you restore the database to an instance of SQL Server that also runs the Enterprise edition of SQL Server.

Step 2 – After you restore the database copy, run Setup from the source media for System Center Configuration Manager. When you run Setup, use the /TESTDBUPGRADE command-line option. If the SQL Server instance that hosts the database copy is not the default instance, you must also provide the command-line arguments to identify the instance that hosts the site database copy.

For example, you plan to upgrade a site database with the database name SMS_ABC. You restore a copy of this site database to a supported instance of SQL Server with the instance name DBTest. To test an upgrade of this copy of the site database, use the following command line: Setup.exe /TESTDBUPGRADE DBtestCM_ABC. You can find Setup.exe in the following location on the source media for System Center Configuration Manager: SMSSETUPBINX64.

Step 3 – On the instance of SQL Server where you run the database upgrade test, monitor the ConfigMgrSetup.log in the root of the system drive for progress and success. If the test upgrade fails, resolve any issues related to the site database upgrade failure, create a new backup of the site database, and then test the upgrade of the new copy of the site database. After the process is successful, you can delete the database copy.

In-place Upgrade to Configuration Manager 1511

Run the file splash to launch the Setup screen. Click on Install to the begin the Installation.

In-place Upgrade to Configuration Manager 1511

Click on Upgrade this Configuration Manager site and click Next.

In-place Upgrade to Configuration Manager 1511

Accept the license terms for Microsoft SQL Server 2012 Express, SQL Server Native Client and Silverlight 5 and click on Next.

In-place Upgrade to Configuration Manager 1511

Prerequisite Downloads – There are 2 options that we see here.

1) Download required files – Select this option to download the setup prerequisites from Microsoft and you can store them in a folder or shared path.

2) Use previously downloaded files – Select this option if you have downloaded the prerequisites. Browse to the folder where the prerequisites are stored and click on Next.

In-place Upgrade to Configuration Manager 1511Click on Next.

In-place Upgrade to Configuration Manager 1511

Click on Next.

In-place Upgrade to Configuration Manager 1511

Click on Next.

In-place Upgrade to Configuration Manager 1511

On the Settings Summary page, we see the Upgrade under Component Details. Click Next.

In-place Upgrade to Configuration Manager 1511

On the Service Connection Point Setup page, click on Yes, let’s get connected and click Next.

In-place Upgrade to Configuration Manager 1511

Prerequisite Check – The Configuration Manager setup checks whether all prerequisites are installed correctly, if any of the prerequisite is not installed it would be displayed. If all the prerequisites are installed correctly then you will see the message “All prerequisites rules pass successfully“. Click on Begin Install.

In-place Upgrade to Configuration Manager 1511

You need to wait until the upgrade is complete. I observed that not all components are seen with green tick. I had to wait for around 15 minutes to see all the components installed. Click Close.

In-place Upgrade to Configuration Manager 1511

You can view the setup log file with a tool called CMTrace. The tool is located in SCCM 2012 R2 source DVD under SMSSETUP > TOOLS. Launch the CMTrace tool, open the log file ConfigMgrSetup.log located in C drive. You should see a line which shows that setup (upgrade) is completed.

In-place Upgrade to Configuration Manager 1511

After the setup is complete, open the SCCM Console, click on the upper left corner on the blue arrow,  select About Configuration Manager. The Console has version 500.8325.1000 and ConfigMgr Version is 1511. You could also click on Administration > Overview > Site Configuration > Sites > right-click on your site and choose Properties. On the General tab, you will see Version = 5.00.8325.1000 and build number = 8325.

In-place Upgrade to Configuration Manager 1511

The next step is to upgrade the clients. You could make use of Client Upgrade feature which does the upgrade job easy for you. To enable this feature, go to Administration > Site Configuration > Select Sites. Click on Hierarchy Settings and go to the Client Upgrade tab.

In the Client Upgrade tab, click on Upgrade all clients in the hierarchy using production client. Set Automatically upgrade clients within days to 7 (default). Click OK.

The second option that we see is Pre-production client version. For upgrading the Configuration Manager client on Windows PCs and devices, you can test a new client version in a preproduction collection before upgrading the rest of the site with it. When you do this, only devices that are part of the preproduction collection upgraded to the new client. Once you’ve had a chance to test the client in this preproduction collection, you can promote the client, which makes the new version of the client software available to the rest of the site.

In-place Upgrade to Configuration Manager 1511

  • Abu Maryam

    Hi, We have successfully upgraded our SCCM 2to version 1511. We have deployed admin console to several machines within our team. Would you please advice the best practice to upgrade the admin consoles too.
    Thanks

    • Anjan

      Yes you need to upgrade the consoles. Other wise its not possible to access the higher version of the configmgr.

  • testuser

    thank you for the post.

    After you upgrade to sccm 1511

    do the sccm clients needs to be upgraded as well?

    if so after the clients have been upgraded do those clients need a reboot?

    • Yes the client agents needs to be upgraded. No reboot is required after the client agent upgrade. To upgrade the client agents, make use of Automatic Client Upgrade feature.
      Select your Site and select Hierarchy Settings in the top ribbon > Go to the Automatic Client Upgrade tab
      > Check Upgrade client automatically when new client updates are available and press OK in the window that pop ups.

  • testuser

    if you are running sccm 2012 sp1 and it is connected to sql 2008 sp1 you do not need to install any patches or updates correct?

    I did my research and test and i do not believe so but i am running past you 🙂 since you know all about sccm

    • I would say not to install any updates. These Cumulative Updates / Patches can cause issues. If you want to keep the SQL updated, take a complete back up of DB, SCCM server and then test the updates installation.

  • Stretch

    Since the update, Failed to get DP locations as the expected version from MP ‘xxxxxxxxxxxx’. Error 0x87d00215

  • Mehedy Mizan

    for Perform test upgrade of DB, if I have deployed sccm in hyper-v and in that case if i take a checkpoint of my sql server and all sccm servers before i upgrade, will it be safe or do i need to Perform test upgrade of DB any how. ????

  • Andreas Pekker Sof

    Hi Prajwal and thanks for the information. After upgrading to 5.0.8325.1000 the “company resource access” is missing from the compliancy settings in Assets and compliance. The upgrade went smooth- did i miss something?

  • Andreas Pekker Sof

    Hello! after updating to SCCM 2012 R2 1511 (5.0.8325.1000) the “Company Resource Access” in “Assets and Compliance”/Compliance Settings is missing. Any ideas?

  • To do the test upgrade on the database it says you need the same edition of SQL. Does it need to be the same version? For instance my SCCM 2012 uses a SQL 2012 Standard but I have another SQL Server that runs SQL 2008 Standard. If this is just going to be a test I kind of would like to avoid having to build another SQL Server temporarily.

    • If its same version it would be great. If not it’s till okay as far as the SQL version is supported by CM.

  • James Munoz

    Hi, I have already installed the ADK 1511 and just noticed that MS recommends NOT installing it. What would be the best process of going back to the older version? Can I just remove the new one and reinstalled the old version without screwing things up?

  • boris boris

    Hi Prajwal Desai, our SCCM version is 2012 R2 SP1, I’d like to upgrade to 1511, but I cannot find or forgot previously downloaded files path, and then I try Download required files. no show setup type is upgrade screen, please advise, thx.

    Hi, Prajwai, I know what happened, thx.

    • You can download the prereq files on any machine. Once you download copy the folder over to the SCCM server. Then proceed with the upgrade. If you are unable to see the upgrade option, reboot the server and try once.

  • Babu Raju

    Hi Prajwal,

    We are planning to upgrade 1511. In our existing environment(SCCM 2012 R2 SP1) we use SCUP to manage Adobe security patches. Please let us know whether SCUP will work after upgradation to 1511. Also i m not getting licensed setup from Microsoft volume license site, can i use the evaluation version. If i m running the setup it’s not asking for any key.

  • Babu Raju

    Hi Prajwal,
    We are planning to upgrade 1511, our existing environment(SCCM 2012 R2 SP1) we use SCUP to manage Adobe security patches. Please let us know whether SCUP will work after upgradation to 1511. And also help in understanding the pre-requisite KB3095113.

    • Hi Babu Raju, I have not tested this yet. When i will that, i will let you know.

  • chioma Debbie

    Hello Prajwal,

    This article was very helpful to me. i upgraded our SCCM 2012 SP1 to SCCM V1511.
    Will work with it to be sure all is well if not i will run here for help.

    Kudos. will like to find out if your have a facebook group of if you are on twitter.

    i’m very impressed.

  • Hi Craig, I haven’t tested this. I will get back to you with a answer on this. Please wait.

  • The upgrade paths are listed here – http://prajwaldesai.com/sccm-2012-r2-sp1-upgrade-guide/

  • Gordon Barker

    Hi Prajwal, We’re looking to upgrade from SCCM 2012 R2 SP1 to SCCM 1606. I already understand that we’ll need to upgrade to SCCM 1511 first and then to SCCM 1606, but I’m hoping we don’t have to update all our existing console and clients twice to do this. Can you go from SCCM 2012 R2 SP1 client and consoles directly to SCCM 1606 client and consoles?. Don’t want to wait after SCCM 1511 upgrade for clients to update to 1511 before we go to SCCM 1606.

    • That’s correct – You can now upgrade from SCCM 2012 SP2 or R2 SP1 straight to Current Branch 1606 -https://blogs.technet.microsoft.com/enterprisemobility/2016/10/12/configuration-manager-a-progress-update-on-the-current-branch-and-a-new-servicing-branch/

  • Yes you can upgrade sccm 2012 R2 SP1 directly to 1606. I will be coming up with a post on this shortly. If you are licensed to use 1511 then during the upgrade it won’t prompt for entering license key.

    • Javid Farvaz

      Thanks for the reply. we are awaiting for your post about the direct upgrade.

      • I am working on it..

      • query to find out non sccm 1511 client agents –
        select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != ‘5.00.8325.1000’

  • mrmadtech

    Hello,
    I was wondering if, after installing the upgrade on the Primary Site Server, if this will automatically upgrade all Site System Servers within this site. If not, is there a manual way to upgrade the Site System Servers so that we do not loose our two extra Distribution