locked
SCCM 2012 migration to SCCM 1602 RRS feed

  • Question

  • I am still running SCCM 2012 and would like to directly upgrade to 1602. I have 1 primary site and several secondary sites.

    Here's my high level upgrade steps - is this correct?

    1. upgrade my primary to 1511 and then immediately apply 1602 from console. apply Update Rollup for 1602 (kb3155482).

    2. upgrade my secondary sites to 1511 from console and then immediately apply 1602 from console. Apply Update Rollup for 1602 (kb3155482)

    3. Upgrade my clients directly to 1602.

    Just to confirm I do not have to upgrade the clients to 1511 first and then 1602? Do i need to apply Update Rollup for 1602 (kb3155482) on the clients?

    Thanks

    Thursday, July 21, 2016 7:33 PM

Answers

  • Simon is correct although that's not what I said. I said skip the post 1602 *hotfix*, not 1602. Now that 1606 is out though this is a moot point as there's no reason to even install 1602.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, July 23, 2016 7:00 PM

All replies

  • I am still running SCCM 2012 and would like to directly upgrade to 1602. I have 1 primary site and several secondary sites.

    Here's my high level upgrade steps - is this correct?

    1. upgrade my primary to 1511 and then immediately apply 1602 from console. apply Update Rollup for 1602 (kb3155482).

    2. upgrade my secondary sites to 1511 from console and then immediately apply 1602 from console. Apply Update Rollup for 1602 (kb3155482)

    3. Upgrade my clients directly to 1602.

    Just to confirm I do not have to upgrade the clients to 1511 first and then 1602? Do i need to apply Update Rollup for 1602 (kb3155482) on the clients?

    Thanks

    You don't need to update the Clients to 1511 first. A 2012 Client can talk with a 1511/1602 Site, but that Scenario is not supported for a long time usage.

    The Rollup is also available for the Clients if I'm not mistaken. You would need to check the Bugs which were fixed, to decide if you need to install it. Usually you only apply Hotfixes if you have a specific issue which will be fixed by this Hotfix.

    You can also wait for 1606 which should be released anytime by now.


    Simon Dettling | msitproblog.com | @SimonDettling

    Thursday, July 21, 2016 7:52 PM
  • Yep, skip the post 1602 hotfix. 1606 will be out "soon".

    Jason | http://blog.configmgrftw.com | @jasonsandys


    Friday, July 22, 2016 12:28 AM
  • So I can go straight to 1606 from 1511? Once its released?

    Thanks
    Friday, July 22, 2016 7:28 PM
  • It actually was released yesterday and yes 1511 directly to 1606 does work. 

    You need to run the following PowerShell Script for now, to opt in to the Fast Ring to see the 1606 Update in the Updates & Servicing Node, as the Update is being released in waves. 

    https://gallery.technet.microsoft.com/ConfigMgr-1606-Enable-043a8c50


    Simon Dettling | msitproblog.com | @SimonDettling



    Saturday, July 23, 2016 2:44 PM
  • Simon is correct although that's not what I said. I said skip the post 1602 *hotfix*, not 1602. Now that 1606 is out though this is a moot point as there's no reason to even install 1602.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, July 23, 2016 7:00 PM
  • What about ADK? Can I first install ADK 1607 then upgrade ConfigMgr 2012 R2 SP1 to CB 1511 and then directly to CB 1606?

    Friday, August 5, 2016 7:08 AM
  • There is not yet an official Statement about the Support of the ADK 10 1607 with ConfigMgr CB.

    Simon Dettling | msitproblog.com | @SimonDettling


    Friday, August 5, 2016 9:07 AM
  • Hi had a quick question. Do I need to apply 1511 to my primary and secondary sites first and then I can only apply 1606?

    I have upgraded my primary site to 1511 but having a hard time upgrading it to 1606. But at this point I havent upgraded my secondary sites yet to 1511. I would like to upgrade the primary to the latest version and then upgrade secondary sites a week later to 1511 and then 1606.

    Friday, August 5, 2016 6:27 PM