Hi Guys, I currently have an SCCM solution within a single domain - looking after about 1000 clients. I need to relocate the SCCM services on another server. In addition, I am going to move the DB onto a SQL cluster, and I want to change the SCCM server name. For these reasons, I am going to need to build a new environment. I will then need to migrate data and clients from the existing SCCM server to my new one. To do this, I would like to do a side-by-side migration, running both systems in production until everything is cut over. To do this I am thinking of taking the following actions: 1. Build new SCCM Server (new site name and site code)2. Attach new SCCM site as a child site to the existing SCCM site3. Let all objects replicate down4. Break the relationship between the two5. Migrate one AD site to the new environment6. Remove that boundary from the old SCCM site7. Add that boundary to the new SCCM site8. Test with users9. Once I am happy with my testing and everything is working ok, repeat steps 5-7 for the rest of the clients10. Decommission old site Is it possible to move one AD site at a time, or do you need to do an all or nothing transfer? The AD Schema has been extended for the current SCCM environment. Would this have any impact on running two systems side by side, especially during the testing phase, before I move all users over? Also, when I decommission the old site, do I need to clean up AD in anyway - remove the old site information - or does this occur automatically? Any information would be great. Thanks very much Luca

Hi,1) If by AD site you are reffering to a boundary then moving one at a time is ok.2) It wont have any impact as long as you don't have overlapping boundaries.3) If it is not removed then you can manually remove the objects.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

There's one step missing: you have to reassign the clients from the old to the new site, because that won't happen automatically (between step 6 and 7). The SDK has a sample script: http://msdn.microsoft.com/en-us/library/cc146558.aspxNo problem with AD schema extension and no problem having two sites in one domain as long as sitecode, servername and boundaries are unique. A removal of all roles and boundaries before decomissioning the old site should delete the entries from the System Management container, but it's always a good idea to double check that.

Thanks guys, that clears things up.Luca

Hello, can you, please, give me described manual what is the right way to do it? I've created a secondary site and attached it to existing one is that a child site? And the "3. Let all objects replicate down" how it should be? Can you, please, describe it? Because I understand how to do it but there's no manual where and what should i change. Thanks.

Please avoid double postings! You already opened a new thread here: http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/f8a20046-890c-49b0-aa86-39cd855d9b3d/#0427dbad-a924-47b6-82ee-606aa056e829

Torsen But why no one want to answer?

There are anwers in the other thread. Locking this one to avoid confusion.