SCCM Migration to New Forest/Domain
I am trying to figure out the best approach to migrating a SCCM hierarchy into a completely new forest with as little disruption to patching as possible. There is 1 Central Site (No Clients), 2 Primaries, and about 12-13 Secondaries split between the 2 primaries. Since everything is moving to a new forest/domain I know we will have to do a complete reinstall of the current sites. My first thought was to stand up a new primary in the new forest with the same hardware configuration as the 2 primary site servers. Give it a new site code and begin migrating clients over. Now my question is should I attach this primary to the current Central? My first thought is no as this Central is going to be uninstalled and reinstalled in the new domain. Should I stand up 2 servers in the new environment and mimic the current environment which I believe will give me a better side by side migration and provide me with the ability to patch both sides. The biggest constraint here is a lot of the hardware in teh old forest is going to be reutilized so down time needs to be at a minimum. I think it is doable with 2 new servers in a Central - Child configuration. Once the first primary and clients are migrated the server can be brought into the new domain, stood up and configured to act as the new 2nd primary. Thoughts? Am I missing anything?
October 25th, 2008 4:59pm

Hi, Start at the top of your hierarchy. Install a new SCCM server in the new forest/domain. Make the new server a child of the existing SCCM server. You can now sync data between them just like you do with a primary child site. Keep in mind that a trust between the domains must be created. In a later phase you can disconnect the new server from his older parent so it becomes the central site for the new domain. You can now install the primary child sites and the secondary sites. When a site is ready you can configure the boundaries so it will manage your clients. My advise is not to do it all at once, just step by step and site by site. Hope this helps.
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2008 12:54pm

Hi, The locked items at the child will become available after you break the parent-child relationship. For the packages at the central site you can provide them with the new DP. When you have a lot of packages this can be scripted. (If you want I can provide you the script, check my e-mailaddress onmy profile.) When your packages are distributed keep in mind to copy and update the sourcefiles and path.
October 27th, 2008 5:55pm

Hi, I want to know, will it sync site database also? Or client will again send their inventory to new Site server. -- Vinayak Sharma
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2010 10:32am

Where should we answer your question? Here or in http://social.technet.microsoft.com/Forums/en-US/configmgradminconsole/thread/d90b77c0-c6bf-440a-be3f-7a720440a8b9? So please avoid double postings in the future. Yes, all objects (packages, advertisements, collections etc) from the current primary site will be replicated to the new child site and the client will send inventory to the new site after the site assignment was changed.
May 12th, 2010 10:39am

Okie... Thanks. -- Vinayak
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2010 12:16pm

Lcpc78, how did you go with this migration. Were you able to succesfully migrate SCCM to the new forest using this method?Nilanga
November 15th, 2010 8:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics