locked
Installation steps for SCCM 2012 R2 for Migration from SCCM 2007 R3 to 2012 R2 RRS feed

  • Question

  • Hi

    We have a single Primary installed SCCM 2007 R3 SP2 site, which is planning to be Migrated to SCCM 2012 R2 single Primary site with single server. SQL is configured in cluster with 2instances (one for SCCM & VMM and another for SCOM). Below are our concerns while starting with SCOM 2012 R2 installation

    a) Creating a folder under services OU, say Systems Management 2012 R2, with delegated full permission for SCCM server - Is this a required step?

    b) Is it required to extend the schema? Currently the DCs are running with Windows 2008 R2, domain and forest functional levels are Windows server 2003.

    c) The parallel migration might take a month's time, so how can we keep existing SCCM 2007 R2 configuration like site boundaries intact and how do we mention the same boundaries again with SCCM 2012 R2?

    Expect support and suggestions


    LMS

    Monday, December 8, 2014 2:31 PM

Answers

  • Laljeev,

    a) You will need to delegate out the permissions to the new site server

    b) Nothing to be done as already extended

    c) Add in the same boundaries but do not set for site assignment and use the SMSSITECODE= switch on client installs on the old 2k7 site.


    Cheers

    Paul | sccmentor.wordpress.com

    Monday, December 8, 2014 2:37 PM
  • Hi,

    a, for the new CM 2012 site to be able to publish site information in AD to the clients then yes you will have to add those permissions, you most likely have it already as you are running SCCM 2007.

    b, If the Schema is extended for SCCM 2007 there is no need to extend the AD once again.

    c, Boundaries is rewritten in SCCM 2012, so as long as you don't set a Boundary Group to be used for Site Assignment there are no problems with overlapping boundaries.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Monday, December 8, 2014 2:39 PM

All replies

  • Laljeev,

    a) You will need to delegate out the permissions to the new site server

    b) Nothing to be done as already extended

    c) Add in the same boundaries but do not set for site assignment and use the SMSSITECODE= switch on client installs on the old 2k7 site.


    Cheers

    Paul | sccmentor.wordpress.com

    Monday, December 8, 2014 2:37 PM
  • Hi,

    a, for the new CM 2012 site to be able to publish site information in AD to the clients then yes you will have to add those permissions, you most likely have it already as you are running SCCM 2007.

    b, If the Schema is extended for SCCM 2007 there is no need to extend the AD once again.

    c, Boundaries is rewritten in SCCM 2012, so as long as you don't set a Boundary Group to be used for Site Assignment there are no problems with overlapping boundaries.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Monday, December 8, 2014 2:39 PM
  • a) Creating a folder under services OU, say Systems Management 2012 R2, with delegated full permission for SCCM server - Is this a required step?

    I just want to make sure that you understand. The container MUST be called System Management. You can't call it what you like (eg Systems Management 2012 R2). As the guys say you will have created this already for 2007 so you don't have to do it again. You merely have to add permissions for the new 2012 site server computer account.


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    Monday, December 8, 2014 3:04 PM
  • Gerry has pointed out something there. Yes the container must be called System Management.

    Cheers

    Paul | sccmentor.wordpress.com

    Monday, December 8, 2014 3:55 PM
  • Thank You all.

    We found the System Management container and will delegate teh full permission for new server.

    Is there a way to confirm the schema extension / current schema is ready for SCCM 2012 R2

    Will configure the same Boundaries (rest I can't comment at this moment since don't have hands on experience), but hope with this setting we can set some as SCCM 2012 R2 clients and test all functionality and won't affect any of the existing 2007 R2 clients)

    Since we have a single site with around 500 client systems we think to go with the installation and not to do a migration. Once everything looks fine with few test systems and if we do not go with a migration, then how can we proceed with install the new client and assign the clients to new site?

    Thanks in advance


    LMS

    Monday, December 8, 2014 5:21 PM
  • Hi,

    >>Is there a way to confirm the schema extension / current schema is ready for SCCM 2012 R2?

    Please check the blog blew that lists all the attributes and classes are added to Active Directory Domain Services When you extend the Active Directory schema for ConfigMgr 2012.

    Extending the Schema in System Center 2012 Configuration Manager

    >>Once everything looks fine with few test systems and if we do not go with a migration, then how can we proceed with install the new client and assign the clients to new site?

    To upgrade or reassign clients from a source site to a destination site, you can use any client deployment method that is supported for deploying clients in the destination hierarchy. Typical client deployment methods include client push installation, software distribution, Group Policy, and software update-based client installation. For more information, see Determine the Client Installation Method to Use for Windows Computers in Configuration Manager.

    Best Regards,

    Joyce

    Tuesday, December 9, 2014 7:26 AM