1 / 32

Advanced Infrastructure for System Center 2012 Configuration Manager SP1

Advanced Infrastructure for System Center 2012 Configuration Manager SP1. Kent Agerlund & Brian Mason ConfigMgr MVP’s. UD-B308. Who are we. Kent Agerlund Chief System Management Architect Work as consultant and trainer Microsoft MVP: Configuration Manager

balin
Download Presentation

Advanced Infrastructure for System Center 2012 Configuration Manager SP1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Advanced Infrastructure for System Center 2012 Configuration Manager SP1 Kent Agerlund & Brian Mason ConfigMgr MVP’s UD-B308

  2. Who are we • Kent Agerlund • Chief System Management Architect • Work as consultant and trainer • Microsoft MVP: Configuration Manager • Author: Mastering System Center 2012 Configuration Manager & System Center 2012 Configuration Manager Mastering the Fundamentals • Brian Mason • ConfigMgr Admin • Wells Fargo • Microsoft MVP: Configuration Manager • Author: Microsoft System Center 2012 Configuration Manager Administration Cookbook

  3. Agenda • SQL and Configuration Manager • Configuring SQL • Site system roles • Load balancing • Fault tolerance • Workgroup & Forest support

  4. SQL server considerations • Standard edition vs. SQL Enterprise • SQL Server version • Service Pack vs. CU • SQL server location • Local vs. remote • Cluster support • Estimated DB size • Rule of thumb is 5 MB per client • Plan the Site Maintenance tasks and status filter rules carefully • Depends on several factors like inventory frequency, AI, maintenance tasks. • Dedicated SQL instance for each site • Collation Case-insensitive collation (SQL_Latin1_General_CP1_CI_AS)

  5. SQL Server considerations • Limit SQL memory • 2 GB for OS/4 GB for CM and the rest for SQL • Reserve min 8 GB RAM in the buffer pool for the CAS/Primary Site and min 4 GB RAM for secondary sites. • 1 database file per core • 1 tempDB file for every two CPU’s • Change Autogrowth • CAP/Limit log files

  6. Enterprise disk layout Local Disk Layout Disk layout example • If cost is an issue or site is medium consider • Combining the tempDB and log files on the same drive • Combining the database files on the same drive • Combining all non OS files on the same drive (small site or lab environment) • Always plan for contentlibrary and backup files • Know your SAN team

  7. SQL memory Additional Files SQL DEMO

  8. I need to design my site for max uptime I must have multiple sites I need to cluster my SQL I need to mirror my SQL • Headaches • Complex environments • The DBA battle • Latency and replication • Solution = Keep It Simple SQL 2012 Always On rocks!

  9. Distribution Point, 250 Management Point, 10 Software Update Point, 8 State Migration Point SMS Provider, 2 Application Catalog web service point Application Catalog website point System Health Validator Reporting Services Fault tolerance – what are my options Multiple instances Non-Fault Tolerant • Site Server • Endpoint Protection Point • Asset Intelligence Point • EnrollmentPoint • EnrollmentProxy Point • Fallback status Point • Out of band service Point

  10. Site Systems Cloud Based Distribution Point Asset Intelligence sync point Out of band service point SMS Provider Enrollment proxy point SQL Server Distribution Point PXE Enrollment point Primary Site Server Application catalog Web services point Reporting Services point Application catalog Web site point System Health Validator Management Point Fallback Status Point Software Update Point State Migration Point

  11. Site systems and performance • Non-userfacing site systems canbeinstalled on the primary site server • Offload user facing site system roles first • Distribution Point • Management Point • Software Update Point • Application Catalog • Use SQL replicas on the Management Points • If needed offload reporting

  12. #4 Enterprise site ABOVE 100K Site systems and performance #1 Small site below 2K CAS SQL DB Primary site server All Roles PSS PSS SQL DB Primary site server SMS Provider Endpoint protection SQL DB Primary site server SMS Provider Endpoint protection #3 Enterprise site below 100K #2 medium site below 20K Management Point Software Update Distribution Point Application Catalog Management Point Software Update Distribution Point Application Catalog

  13. Management Point • Primary point of contact for clients • Support for 10 Management Points per primary site • Support for 1 Management Point per secondary site • Role is not “site aware” • Offload SQL work to database replicas

  14. DB replica on Management Point • Why • Performance • Fault tolerance • Additional SQL license • Not required • Requirements • SQL transactional replication • SQL Agent • Share to store replica data • Client Notification (BGB) Support included for SP1 • Prepare Broker service and certificates

  15. Configure MP replica Site Systems DEMO

  16. BGB (Client Notification) Service • Runs on each MP (via port 10123) • After setup, via SQL queries you still need to: • Enable the broker service • Export and swap certs (via SQL commands) MP01 MP01 EXEC sp_BgbConfigSSBForRemoteService 'REPLICA', '4022', '\\CM01\Storage$\MP01.CER', 'MP01.domain.fqdn', 'PRI_REPL‘ EXEC sp_BgbConfigSSBForRemoteService 'REPLICA', '4022', '\\CM01\Storage$\MP02.CER', 'MP02.domain.fqdn', 'PRI_REPL' EXEC sp_BgbConfigSSBForReplicaDB 'MP01.domain.fqdn', 'PRI_REPL', '\\CM01\Storage$\MP01.CER' EXEC sp_BgbConfigSSBForReplicaDB 'MP02.domain.fqdn', 'PRI_REPL', '\\CM01\Storage$\MP02.CER' MP02 MP02 PR1 PR1

  17. Distribution Points • On premise • Remote location support • throttling and scheduling • Pull Distribution Points • Pull from master • Offload processing from the primary site server • Cloud based

  18. Cloud Distribution Point • Purpose and Benefit • Use as fallback distribution point • 99.9% availability • Easy to scale • Requirements • Azure Subscription • Management Certificate • DNS • Client Settings • Cost

  19. Distribution Point WAN considerations • Preferred distribution point • Assigned using boundary groups • Allow fallback source location for content • Distribute the content for this package to preferred distribution points • On demand content push • Pull Distribution Points • Offloads processing on the site server • Daisy Chaining • Do not honor rate limits

  20. No local Distribution Points • Alternate Content Provider • Nomad from 1E • OneSite from Adaptiva • Benefits • Eliminates the need for a local DP • PXE lite • Fault tolerance • Microsoft BrancheCache

  21. Pull DP Content Pull Site Systems DEMO

  22. Software Update Points - SUPList • Multiple SUPs in SP1 • All SUPs are Active • Client will stay with the same SUP until it fails • Client randomly selects a SUP at install • Multiple SUPs are not as robust as NLB

  23. Software Update Points - Costs • Scan cost of switching that could be up to 4,500 MB per client • Scan cost 12x better if you use a shared DB • Shared DB means a single point of failure • The big post to read on this: • http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx • Watch WUAHandler for the change

  24. Forest and Workgroup Support

  25. Workgroup support • Device Oriented • Installing the client • Client push doesn’t work in ConfigMgr 2012. • System Center 2012 Orchestrator • Accounts • Network Access Account

  26. Cross Domain/Forest support • All site servers must be in a fully two way trusted domain • User facing site systems can be deployed in untrusted forests • DMZ • Deploy remote site roles in DMZ for managing Internet-Based Clients. • All Internet based clients receives machine policies • User policy requires: • One way trust between DMZ and the forest to which the client belongs. • Extend AD schema is remote forest

  27. Discovery Publishing Site information Installing clients Cross forest support DEMO

  28. Links and Questions • Connect with the speakers • Twitter: @Agerlund & @AbetterPC • Mail: kea@coretech.dk & Brian@@AbetterPC.com • Blog: http://blog.coretech.dk/author/kea & http://www.mnscug.org/blogs/brian-mason • Blog: Management Point replica • http://blog.coretech.dk/kea/working-with-database-replicas-on-your-management-point/ • http://myitforum.com/myitforumwp/2012/08/06/next-sccm-guru-webcast-features-brian-mason/ • Planning for clients • http://technet.microsoft.com/en-us/library/gg712701.aspx • Planning for Cloud based Distribution Points • http://technet.microsoft.com/en-us/library/jj613909.aspx • Supported hardware and software configurations • http://technet.microsoft.com/en-us/library/gg682077.aspx

  29. Evaluation We want to hear from you! Complete your session evaluations today and enter to win prizes daily. Provide your feedback at a CommNet kiosk or log on at www.2013mms.com. Upon submission you will receive instant notification if you have won a prize. Prize pickup is at the Information Desk located in Attendee Services in the Mandalay Bay Foyer. Entry details can be found on the MMS website.

  30. Resources Access MMS Online to view session recordings after the event. http://channel9.msdn.com/Events

  31. © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related