PENDING Expand SCCM Hierarchy

[Ahmed.kassem]

We have two sites that well connected and one single SCCM central administration primary site in the first site that manages devices of both sites .I want to build a new site server in the second site to have the same configurations and database in case I totally lost connection to the first site I can manage devices of second site normally .Also I don't want that server to affect my current configuration and to be able to manage devices from either sites from both sites .To simplify the case I want like an active active two servers that serves devices on both sites and In case losing of connection I still be able to manage devices of second site using the new server that I built , what is the recommended scenario to apply in my case ?

 

[Garth]

To be clear do you have a single primary site or CAS with one or more primary sites?

What exact is you SLA for the network connection? What is your SLA for CMCB? What you are looking to do will cause a ton of headache. What exact do you want to manage when the connection is down?

 

[Ahmed.kassem]

I have a single primary site. We are building a scenario if one of the site infected with a cyber attack to isolate the other site to prevent attack spread through the network. I want to be able to deploy packages, software updates, windows images etc when the other site connection is down.

 

[Garth]

but you didn't answer any of my questions. what you are asking to do does make any sense, even with the extra details. so what are your SLAs?