We have a Primary standalone SCCM 2012 site in a single Domain hosting multiple location with the connectivity to MP & DP’s, we have SQL installed on same site server.
Usage: Software Distribution, Software Update, Reporting. We do not use it for Image Management.
Requiring: If the current site server connectivity is broken and takes long time to recover because of any reason. We are looking to host another SCCM server to leverage all our tasks during that disaster recovery plane.
Plans: Is it good idea to build another SCCM standalone site with in a single domain with different boundaries for time being.
When we need to execute plans we can add boundaries to the new SCCM sever and run a script to change the site code to manage the systems.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Current Scenario
We have a Primary standalone SCCM 2012 site in a single Domain hosting multiple location with the connectivity to MP & DP’s, we have SQL installed on same site server.
Usage: Software Distribution, Software Update, Reporting. We do not use it for Image Management.
Requiring: If the current site server connectivity is broken and takes long time to recover because of any reason. We are looking to host another SCCM server to leverage all our tasks during that disaster recovery plane.
Plans: Is it good idea to build another SCCM standalone site with in a single domain with different boundaries for time being.
When we need to execute plans we can add boundaries to the new SCCM sever and run a script to change the site code to manage the systems.
Share this post
Link to post
Share on other sites