560 likes | 661 Views
#BEMMS. Configuration Manager 2012: Deployment and Infrastructure considerations. Kenny Buntinx MVP Configuration Manager Computacenter. Who I am. Microsoft Practice Leader @ Computacenter Configuration Manager MVP since July 2009
E N D
#BEMMS Configuration Manager 2012: Deployment and Infrastructure considerations Kenny Buntinx MVP Configuration Manager Computacenter
Who I am • Microsoft Practice Leader @ Computacenter • Configuration Manager MVP since July 2009 • Co-Founder of the System Center User Group Belgium @ http://www.scug.be • Email : Kenny_Buntinx@computacenter.com • : KennyBuntinx
What I plan to cover in this session • Infrastructure setup • High availability • SQL replication • CAS ,Primary Site, Secondary Site & DP’s • Internet Based Managed Clients • AMT (Vpro)
Infrastructure Promises • Modernizing Architecture • Minimizing infrastructure for remote offices • Consolidating infrastructure for primary sites • Scalability and Data Latency Improvements • Central Administration Site is just for administration and reporting – Other work distributed to the primaries as much as possible • File processing occurs once at the Primary Site and uses replication to reach other sites (no more reprocessing at each site in the hierarchy) • System-generated data (HW Inventory and Status) can be configured to flow to the Central Administration Site directly • Be Trustworthy • Interactions with SQL DBA are consistent with Configuration Manager 2007 • Configuration Manager admin can monitoring and troubleshoot new replication approach independently
Infrastructure and DesignInitial impressions / questions • How to design a new infrastructure for a new environment? • Will this differ for a customer with SCCM 2007 today ? • Where do I need site servers and site role servers? • Good news ! – Initial experience suggests fewer servers
Delivering on the Promise Infrastructure ?
Simple topology Primary Central Administration Site Distribution Point Distribution Point Secondary Site 2012
The business scenario needs for today’s session : Well designed , reduced infrastructure Highly available, well monitored Clients and servers management must be separated Internet connected laptops Separate European Active Directory Forest Remote out-of-band support Primary 3 MP DP
USA Europe • 30.000 clients • 2500 Servers EMEA.company.com • 15.000 clients • 250 Servers AMT enabled devices Solutions enabled Well designed , reduced infrastructure High availability/monitoring Clients and servers management must be separated Internet facing in USA Additional Active Directory Forest Out of band management in Asia Asia • 500 clients • 15 Servers MP DP
Delivering on the Promise High available ?
High Availability (Administration) • Ensure I can administer my environment • SQL Clustering: • site database • Multiple Admin-Facing Site System Roles: • SMS Provider, Reporting Services Point
High Availability (Serving Clients) • Ensure clients can be managed • Windows Network Load Balancing continues to be supported for: • Management Point, Software Update Point • New client load balancing and failover solution in 2012 • High-availability without the need for network load balancer! • Multiple MP’s • Multiple DP’s • Multiple Client-Facing Site System Roles: • Distribution Point (PXE), Server Locator Point, State Migration Point, System Health Validator Point • Automatic remediation for unhealthy clients
Delivering on the Promise Central Administration site ?
When do I Need a Central Administration Site? • More than one Primary Site in a single hierarchy • Off-load reporting and administration from your Primary Site • Disaster Recovery scenarios (**) Migration Consideration: The Central Administration Site must always be installed first
Our IT challenge USA Europe • 30.000 clients • 2500 Servers EMEA.woodgrove.com • 15.000 clients • 250 Servers CAS AMT enabled devices Business needs Well designed , reduced infrastructure Highly available, well monitored Internet connected laptops Separate European Active Directory Forest Clients and servers management must be separated Remote out-of-band support Asia • 500 clients • 15 Servers MP DP
SQL Server in Configuration Manager 2012 • Be Trustworthy • Interactions with SQL DBA are consistent with Configuration Manager 2007 • Configuration Manager admin can monitor and troubleshoot new replication approach independently • Only one Configuration Manager site per SQL Server instance is allowed • All database communication is encrypted • TCP/IP port for service broker
Replication *Subset of global data only
SQL Replicated Data Types Global Data Examples Site Data Examples • Collection Rules & Count • Package Metadata • Program Metadata • Deployments • Configuration Item Metadata • Software Update Metadata • Task Sequence Metadata • Site Control File • System Resource List (site servers) • Site Security Objects (Roles, Scopes, etc.) • Alert Rules • Collection Membership Results • Alert Messages • Hardware Inventory • Software Inventory & Metering • Asset Intelligence CAL Track Data • Status Messages • Software Distribution Status Details • Status Summary Data • Component and Site Status Summarizers • Client Health Data • Client Health History • Wake On LAN • Quarantine Client Restriction History
Conceptual Replication Model • Global Data • Available at: Central Administration Site and all Primary Sites • Examples • Collection rules • Package metadata • Deployments • Security Scopes • Site Data • Available at: Central Administration Site, Replicating Primary • Examples: • HINV • Status • Collection Membership Results Content Available where content has been distributed to a Distribution Point Central Administration Site USA Europe USA -Texas Asia
Delivering on the Promise Primary site ?
Infrastructure and DesignEvaluating the need of multiple primaries? • Remove those required only due to SCCM 2007 • Consider addition of multiple roles per site (MP, provider, etc.) • Consider changes in network to support client traffic • Consider throttling and scheduling added to DPs
Client Settings Easiest Step to Infrastructure Reduction: Stop using primary sites for different Client Settings Default Client Settings for the entire hierarchy Custom Client Settings assigned to collections • Resultant settings can be an aggregation of both default & one or more custom settings • Priority-based conflict resolution • Custom settings override default settings
When do I Need a Primary Site? • To manage any clients • Add more primary sites for: • Scale (more than 100,000 clients) • Reduce impact of primary site failure • Local point of connectivity for administration • Political reasons • Content regulation • Decentralized administration • Logical data segmentation • Client settings • Language • Content routing for deep hierarchies
Our IT challenge USA Europe • 30.000 clients • 2500 Servers EMEA.woodgrove.com • 15.000 clients • 250 Servers CAS Primary 1 Primary 2 AMT enabled devices Business needs Well designed , reduced infrastructure Highly available, well monitored Internet connected laptops Separate European Active Directory Forest Clients and servers management must be separated Remote out-of-band support Asia • 500 clients • 15 Servers MP DP
Cross Domain/Forest: Trusted woodgrove.com Woodgrove-emea.com USA.woodgrove.com CAS PR1 PR2 SEC1 Distribution Point Management Point Management Point Distribution Point Asia.woodgrove.com Distribution Point Management Point
Delivering on the Promise Secondary site ?
When do I Need a Secondary Site? • Manage upward-flowing WAN traffic • Tiered content routing for deep network topologies • Use of local SMP • No local administrator
Our IT challenge USA Europe • 30.000 clients • 2500 Servers EMEA.woodgrove.com • 15.000 clients • 250 Servers CAS Primary 1 Primary 2 AMT enabled devices Business needs Well designed , reduced infrastructure Highly available, well monitored Internet connected laptops Separate European Active Directory Forest Clients and servers management must be separated Remote out-of-band support Asia Secondary 1 • 500 clients • 15 Servers MP DP
Delivering on the Promise Local Distribution Point ?
When a Local Distribution Point? • BITS not enough control for WAN traffic • Multicast for Operating System Deployment • App-V streaming
Distribution Points • One distribution point type • Role can be installed on clients and servers • Clients - Windows Vista SP2 and later • Servers - Windows Server 2003 SP2 and later • Ability to configure throttling and scheduling • PXE service and multicast properties • Specify drives for content storage • IIS feature is required on all distribution points • Co-exist on secondary site server or remotely connected
Delivering on the Promise Delivering the Promise ?
Configuration Manager 2007 vs. 2012Delivering on the Promise
Delivering on the Promise Internet Based Managed Clients ?
Client Communication ConfigMgr 2007 ConfigMgr 2012 Intranet Intranet Internet Internet CEN Management Point PR1 Management Point Distribution Point PR1 Distribution Point PR2 Management Point Distribution Point Management Point Distribution Point PR1 (Site Properties) PR2 (Site Properties)
Client Communication ConfigMgr 2007 ConfigMgr 2012 Intranet Intranet Internet Internet CEN Management Point PR1 Management Point Distribution Point PR1 Distribution Point PR2 Management Point Distribution Point Management Point Distribution Point
Cross Domain/Forest: Internet-Based Client Management Intranet USA.woodgrove.com DMZ CAS Internet Software Catalog Machine policies only Machine and user policies PR1 Distribution Point Management Point USA.woodgrove.com clients Machine policies only WorkGroup clients Software Update Point Distribution Point Management Point
Out Band Management – Intel Active Management Technology (AMT) • Scenario refresher • Remote wakeup/shutdown/image boot with Windows running or not • Wakeup all clients in a collection prior to application deployments, software update and OSD operations • Key improvements in ConfigMgr 2012 • Increased scale for client wake-up (now 20K+ devices) • Aligned to RBA Admin, Remote Tools and Software admin roles • Support for latest firmware (AMT 6.1)