locked
Upgrade from 2012 R2 to 2016 RRS feed

  • Question

  • Good morning,

    We use Configuration Manager 2012 R2 with only one primary site. We use it for Endpoint, OS and application deployment. When the 2016 version will be available, we would like to install it.

    We don't want to upgrade the 2012 R2 version to 2016. We would like to do a new server and then change the client little by little.

    As I see, we don't need to extend the AD schema because it's already done with 2012 R2 version.

    My question is : Will I have problem to have 2 differents SCCM servers publish in AD ?

    Thank you so much for your help.

    Best Regards

    Wednesday, September 21, 2016 10:56 AM

Answers

All replies

  • No you will not have problem publishing two cm servers is AD. However you might have issues with site assignments if you have overlapping boundaries

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    • Marked as answer by user_007 Friday, September 23, 2016 7:43 AM
    Wednesday, September 21, 2016 11:09 AM
  • Thank you so much for your quick answer.

    Good remark! I had not thought of it. I shall have to separate the boundary as one goes along then.

    Thanks a lot.

    Wednesday, September 21, 2016 11:31 AM
  • "When the 2016 version will be available, we would like to install it"

    You do know that the successor to ConfigMgr 2012 has been out for almost a year now, correct? It's called ConfigMgr Current Branch (CB) and has had three builds released for production use: 1511, 1602, and 1606. Also, there will never be an official version called 2016 either -- a build (mostly likely 1610) will be included with System Center 2016 but there's no reason whatsoever to wait for this.

    Why don't you want to upgrade though? It's a very seamless process.


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


    Wednesday, September 21, 2016 12:05 PM
  • No I don't know.

    I'm doing a test lab and I download Configmgr & SCEP, but it's in technical preview 5 now. It's now already available ?

    Because we would like to do a new server with Server 2016 when it will be available.

    Wednesday, September 21, 2016 12:20 PM
  • ConfigMgr current branch is already available as Jason mentioned. TP5 is just a preview though and has nothing to do with CM CB though.

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

    Wednesday, September 21, 2016 12:26 PM
  • Because we would like to do a new server with Server 2016 when it will be available.

    That doesn't stop you from doing an in-place upgrade today and then a backup and restore to a new site server running Server 2016 when its released *and* supported as a site server by ConfigMgr.

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

    Wednesday, September 21, 2016 1:30 PM
  • Thank you for the information.

    I prefer to do a new server and to configure it from scratch. We have Windows 7 client now and we would like to have Windows 10 client in the same time we do the new ConfigMgr server.

    Thanks a lot for the explanation.

    Friday, September 23, 2016 7:43 AM