SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

Let’s check SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr. In this post (SCCM 2012 to CB upgrade checklist), you will see the steps to upgrade SCCM 2012 to SCCM CB’s latest baseline (1606) and then Latest Baseline to the latest version of CB (1610/1702). SCCM 2012 to CB 1606 up-gradation is a very critical process for all organizations. Windows 10 1607 support is the trigger for this upgrade process.

We need to plan this in a very detailed manner to complete the upgrade without any impact. I would recommend conducting end to end analysis and study of the existing SCCM 2012 environment before the start of the upgrade process. Also, we need to make sure that your environment has a minimum supported version of SCCM 2012 to start the in-place upgrade. This post contains 2 phases, please check it out!

Step by Step Guide to Perform SCCM ConfigMgr Server Hardware Migration here.

SCCM 2012 to CB upgrade checklist SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

5 Phases of ConfigMgr Migration

SCCM/ConfigMgr CB upgrade process is the best opportunity to redefine your SCCM architecture. If you have CAS and SCCM hierarchy then this is the best chance to remove the CAS server. In this post, we are going to see the unofficial checklist of SCCM 2012 to CB 1606 upgrade (phase 1) and CB 1606 to 1610 in console upgrade (phase 2). This will be a helping hand to plan the entire upgrade process for your organization. Take a FULL backup of SCCM 2012 CAS/Primary servers before the start of the migration/upgrade activity. I would recommend keeping more than one copy of the backup.

Supported SCCM/ConfigMgr CB Upgrade path is explained in following TechNet documentation here In-place upgrade paths.

Phase 1 – Upgrade SCCM 2012 CAS or Standalone Primary Server to SCCM CB

Check the Firewall communications between CAS and Primary servers. The important point is that we need to make sure all the Firewall ports are opened. The upgrade requires the same set of Firewall communications that are required for new SCCM hierarchy installation. I made this as first in the checklist because there could be multiple teams involved in this process and it may take a long time than you expect. More details here and here.

1E Nomad
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

2. Check whether your SCCM/ConfigMgr 2012 infrastructure servers are meeting the minimum hardware requirements of SCCM/ConfigMgr CB 1606. More details here.

SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

3. Check whether CAS, primary servers, SQL, Secondary, and SUPs/MPs are meeting minimum OS requirements of SCCM CB 1606. The very minimum server OS requirement for SCCM/ConfigMgr CB 1606 is Server 2008 R2 SP1 or Server 2008 SP2. More details here. Important to note is that we have a requirement for later versions of Server OS (server 2012) for Windows 10 servicing. This is because of WSUS 4.0 dependency. The best approach would be to upgrade SCCM/ConfigMgr 2012 to SCCM CB 1606 in phase 1 and then perform server OS in-place upgrade once you are in SCCM CB 1606.  

SCCM 2012 R2 Upgrade CheckList SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

4. Check whether SQL server versions (for CAS, Primary and secondary servers) are meeting the minimum requirement of SCCM/ConfigMgr CB  1606. Minimum SQL versions are SQL Server 2008 R2 SP3 – Standard, Enterprise, Datacenter. More details here. Following is the SQL query which you can use for checking the server versions.

SELECT @@VERSION AS 'SQL Server Version'
SQL Server Version (After SP3 upgrade)
 Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)   - Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
SQL Server Version (Before SP3 upgrade)
 Microsoft SQL Server 2008 R2 (SP2) - 10.50.4297.0 (X64)   - Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

5. Run Microsoft Software Updates on the servers and make sure all the SCCM/ConfigMgr servers are up to date with patching. All the critical updates should be installed on the server OS.

6. Download the source files of SCCM CB 1606, along with all the other prerequisite applications like the latest version of Windows 10 ADK. More details here and here.

7. Uninstall the SCCM/ConfigMgr 2012 site system roles like Out of Band Management point and Service Health Validator point before the prerequisite checks.

8. If you have MP replicas on SCCM/ConfigMgr 2012 environment, you should disable Database replicas. Also, reconfigure software update points that use NLBs and Disable all site maintenance tasks.

9. Make sure the Primary server admin who is running prerequisite checks and performing the actual upgrade process must be part of the local admins of CAS and CAS SQL. Also, they must have FULL admin access on SCCM and should SQL admin access.

10.  Run the prerequisite checker – a couple of days before the scheduled upgrade – Ignore errors related to the AI license and some warnings like unsupported site system roles. More details here.

prereqchk.exe (<ConfigMgrInstallationPath>\BIN\X64)

As part of the Prerequisite check, I would recommend adding one more verification step to avoid the following issue during the upgrade process “Prerequisite Downloads – Use previously downloaded files- An error has occurred while attempting to download or verify required prerequisite components and setup cannot continue”. More details here (Authenticode Signature error).

11. You may get false warning messages during the prerequisite checks about unsupported OS for Primary, MPs, SUPs. Check and confirm that we have supported OS versions for Primary, MPs, SUPs. Following is the warning that you can ignore once you complete the proposed checking. Minimum OS version should server 2008 SP2 or later or Server 2008 R2 – Most of them can be safely ignored.

SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

IGNORE the following errors  on primary server prerequisite checks

CWmiRegistry::WmiOpen: Failed to create key SOFTWARE\Microsoft\SMS.

12. Test the database upgrade process on a copy of the most recent site database backup: the same SQL server can be used with different instance- We can safely ignore the warnings about the production DB impact in case you are running the test DB upgrade on a different instance of same SQL server! More details here.

