Advanced Infrastructures In System Center Configuration Manager 2012 R2 Jason blog.configmgrftw.com m Wally

Best practices are guidelines allowing newbies to NOT think about

1 != != 2012 ConfigMgr 2007 != ConfigMgr 2012 ConfigrMgr 2007 Sites != ConfigMgr 2012 Sites

To CAS or Not to CAS

Central Administration Sites The Good Lots of managed clients Distributed Content The Bad Does not provide high availability, redundancy, or site resiliency The Ugly SQL Replication Administrative Latency

CAS Scenarios More than 100,000 managed Windows* clients CAS Geographically separated locationsNo CAS. Use secondary sites (if needed) and remote distribution points Internal politics and whiningBe the technical expert!

Remote Location Fringe Scenario 1: Multiple locations, each with 10,000+ managed Windows clients Secondary Site 2Secondary Site 1 Primary Site

Fringe Scenario 2: Remote Content Creators DP2 DP1 Primary Site

Fringe Scenario 2: Remote Content Creators Primary Site 2 Primary Site 1 CAS

Nation B Nation A Fringe Scenario 3: National Politics Primary Site 2 Primary Site 1 CAS

Remote Locations

Secondary Sites Provide location aware, local site roles Schedule and throttle client to (primary site) MP communication Are resilient Manage clients

Primary Site Remote Location: Option 1, No Remote Infrastructure MP DP WSUS Content * * State & Status Messages, Hardware and Software Inventory Update Catalog

Primary Site Remote Location: Option 2, Remote DP only MP DP WSUS DP Primary Site Server * * State & Status Messages, Hardware and Software Inventory

Primary Site Secondary Site Remote Location: Option 3, Remote Secondary MP DP WSUS MP DP WSUS Primary Site Server * Registration

The Choice: DP vs Secondary Site DP Secondary Site Clients Available Bandwidth

Site Role Placement and Client Location

Multiple (Client Facing) Site Roles Within a Single Primary Site High AvailabilityCross-forest Remote locations Segregated Networks * The “No’s” on this slide are only applicable to MPs

High Availability -- Not CAS Primary Site 1 Primary Site 2

High Availability MP DP WSUS Primary Site Server MP DP WSUS

Client Selection (within a Primary Site) Respects HTTPS/HTTP, forests, and domains Random 3 failures leads to failover MP Respects HTTPS/HTTP, boundaries, subnets, and fallback Random within boundary group 8-hour failover DP First installed Respects forests 3 failures leads to failover – no automatic failback SUP

Management Point Location Times

DMZs and Segregated Networks

Segregated Network: Option 1 Primary Site MP DP WSUS Content * * State & Status Messages, Hardware and Software Inventory Update Catalog TCP 80/443 TCP 8530/8531 (80/443)

Secondary Sites are not Gateways Primary Site MP DP WSUS MP DP WSUS Primary Site Server * MP *

Primary Site Domain or Forest B Domain or Forest A Segregated Network: Option 2a DB DP WSUS MP DP WSUS Primary Site Server MP

Primary Site Segregated Network: Option 2b DB DP WSUS MP DP WSUS Primary Site Server MP

Multiple Hierarchies

Test, Dev, LabLegal or National Politics Administrative segregation Client segregation

Evaluations Please provide session feedback by clicking the Eval button in the scheduler app. One lucky winner will get a free ticket to the next MMS! Platinum Sponsors Gold Sponsors Visit all of our sponsors in the expo area and online!