locked
Upgrade RRS feed

  • Question

  • Hi,

    We are planning to upgrade our SCCM 2012 version 1606 to the latest version 1909. Currently SCCM is installed on a Windows 2012 R2 OS.

    As part of the upgrade plan first we will upgrade from 1606 to 1706.Pre requisite check for the upgrade is completed successfully.As part of the upgrade i believe all the SCCM clients will be upgraded to the latest version. Please note that we have removed the SCCM service account from all local administrators from all the servers which has the client installed.

    My query is does upgrading the SCCM client require local administrator permissions or we should be able to upgrade the clients without local admin permissions.

    Also we need to upgrade the Operationg system of the SCCM server from Windows 2012 to Windows 2019. Have few queries on this.

    Is it a good idea to first upgrade the SCCM server from 1606 to 1909 and then do an in place upgrade of the OS from Windows 2012 to Windows 2019 or to first upgrade the OS to Server 2019 and then upgrade the SCCM Server

    What will be the impact of doing an in-place upgrade of the OS from Windows 2012 r2 to Windows 2019 on the SCCM application.

    Any advise on the above will be appreciated

    Tuesday, December 10, 2019 7:34 AM

Answers

All replies

  • For SCCM client upgrade local admin access is not required, If you enable automatic client upgrade in the hierarchy settings, a system task will create on client machine and upgrade will happen with the time period. But if you want to do client push again, it required local admin access.

    there are some prerequisites for in-place upgrade, i would recommend to perform in-place OS upgrade to 2019 and proceed with SCCM in console upgrade

    https://docs.microsoft.com/en-us/configmgr/core/servers/manage/upgrade-on-premises-infrastructure

     
    Tuesday, December 10, 2019 8:05 AM
  • Thank kalyan for your advise appreciate it. Also can you please confirm if SQL Server 2012 SP1 is supported for the new SCCM version 1909
    Tuesday, December 10, 2019 8:10 AM
  • Also is SCCM 2012 version 1606 supported on 2019 Server, if we do the OS upgrade first
    Tuesday, December 10, 2019 8:29 AM
  • SQL 2012 is supported, however, kindly upgrade to SP3. https://docs.microsoft.com/en-us/configmgr/core/plan-design/configs/support-for-sql-server-versions

    Since SCCM 1909 is supported for Windows server 2019, you can upgrade the SCCM first and perform OS upgrade.

    Sorry for the previous update, SCCM 1606 may not support Server OS 2019.

    • Marked as answer by wasif kazia Tuesday, December 10, 2019 9:26 AM
    Tuesday, December 10, 2019 9:13 AM
  • In addition, following SCCM 1910 step-by-step upgrade:

    https://www.prajwaldesai.com/sccm-1910-step-by-step-upgrade-guide/

    PS: You need at least SCCM 1806 to upgrade to the latest SCCM version (1910).

    Please note that there is no SCCM 2012 1606 version, 1606 is a Current Branch version and has nothing with SCCM 2012. SCCM CB 1606 is no longer supported, you have to upgrade as soon as possible.

    Regards,

    Youssef Saad

    ______

    Please remember to mark the replies as answer if they help, thank you!





    • Proposed as answer by SAAD Youssef Tuesday, December 10, 2019 10:08 AM
    • Edited by SAAD Youssef Tuesday, December 10, 2019 10:11 AM
    Tuesday, December 10, 2019 10:03 AM
  • Thanks Kalyan for your advise. Appreciate your help
    Tuesday, December 10, 2019 11:01 AM
  • SCCM 2012 version 1606

    1606 is not a version of ConfigMgr 2012, it's a version of Configuration Manager which is the successor product to ConfigMgr 2012 and is often referred to as ConfigMgr Current Branch.

    to the latest version 1909

    1909 is a version of Windows, not ConfigMgr. The latest ConfigMgr version is 1910. To get to 1910, you will to need to upgrade to 1706 then 1806 and then finally 1910.

    As part of the upgrade i believe all the SCCM clients will be upgraded to the latest version.

    No, this is not correct. The client agent is only upgraded automatically if you enable auto upgrade. There is no specific reason to do this immediately when upgrading to additional versions.

    My query is does upgrading the SCCM client require local administrator permissions or we should be able to upgrade the clients without local admin permissions.

    As Kaylan noted, no, local admin is not required if you use client auto upgrade.

    > Also we need to upgrade the Operationg system of the SCCM server from Windows 2012 to Windows 2019. 

    Not for ConfigMgr no. While this is probably a good idea, it's not required.

    Is it a good idea to first upgrade the SCCM server from 1606 to 1909 and then do an in place upgrade of the OS from Windows 2012 to Windows 2019

    This is not possible because ConfigMgr 1606 does not support Windows 2019. You need to upgrade ConfigMgr first and then perform an in-place OS upgrade. Alternatively, you can upgrade ConfigMgr first and then perform a site back and restore it to a new system running Windows Server 2019.

    What will be the impact of doing an in-place upgrade of the OS from Windows 2012 r2 to Windows 2019 on the SCCM application.

    None, this is fully supported. As noted though, some folks avoid in-place OS upgrades and so performing a site backup and restore is an alternative options that works quite well.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, December 10, 2019 2:09 PM
  • Hi,
     
    Thanks for your marking. To make our thread clear to read, here is a short summary for it.
     
    Problem/Symptom:
    ===================
    1. Does upgrading the SCCM client require local administrator permissions or we should be able to upgrade the clients without local admin permissions?

    2. Is it a good idea to first upgrade the SCCM server from 1606 to 1909 and then do an in place upgrade of the OS from Windows 2012 to Windows 2019?

    3. What will be the impact of doing an in-place upgrade of the OS from Windows 2012 r2 to Windows 2019 on the SCCM application.

    Suggestions:
    ===================
    1. No, it is not required. When we enable automatic client upgrade, the upgrade will happen.

    2. Since ConfigMgr 1606 is not support Windows server OS 2019, so we can upgrade ConfigMgr first and then do an in place upgrade for the OS.

    3. No, it has no impact.

    Best Regards,
    Tina

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

    Wednesday, December 11, 2019 2:13 AM