Setup.exe /TESTDBUPGRADE DBtest\CM_ABC
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

13. Before the start of an upgrade from SCCM 2012 to SCCM CB 1606. Make sure that the servers are restarted. This is to ensure that there is no pending reboot for the server.

14. Keep calm and SCCM/ConfigMgr 2012 upgrade to SCCM CB 1606 can take hours to complete (depending upon DB size, the hardware configuration of the server, etc…). I have seen primary servers are going to take double time as CAS servers.

15. Make sure all the standalone SCCM/ConfigMgr 2012 console instances have been upgraded to SCCM/ConfigMgr CB 1606 console version.

SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr
SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr

Phase 2:- Upgrade SCCM CB 1606 CAS or Standalone Primary Server to SCCM CB 1610

  1. Check whether the SCCM/ConfigMgr CB 1606 console is getting the latest update in updates and servicing node. Make sure that you have an exception set on your proxy server to download the latest version of SCCM/ConfigMgr CB. More details here.
  2. If you have SCCM/ConfigMgr CB CAS server then you won’t get the latest updates of SCCM CB in the CAS console until you have upgraded all the primaries to SCCM/ConfigMgr CB 1606. This is because SCCM CB will be in interop mode. More details here.
  3. Make sure that you have checked out SCCM/ConfigMgr CB OSD interop mode documentation to understand the impact of the OSD in your organization. More details here.
  4. Make sure that you have completed the pre-requisite check for the in-console upgrade. Make sure to create a pre-prod collection to test the client upgrade.
  5. Make sure that you have completed the setup of the service window at the primary server so that we can control the upgrade of the SCCM CB primary server from CB 1606 to 1610. I would recommend scheduling this to the date and time which you want to complete the in-console upgrade of the primary server. Otherwise once the CAS is successfully upgraded to 1610 and the package replication is completed then the primary server will automatically start the upgrade process.
  6. Check all the site system status are ok and make sure there are no errors.
  7. Make sure all the boundary groups are ok after the upgrade. More details in this comparison video about boundary group changes here.
  8. Make sure, you plan SCCM/ConfigMgr 2012 clients upgrade to CB 1610 in a phase-wise manner.

Reference Links –>

  • SCCM ConfigMgr CB Flowchart  Update replication here
  • SCCM ConfigMgr CB  Flowchart – Download updates from Microsoft cloud services here

16 thoughts on “SCCM 2012 to CB Current Branch Upgrade | Migration | Possible Issues | ConfigMgr”

  1. Hi Anoop,
    Thanks for this guide.

    Phase 1, #6.
    The second link (here) return this message : Grrrr! I’ve lost the trail to that page.

    Reply
  2. Hi Anoop,
    You don’t mention the version of SCCM 2012 that you are upgrading. Are you suggesting that it’s ok to do this on a straight 2012 or R2 version without first upgrading to SP2/SP1 accordingly?

    I was under the impression that 2012 must be fully patched before upgrading to Current Branch.

    Thanks.

    Reply
  3. upgrage to system center configuratiion manager dated 2-23-17
    the doc says “on Dec 15th, 2016 the baseline media for version 1606 was rereleased to add support for additional upgrade scebaruis, it’s listing system center 2012 R2 configuration manager will upgrade to version 1606
    so no SP would be required

    Reply
    • I have seen that but I could not confirm it because I never tested it myself. I did upgrade of 3 corporate environments but none of them were plain SCCM 2012 rather all were SCCM 2012 R2 SP1

      Reply
  4. Thanks for the great post! We are currently at 1610 with a CAS and Primary. As you briefly mentioned we want to do away with the CAS and move forward with just the Primary. Since Microsoft will no longer be supporting future versions of CM on 2008 server and 2008 SQL, we would like to move to server 2016 with SQL 2014 minimum. With that in mind, is the best way to have the new environment built out parallel to the existing and then slowly move content, DP’s, and then boundaries to the new environment in a controlled manner? Looking for suggestions or best practices etc. Thanks!

    Reply
  5. I am trying to Migrate/Upgrade SCCM 2012 SP2 to Current banch 1802.
    Old server: OS: 2008R2, SQL: 2008R2, SCCM 2012 SP2, WSUS & ADK installed
    New Server: OS: 2016, SQL 2016, SCCM 1802, WSUS & ADK installed/

    Could you please provide me with a step-by-step instructions, how to migrate/upgrade SCCM from my old system to the new and maintain all the data and configuration settings as possible

    Thanks
    MDL

    Reply
  6. Hi Sir,

    We have 1 CAS site and 3 Primary sites running with SCCM 2012 R2 SP2 on all sites
    We are upgrading the environment from 2012 R2 to current branch 2002.
    What should be our approch?

    1. Upgrade CAS site first and wait for other primary site to upgrade automatically?
    Does this approch of automatic upgrade works?
    We dont have to run the splash file manually on none of the primary sites?
    Once we upgrade CAS is it really upgraded other primary sites automatically or we have run the setup on primary site manually?

    Or other approch is

    2. Upgrade CAS to Current branch by running setup/spalsh file
    Once CAS completed go to primary site and run the setup manually.
    Once Primary finishes go on to next primary site and likewise finish the setup of all primary sites.

    Which approch is correct here?

    Thanks in advance for your gudance.

    I must tell you that your blogs are full of knowledge and it shows your persistance in relation to technology.

    Regads,
    MV

    Reply

Leave a Comment

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