locked
System Center 2012 / 1606 Co Existence RRS feed

  • Question

  • Hello Community,

    currently we use a 2012 SP1 CU5 Installation, without AD Publishing, hence no "Systems Management" OU has been created. We have a single Site System with one Primary Site. All Clients are covered with boundaries based on Network ranges.

    We are planing to build a DEV Environement with SCCM 1606 in a separat Subnet and a new Site to minimize boundary overlapping.

    When we start with the setup, the common method is, to create such a OU "System Managament" in AD in combination with the Schema Extension, regarding this Link:

    https://social.technet.microsoft.com/wiki/contents/articles/36614.sccm-2016-step-by-step-walk-through-setup.aspx

    What happens to the current SCCM Environment when we create this OU durring the SCCM 1606 Setup?

    How do we prevent the new SCCM System to publish into AD, or shouldn't we?

    Thank you for any Advise.

    Tuesday, April 18, 2017 11:25 AM

Answers

  • "System Managament" is a container, not an OU.

    Multiple ConfigMgr sites can happily co-exist as long as site assignment boundary/Groups do not overlap (and if they are using unique sitecodes obviously).


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

    Tuesday, April 18, 2017 11:39 AM
  • > "What happens to the current SCCM Environment when we create this OU durring the SCCM 1606 Setup? "

    Nothing.

    > "How do we prevent the new SCCM System to publish into AD, or shouldn't we?"

    You don't have to do anything. To enable publishing, you need to grant permissions on this container, thus if you don't grant permissions for the existing site, it can't do anything.


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

    • Marked as answer by lonleysurvior Friday, July 21, 2017 6:59 AM
    Tuesday, April 18, 2017 1:35 PM

All replies

  • "System Managament" is a container, not an OU.

    Multiple ConfigMgr sites can happily co-exist as long as site assignment boundary/Groups do not overlap (and if they are using unique sitecodes obviously).


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

    Tuesday, April 18, 2017 11:39 AM
  • > "What happens to the current SCCM Environment when we create this OU durring the SCCM 1606 Setup? "

    Nothing.

    > "How do we prevent the new SCCM System to publish into AD, or shouldn't we?"

    You don't have to do anything. To enable publishing, you need to grant permissions on this container, thus if you don't grant permissions for the existing site, it can't do anything.


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

    • Marked as answer by lonleysurvior Friday, July 21, 2017 6:59 AM
    Tuesday, April 18, 2017 1:35 PM