1 / 28

Kent Agerlund

Kent Agerlund. Configuration Manager Advanced Infrastructure. Who am I. Kent Agerlund Profession Chief System Management Architect & Co-founder of Coretech Coretech A/S, System Center Gold Partner Work as consultant and trainer Titles Microsoft MVP: Configuration Manager

rance
Download Presentation

Kent Agerlund

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. Kent Agerlund • Configuration Manager • Advanced Infrastructure

  2. Who am I • Kent Agerlund • Profession • Chief System Management Architect & Co-founder of Coretech • Coretech A/S, System Center Gold Partner • Work as consultant and trainer • Titles • Microsoft MVP: Configuration Manager • Microsoft Certified Trainer • MCITP Enterprise Administrator • Communities • Founder of SCUG.dk • Moderator on Microsoft TechNet Forums • Member of the System Center Alliance Team • Member of the System Center Influencers Team • Author • Mastering System Center 2012 Configuration Manager • System Center 2012 Configuration Manager Mastering the fundamentals

  3. Agenda • SQL and Configuration Manager • Placement of the site system roles • Load balancing • Fault tolerance • Forest support

  4. SQL server considerations • Standard edition max 50.000 clients in the hierarchy • Dedicated SQL instance for each site • Collation Case-insensitive collation (SQL_Latin1_General_CP1_CI_AS) • SQL Server version • Minimum SQL Server 2008 SP2 with CU7 • Recommended SQL Server 2012 CU3 • SQL server location • Local VS remote (1 GB connection between site server and site DB) • Cluster support • Plan the Site Maintenance tasks and status filter rules carefully • Estimate DB size • Depends on several factors like inventory frequency, AI, maintenance tasks etc. • Rule of thumb is 5 mb pr. client

  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 pr. core • 1 tempDB file for every two CPU’s • Change Autogrowth to 1 GB

  6. Disk layout example Enterprise disk layout Disk layout • 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

  7. DEMO SQL SQL memory Files

  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. Fault tolerance – what are my options Multiple instances Non-Fault Tolerance Site Server Endpoint Protection Point Asset Intelligence Point EnrollmentPoint EnrollmentProxy Point Fallback status Point Out of band service Point • 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

  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 SQL DB Primary site server SMS Provider Endpoint Asset Intelligence • 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 Management Point Software Update Distribution Point Application Catalog

  12. Management Point • Primary point of contact for clients • Support for 10 Management Points pr. primary site • Support for 1 Management Point pr. secondary site • Role is not “site aware” • Offload SQL use a database replica

  13. DB replica on Management Point • Why • Performance • Fault tolerance • Additional SQL license • Not required • Requirements • SQL replication • SQL Agent • Share to store replica data • Uses traditional SQL replication • BGB Support needed for SP1 • Prepare Broker service and exchange certificates

  14. DEMO Site Systems Placement of Site System Roles Configure MP replica

  15. Distribution Points • On premise • Remote location support • throttling and scheduling • NO_SMS_ON_DRIVE.SMS • Cloud based • Pull Distribution Points

  16. 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

  17. DEMO Site Systems Cloud based DP

  18. Distribution Point WAN considerations • Preferred distribution point • Assigned using boundary groups • Allow fallback source location for content • Formerly known as protected boundaries • 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

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

  20. DEMO Site Systems Pull DP Content Pull

  21. Software Update Points • Multiple Software Update Points in SP1 • All Software Update Points are Active • Client will stay with the same SUP until it fails • Client randomly select a SUP • Multiple SUP’s are not as robust as NLB

  22. DEMO Site Systems SUP

  23. Forest and Workgroup Support

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

  25. 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

  26. Cross Domain/Forest corp.contoso.com SC2012.lcoal corp.sc2012.lcoal CAS MP DP hr.sc2012..local PR2 PR1 PR2 DP MP MP DP

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

  28. Q & A

More Related