none
SCCM 2007 update to SCCM 2012

    Question

  • Hi!

    Want to update SCCM 2007 to the 2012. I would like to find a scenario to gradually transfer the existing site is providing all of the roles to the new SCCM 2012. Is this possible? Maybe need to make a new site, and gradually move customers? How is it better?


    cenubit

    Monday, April 23, 2012 11:14 AM

Answers

  • Hi,

    It is not possible to do an inplace upgrade from SCCM 2007 to ConfigMgr2012, so you would have to install a new site, use the migration features and migrate what you need from your old site and then gradually move clients to the new Site.

    The migration scenario is explaned here:

    http://technet.microsoft.com/en-us/library/gg682006.aspx

    Regards,
    Jörgen


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

    • Proposed as answer by Jason SandysMVP Monday, April 23, 2012 12:13 PM
    • Marked as answer by GirtsR Monday, April 23, 2012 12:20 PM
    Monday, April 23, 2012 11:25 AM
  • if you plan to have multiple primary site then you need CAS and then you can have primary site to join. if you create stand alone site then you cant join it to CAS later.

    simple is = first create CAS then primary site.


    Syed Kasif

    • Marked as answer by GirtsR Monday, April 23, 2012 12:18 PM
    Monday, April 23, 2012 12:09 PM
  • It is not likely that you need a CAS, when  you currently do not have multiple primary sites.

    Let's start with this:  At a fundamental level, the core components of ConfigMgr 12, it is different.  So very, very different, that it is impossible to upgrade in place.

    So, considering your request of "slowly moving over", that's actually perfect for you--just not in the way you meant, I think. You really need to read through the Migration scenario Jorgen posted.  I'd just be repeating everything in the forum post that is already documented.

    Basically, Yes, you DO need to install a new site--a new standalone primary site, with a new site code and (likely) new hardware; although I've heard of suggestions where you could re-use existing hardware, but that would likely not fit into your 'slow' scenario.  Just basically follow the documentation.  I suspect it will get clearer.  There are tools available to migrate your packages, collections, content--it can all be migrated from old to new. 

    Personally, I suggest you cherry-pick the stuff you really want to migrate; not just select all and dump it over.  But that's me...


    Standardize. Simplify. Automate.

    • Proposed as answer by Jason SandysMVP Monday, April 23, 2012 12:13 PM
    • Marked as answer by GirtsR Monday, April 23, 2012 12:20 PM
    Monday, April 23, 2012 12:10 PM

