Planning the Configuration Manager Hierarchy

When designing your Configuration Manager hierarchy you need to create an implementation plan for where to install which server with what kind of roles. The deployment information you gathered in an earlier stage will provide the requirements for where you need to install the Central Administration Site, primary sites, secondary sites, and distribution points. To come up with the right design, follow these design steps:

1.  Define a naming convention if one doesn’t already exist.
2.  Determine whether a CAS is needed and where to place this site in your environment. The CAS is the topmost site in your Configuration Manager hierarchy.
3.  Define the placement of the primary sites, secondary sites, or just distribution points;remember that tiering primary sites is no longer possible. Look at your WAN and keepthe design rules in mind and which roles you need in a specific site.
4. Look at the logical and physical connections between your Configuration Manager sites so you can decide whether addresses need to be configured to manage the traffic between the sites.
5. Assign the boundaries that represent your Configuration Manager sites, and be sure that no boundaries overlap each other.
6.  Depending on the Configuration Manager sites, high-availability demands, and other requirements, you can place the site system roles where they are needed. Designing a good Configuration Manager hierarchy is a must for an effective and solid Configuration Manager infrastructure. Always check the proposed design, and if possible let someone else review the design.