Posted by Eswar Koneti on September 4th, 2012
Neil Peterson blogged about Cross Forest Support in #SCCM / #Configmgr 2012 into 4 series of guides and they are listed below.
Welcome to the last in this series of four articles examining cross forest support in 2012 Configuration Manager. In the previous three postings I have examined configuration options for client management across a non-trusted forest. To recap, the following scenarios or configurations have been discussed.
- Scenario 1 – Simple management of a small amount of know clients residing in a non-trusted forest.
- Scenario 2 – More complex management of a larger number of unknown clients residing in a non-trusted forest. This article introduces cross forest discovery, publishing, and client push installation.
- Scenario 3 – Introduces the placement of Configuration Manager Infrastructure (MP, DP) in a non-trusted forest.
In this final and brief article I will examine the cross forest placement of a Configuration Manager site (Primary or Secondary). This process is very similar, almost identical to deploying a child site in the same forest as the parent. Because of this I will not go into deep detail on site deployment; this will be a short post. There are however a few items worth pointing out, and I do want to ensure that this series on cross forest management has come full circle.
Why deploy a cross forest site -
Why install a site into a forest other than the on hosting the CAS or Primary site? In my opinion, the reasons for doing so would be the same reasons that would justify the introduction of an additional site (primary or secondary) into a Configuration Manager Hierarchy spanning only one forest. Some of these reasons may include (just to name a few)
- Client counts of greater than 100,000 (Primary)
- Requirement to control the upward flow of client and site communication (Secondary)
- Rich Content Routing capabilities (Secondary)
Check out the following article for more information that will aid in determining if additional sites are needed in you Configuration Manager deployment – Planning for Sites and Hierarchies in Configuration Manager .