All replies

  • Hi,

    It is not possible to do an inplace upgrade from SCCM 2007 to ConfigMgr2012, so you would have to install a new site, use the migration features and migrate what you need from your old site and then gradually move clients to the new Site.

    The migration scenario is explaned here:

    http://technet.microsoft.com/en-us/library/gg682006.aspx

    Regards,
    Jörgen


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

    • Proposed as answer by Jason SandysMVP Monday, April 23, 2012 12:13 PM
    • Marked as answer by GirtsR Monday, April 23, 2012 12:20 PM
    Monday, April 23, 2012 11:25 AM
  • Ok. I do not understand or need to install a new primary site for a stand-a-lone site. Or first create the Central Administration Site and join my new site to this central administration site?

    cenubit

    Monday, April 23, 2012 11:35 AM
  • if you plan to have multiple primary site then you need CAS and then you can have primary site to join. if you create stand alone site then you cant join it to CAS later.

    simple is = first create CAS then primary site.


    Syed Kasif

    • Marked as answer by GirtsR Monday, April 23, 2012 12:18 PM
    Monday, April 23, 2012 12:09 PM
  • It is not likely that you need a CAS, when  you currently do not have multiple primary sites.

    Let's start with this:  At a fundamental level, the core components of ConfigMgr 12, it is different.  So very, very different, that it is impossible to upgrade in place.

    So, considering your request of "slowly moving over", that's actually perfect for you--just not in the way you meant, I think. You really need to read through the Migration scenario Jorgen posted.  I'd just be repeating everything in the forum post that is already documented.

    Basically, Yes, you DO need to install a new site--a new standalone primary site, with a new site code and (likely) new hardware; although I've heard of suggestions where you could re-use existing hardware, but that would likely not fit into your 'slow' scenario.  Just basically follow the documentation.  I suspect it will get clearer.  There are tools available to migrate your packages, collections, content--it can all be migrated from old to new. 

    Personally, I suggest you cherry-pick the stuff you really want to migrate; not just select all and dump it over.  But that's me...


    Standardize. Simplify. Automate.

    • Proposed as answer by Jason SandysMVP Monday, April 23, 2012 12:13 PM
    • Marked as answer by GirtsR Monday, April 23, 2012 12:20 PM
    Monday, April 23, 2012 12:10 PM
  • Hi,

    IF you need a CAS you must install it first, I strongly recommend that you read the section "Determine wheter to install a CAS" here: http://technet.microsoft.com/en-us/library/gg712681.aspx if you haven't already to determine if you need a CAS in your environment.

    Regards,
    Jörgen


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

    Monday, April 23, 2012 12:20 PM
  • Ok. 

    Now I have two primary site, a single domain. Old and new. 



    There was a problem with hosts Remote Controll. AD extsch performed:

    "
    <04-25-2012 08:52:58> Modifying Active Directory Schema - with SMS extensions.
    <04-25-2012 08:52:58> DS Root:CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-Site-Code already exists.
    <04-25-2012 08:52:58> Attribute cn=mS-SMS-Assignment-Site-Code already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-Site-Boundaries already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-Roaming-Boundaries already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-Default-MP already exists.
    <04-25-2012 08:52:58> Attribute cn=mS-SMS-Device-Management-Point already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-MP-Name already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-MP-Address already exists.
    <04-25-2012 08:52:58> Attribute cn=mS-SMS-Health-State already exists.
    <04-25-2012 08:52:58> Attribute cn=mS-SMS-Source-Forest already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
    <04-25-2012 08:52:58> Attribute cn=MS-SMS-Ranged-IP-High already exists.
    <04-25-2012 08:52:58> Attribute cn=mS-SMS-Version already exists.
    <04-25-2012 08:52:58> Attribute cn=mS-SMS-Capabilities already exists.
    <04-25-2012 08:53:00> Class cn=MS-SMS-Management-Point already exists.
    <04-25-2012 08:53:00> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM
    <04-25-2012 08:53:00> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM.
    <04-25-2012 08:53:00> Class cn=MS-SMS-Server-Locator-Point already exists.
    <04-25-2012 08:53:00> Located LDAP://cn=MS-SMS-Server-Locator-Point,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM
    <04-25-2012 08:53:01> Successfully updated class CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM.
    <04-25-2012 08:53:01> Class cn=MS-SMS-Site already exists.
    <04-25-2012 08:53:01> Located LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM
    <04-25-2012 08:53:01> Successfully updated class LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM.
    <04-25-2012 08:53:01> Class cn=MS-SMS-Roaming-Boundary-Range already exists.
    <04-25-2012 08:53:01> Located LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM
    <04-25-2012 08:53:02> Successfully updated class LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=DOMAIN,DC=GOV,DC=COM.
    <04-25-2012 08:53:02> Successfully extended the Active Directory schema.

    <04-25-2012 08:53:02> Please refer to the ConfigMgr documentation for instructions on the manual 
    <04-25-2012 08:53:02> configuration of access rights in active directory which may still 
    <04-25-2012 08:53:02> need to be performed.  (Although the AD schema has now be extended, 
    <04-25-2012 08:53:02> AD must be configured to allow each ConfigMgr Site security rights to 
    <04-25-2012 08:53:02> publish in each of their domains.)
    "
    Many entries already exists. It can interfere with correct operation?

    Test computer IP exceptions from the old site Boundaries, and add to the new site. But the host SCCM agent is not the Find 
    Site (Configuration Manager did not find a site to manage this client.

    When I try to connect, get an answer:

    "A remote control session could not be established with the remote computer"



    Where would be a mistake.



    --------------------

    Inserted the SCCM Agent New Site name (COnfig.Manager Service Properties / Assigned currently the site code). 
    And after a few restarts and ~ 4 hours, a workstation connects to the SCCM site. Remote control works well. 
    Should understand how the site code, added automatically.


    • Edited by GirtsR Wednesday, April 25, 2012 11:26 AM
    Wednesday, April 25, 2012 6:56 AM
  • Hi everybody,

    I am in a project for to migrate SCCM 2007 to SCCM 2012, but i have questions. 

    the scenary for SCCM 2007 is follow:

    - only one CAS

    -Only one primary site

    -19 Distribution points

    I thinking for SCCM 2012

    only one primary site and share distribution point 

    is posible?

    thanks 


    jose

    Monday, May 14, 2012 3:15 PM
  • You should start a new thread for new questions.

    Also note, 2007 does not have a CAS -- the Central Administration Site (CAS) role in 2012 is a completely new beast and is not the same thing as a Central Primary Site in 2012.

    In 2012, the need for a CAS is very limited and unless you have over 100,000 clients, you should start out your design without one and only use  single primary.

    The number of DPs is dependnat on other factors that you have not listed including client locations, cound, and connectivity.


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Monday, May 14, 2012 4:48 PM