SCCM 2012 R2 to SCCM vNext Migration RRS feed

  • Question

  • Team

    We have SCCM 2012 R2 SP1 CU3 infrastructure and are planning to upgrade to SCCM 2016 vNext in next 1-2 months. Below are our SCCM detailed infrastructure.

    OS Platform - Windows Server 2008 R2 SP1

    1 CAS

    2 Primary Site Servers for Servers (Intranet Only) and Workstation Management (Internet and Intranet)

    10000+ Workstations

    800+ Server

    One of the main objective of the migration is to facilitate Windows 10 upgrades across the organization. Since we are on Windows 2008 R2 Sp1 platform, we are using WSUS 3.0 and as per below article there is a dependency for Windows 10 upgrade as it requires WSUS 4.0 for which we need to perform OS upgrade.


    As per the supported configuration for Configuration Manager TechNet article, Configuration Manager does not support "Any version of Windows Server 2008 R2 to any version of Windows Server 2012 or later." This is a challenge.

    We have 2 options-

    Plan A- In Place Upgrade

    Build separate Windows 2012 R2 infrastructure for Site Servers (1 CAS and 2 Primary Site Server), Install SCCM with site recovery option with proper backups. I need the complete documentation here.

    Plan B- Side by Side upgrade

    Build a clean SCCM infrastructure on Windows Server 2012 platform with a different Site Code in parallel with current SCCM infrastructure and migrate all clients phase by phase.

    Please suggest which is the best possible options for our environment.

    Thanks much.



    Gururaj Pai

    • Edited by Gururaj Pai Thursday, January 14, 2016 10:46 AM
    Thursday, January 14, 2016 10:40 AM


All replies

  • I'd go for #B. Main reason: get rid of the CAS and use a standalone primary site instead.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, January 14, 2016 11:08 AM
  • Hi,

    As Torsten said, the Central Administration Site is only needed if you want to manage more than 100.000 clients.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, January 15, 2016 2:41 AM
  • Thanks Torsten.

    Found a great blog on migration here.


    A quick question on setting up source hierarchy. Since we have 1 CAS and 2 Primary site servers and the total number of clients are less than 20,000 we thinking to get rid of the CAS and have only 2 primary sites in future design.

    If we need to achieve this scenario, do we need to migrate jobs under Primary sites? Can you please put some more if my understanding is correct?

    Gururaj Pai

    • Edited by Gururaj Pai Tuesday, January 19, 2016 5:18 AM
    Tuesday, January 19, 2016 5:18 AM
  • All ConfigMgr 2012 objects can be found on each site so you only have to run the migration jobs against the CAS.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, January 19, 2016 6:53 AM