Install secondary site sccm

Hi,

Yes, it is possible to deploy a secondary site in a different forest with a two-way trust relationship in Microsoft System Center Configuration Manager (SCCM). A secondary site is used to extend the management functionality of a primary site to a remote location.

Here's a step-by-step guide to installing a secondary site in SCCM:

Prerequisites:

• Ensure that there is a two-way trust relationship between the two forests. This trust allows the SCCM site systems in one forest to communicate with SCCM in the other forest.
• Verify that the network connectivity between the primary site and the remote location (where you want to install the secondary site) is reliable and stable.

Install Prerequisites on Secondary Site Server:

• Ensure that the server intended for the secondary site meets the prerequisites for SCCM installation, such as supported operating systems, disk space, and roles/features.
• Install the required roles and features on the server using Server Manager or PowerShell. SCCM documentation provides information about the prerequisites.

Prepare the Site System Account:

• In the secondary forest, create an SCCM site system account that has the necessary permissions to install the secondary site and access resources in the primary site's forest. Assign this account the necessary permissions in both forests.

Run SCCM Setup on Secondary Site Server:

• Insert the SCCM installation media or mount the SCCM ISO file on the secondary site server.
• Run SCCM setup and choose the "Install a secondary site" option.
• Follow the on-screen instructions to complete the installation.
• During the installation, provide the necessary information about the primary site, including the site code and site server name.

Monitor Installation and Synchronization:

• Once the secondary site installation is complete, monitor the installation status in the SCCM console to ensure everything is functioning correctly.
• Verify that the secondary site synchronizes with the primary site to replicate data, policies, and packages.

Configure Boundaries and Boundary Groups:

• In the SCCM console, configure boundaries and boundary groups to define the network locations of devices that should be managed by the secondary site.

Test and Verify:

• After the secondary site is set up and synchronized with the primary site, test client connectivity and deployment to ensure everything is working as expected.

Hello, I have a question about the design. Multiple forests connected with a two-way trust relationship. I'm a bit confused with the layout it should have, in order to manage them all from the same sccm console. Do I need to have a CAS and parent site hierarchy under each forest so as not to overload the bandwidth on the links that join them?

I don't have more than 100,000 clients to manage among the entire forest, but from what I understand I can't create several joined primary sites, due to redundancy issues and so on… everything that is more than one primary site needs a CAS, right?

What would be the best solution? implement several primary sites (for redundancy) and hang a secondary site all under a CAS.

Or implement a primary site and secondary sites hang from it? Would a CAS be necessary?

thanks I have no experience with SCCM

I would not install a CAS. Depending on the number of clients, the lan/wan setup and others thing will help determine what you install and where. There isn't enough detail to give advice. As you might not need anything extra to support the other forest.