Close Menu
    Facebook X (Twitter) Instagram
    Sunday, October 12
    X (Twitter) LinkedIn Reddit RSS
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»Documentation»Cross Forest Support in #SCCM / ConfigMgr 2012

    Cross Forest Support in #SCCM / ConfigMgr 2012

    Eswar KonetiBy Eswar KonetiSeptember 04, 5:27 pm2 Mins Read Documentation 1,603 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Neil Peterson blogged about Cross Forest Support in #SCCM / #Configmgr 2012 into 4 series of guides and they are listed below.

    Introduction -

    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 .

    Read Completed post on http://blogs.technet.com/b/neilp/archive/2012/09/04/cross-forest-support-in-configmgr-2012-part-4-deploying-sites-in-multiple-forests.aspx

    CA Config mgr 2012 configuration Manager Deploying sites multiple Forest Forest Support in SCCM /#Configmgr MP Non Trusted Forest Non-Trusted Forest manage DP primary SCCM 2012 sites Trusted Forest Trusted site Manage sites Unknown Clients
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    SCCM report list collections with no deployments

    December 05, 12:04 pm

    Tool for managing the import and export of SSRS report – ReportSync Tool

    October 27, 9:10 pm

    Investigating SCCM Client Policy Request and Communication Status with a Collection Specific Report

    October 15, 11:22 pm

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2025 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.