SESSION CODE MGT 306 Jeffrey Sutherland Principal Program

SESSION CODE: MGT 306 Jeffrey Sutherland, Principal Program Manager Lead John Vintzel, Program Manager Microsoft Corporation

Differences from Config. Mgr 2007 Central Administration Site Recommended location for all administration and reporting for the hierarchy 1. No client data processing 2. No clients assigned 3. Limited site roles Primary Site Service clients in well connected network 1. No tiered primaries 2. Just add primary for scale out; not needed for data segmentation, client agent settings, or network bandwidth control Secondary Site Service clients in remote locations where network control is needed 1. Bundle Proxy MP and DP for install 2. Tiered content routing via secondaries 3. SQL needed

“Remote office optimization” Infrastructure Goal: Minimize Config. Mgr infrastructure to support the remote office locations. Profile Item Hierarchy Design Impacts Company Locations One campus in Minneapolis metro area and a few satellite offices Administrators 1 administrator with other IT responsibilities, limited day-to-day use System Count Approximately 5, 000 clients Feature Set Usage Hardware Inventory every 7 days, deploys software and software updates

“Remote office optimization” Corporate Campus • • • Primary site (3, 000 clients) Local SQL Server MP, DP (x 2), FSP*, SLP*, SUP, SMP, RP/RSP Sales Office • • • Only 15 clients Good connectivity Branch DP or Branch. Cache™ Warehouse • • • District Office • • • Secondary site (1, 500 clients) Manage WAN MP, DP, SUP, PMP Configuration Manager 2007 Secondary site (485 clients) Manage WAN DP

“Remote office optimization” Corporate Campus • • • Primary site (3, 000 clients) Local SQL Server MP, DP (x 2), FSP*, SLP*, SUP, RP/RSP Sales Office • • • Only 15 clients Good connectivity Branch DP or Branch. Cache™ Warehouse • • District Office • • V. Next Secondary site (1, 500 clients) Manage upward/downward WAN traffic SQL Express MP, DP, SUP, PMP DP with throttling and scheduling (485 clients) Manage downward flow of Content over WAN

Data Type Examples Replication Type Where is data found? Global Data Collection Rules, Package Metadata, Software Update Metadata, Deployments SQL Central Administration Site, All Primary Sites, Secondary sites* Site Data Collection Membership, HINV, Alert Messages SQL Central Administration Site, Originating Primary Site Content Software package installation bits, Patch bits, Boot images File-based Primary Sites, Secondary Sites, Distribution Points

Central Administration Site (Germany) Germany (Berlin) Global Site Data Content Available at: Central Administration Site Available at: where Centralcontent Administration Site, Available has been and all Primary Sites Replicating Primary distributed to a Distribution Point Examples: Collection rules • • HINV Package metadata • • Status Deployments • • Collection Membership Results • Security Scopes Spain(Madrid) Cordoba Global Data subset Sevilla Primary Site Content routing between Secondaries Secondary Site Examples • Packages metadata and status • Program metadata

Global Data Examples Site Data Examples

Characteristics Config. Mgr 2007 Config. Mgr v. Next Granularity • Site level attribute • Hierarchy wide default • Complex workarounds • Deploy separate sites based on client setting requirements • Set client agent settings with local policy on each client • Customizations associated to one or many collections • Varies by collection attribute • Resultant settings can be an aggregation of both default & custom settings Policy Applied • Maintenance Windows • Uses additive approach in conflict • Hard to determine “what’s” being applied “where” • Collection Variables • Non-deterministic conflict resolution • No reporting • Setting Objects are priority based and when conflicts arise, Configuration Manager resolves based on priority

“Display what’s relevant to me”

Meg wishes to distribute a package to all of her EMEA users in the West region France Primary Site Louis “French Admin” • French collection(s) • Create advertisement for French collection(s) Meg Collins “Central Admin” • Create and distribute package England Primary Site Anthony “English Admin” • English collection(s) • Create advertisement for English collection(s)

X

“Minimize Infrastructure” Infrastructure Goal: Minimize Configuration Manager infrastructure to support unique remote control settings for the HR department and hardware inventory policies for servers. Profile Item Hierarchy Design Impacts Company Locations Headquarters in Chicago Subsidiary in London Administrators 2 -4 administrator with other IT responsibilities, limited day to day use System Count Approx. 25, 000 clients Feature Set Usage Hardware Inventory every 7 days, deploys software and software updates

HR Primary Site • • • Chicago Central Site Primary site (300 clients) Remote Control Disabled Admin Segmentation • • Primary site (~14, 700 clients) Remote Control Enabled Chicago Campus 15, 000 clients London Primary Site London Servers Site • • • Configuration Manager 2007 Primary site (500 clients) Hardware Inventory Policies unique to Servers Admin Segmentation London Offices 5, 000 desktops 500 Servers • • Primary site (5, 000 clients) Standard Inventory Policies for desktop

Central Admin Site Chicago Primary Site • • • Primary site (15, 000 clients) Local SQL Server HR Collection-based settings for Remote Control No Clients Administration & Reporting for Hierarchy Admin segment for HR clients Chicago Campus 15, 000 clients London Primary • • • London Offices V. Next 5, 000 desktops 500 Servers Primary site (5, 500 clients) Inventory Class reporting at Collection level Admin Segment for Servers

“ 200 k Clients” Profile Item Hierarchy Design Impacts Company Locations Global distributed across US, Latin America, Europe and Asia Administrators 8 - 12 administrator dedicated, packaging personnel, distribution only roles , helpdesk & many customer workflows (high automation) System Count Greater than 200, 000 clients Feature Set Usage Pretty much the same as previous customer, just increasing scale with more clients, more software distribution, and more operating system distributions

SQL Server Central Administration Site Primary 2 Distribution Point Primary 3 Primary 1 Primary 4 Distribution Point Local point of connectivity for administration Secondary Sites (3) Fault Tolerance Secondary Sites (3) Distribution Point Scale/Perf Secondary Site Content Regulation Secondary Site Branch Distribution Point or Branch. Cache™ Content Secondary Sites (3) Distribution Point Secondary Site Concerned with downward flow of content only Concerned with upward and downward flow of traffic (Client/Content) Branch Distribution Point or Branch. Cache™ Primary 5 Branch Distribution Point or Branch. Cache™

Scenario 2007 v. Next Establish central administration/reporting site for hierarchy Central primary Reprocess all data from child sites Central administration site – no data processing Manage different client agent settings Separate primary Collection-based settings Provide client and data segmentation* Separate primary Role-based administration/Admin Segmentation Apply throttling and bandwidth control to content distribution Secondary Site Distribution Points with throttling and scheduling Make content available to clients in small remote offices Standard Distribution Points and Branch Distribution Points • Standard Distribution Points • Branch. Cache™

www. microsoft. com/teched www. microsoft. com/learning http: //microsoft. com/technet http: //microsoft. com/msdn

link Link download link link