Hi, We need to install another sccm central site in the same forest (domain) where we currently already have sccm implemented. Can anyone see any problems here with setting up another independent sccm deployment (it will also be published to AD). This new one will service clients in another untrusted domain as a workgroup setup. The bigger picture is to sort out the problems with the first sccm design, then migrate the clients in the other domain, and then have that as a primary of the original central (but that will all be in the distant future). So for now we need to: 1. Have both central sites sitting side by side and published to AD (the clients in remote site will be set up as a workgroup) 2. Once we are ready, is it a simple process to connect the sccm hierarchy just created to the original central site in the future. I would think this is straight forward since it would then just become a primary of the central, but if anyone could direct me to some documentation it would be appreciated. 3. I guess doing this is a better idea than installing sccm into the domain which has the clients to be managed but will be migrated in 12 months time, and then having to rip sccm out of the old domain and reinstall sccm as a primary in the new domain

Hi, It can be done, and sounds like a good plan as long as you don't have any overlapping bounaries between the two sites. The process of connecting the two sites is very straight forward, it's just a "normal" parent-child relationship.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Hi, I made several tests in my virtual environment to setup multiple SCCM site in one domain, as Kent said, as long as there is no overlapping boundaries, it will be OK.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.