locked
Child/Parent relations in SCCM 2007 to SCCM 2012 (Migrating) RRS feed

  • Question

  • Hi,

    Im wanting to migrate 2007 to 2012. When i migrated from 2003 to 2007 i basically installed the clients and added them into the new site with commandline without AD publishing.
    Unforynatly we are using SCCM for more critical solutions now inclusing patch managment. Im unabel to affectivly big bang the migration.

    I have been reading a few posts and i think i may have a plan, but wanted to know if anyone else had already done it, or a better way to do it.

    Im going to create a new server with SCCm 2012 installed. Make this a child to my sccm 2007 site and create sender addresses. I should then be able to conrol my sccm 2007 through 2012 site??
    Then create a source site to migate from (sccm 2007).
    Publish the new site to AD
    Once all client sreporting

    Is it better to create a new WSUS server? Or can you add the existing site server
    Do you have to create a new datbase?

    Monday, July 30, 2012 10:52 AM

Answers

All replies

  • Im going to create a new server with SCCm 2012 installed. Make this a child to my sccm 2007 site and create sender addresses. I should then be able to conrol my sccm 2007 through 2012 site??

    That won't work. You have to migrate everything from CM07 to CM12 using migration jobs: http://technet.microsoft.com/en-us/library/gg699364.aspx 

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

    Monday, July 30, 2012 11:11 AM
  • Does that mean i will have to create a new databse for config mgr 2012?

    THe client migration isnt making much sense... You migrate collections and other objects using the wizsards. Then you client are still talking to the old site.

    So do you publish the 2012 site to AD and then run a software update package from config mgr 2007 to upgrade client, and then it should report to 2012?

    The issue i have is only half my client was installed with SMSSITECODE=AUTO the others were had the side code in commandline.

    Monday, July 30, 2012 11:24 AM
  • Yes, you have to set up a new CM12 infrastructure.
    It does not matter how you installed the clients intially. They won't change site assignment automatically once they were assigned to a site. There are several ways tp upgrade and re-assign clients: client push from CM12, deploying the CM12 client using CM07, using the SUP etc ...

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

    Monday, July 30, 2012 12:14 PM
  • So even though i discover the clients in CM12 and i have published CM12 to AD the clients will still talk to CM07?

    I dint know that! So you effectivly have to big bang the project? Isnt there any better way to migrate, as client are reciving Updates and definition updates from CM07 now.

    Thanks for you help.

    I have read the following TechNet:
    http://technet.microsoft.com/en-us/library/2ad4b21a-43bd-434e-b3bb-fc8744da7e9c#BKMK_upgrade

    The method i will be using is combination of package rollout and client push via collection. But...

    If i discover the clients, and publish the site to AD, and move add the boudaries into CM12, ALL other cleints will stop talking to CM07 and wont recive updates? Which mean i will have to push hard on client install... I dont think my manager will wont to go with this approach..

    Friday, August 3, 2012 11:02 AM
  • If i discover the clients, and publish the site to AD, and move add the boudaries into CM12, ALL other cleints will stop talking to CM07 and wont recive updates? .

    They still will be able to receive updates etc.

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

    Friday, August 3, 2012 11:35 AM