The Best of MMS 2013


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Best of MMS 2013

  1. 1. Best of MMS 2013
  2. 2. Quick FactsAbout Us• 23rd Year• Grand Rapids &Royal Oak• 30 StaffApproach• VendorIndependent• Non-reseller• ProfessionalServices OnlyPartnerships• Microsoft Gold• VMwareEnterprise• Citrix Silver• Cisco Premier• Novell Gold
  3. 3. Microsoft Gold PartnerCompetenciesThree GoldFive SilverSuccessesCustomerExcellence AwardVirtual TechnicalSpecialist (VTSP)Managed PartnerNumerous PartnerAwardsPinpointMicrosoft’s officialpartner directory5-star rating
  4. 4. Expertise
  5. 5. Get Social with C/D/
  6. 6. Your PresenterErik GilreathMCSE, MCITP, CNE, CCNA, CCDA, CCA, CCEA• Consultant with C/D/H• Currently focusing on SystemCenter, infrastructure andvirtualization• Been with C/D/H since
  7. 7. Today’s Agenda• Keynote Highlights• Keynote Debrief• System Center Overview: V-SCOOPED• SQL Configuration Tips for System Center• Global Services Monitoring• System Center Advisor
  8. 8. Keynote Highlights• Started 25 minutes late due to loss ofInternet – when all demos use the cloud,the Internet is pretty important.• Key takeaways:– Cloud optimize your business– Mix public and private clouds for greatestflexibility– Microsoft workloads run best on MicrosoftCloud platforms
  9. 9. Keynote Highlights (cont.)• Public cloud– Microsoft Azure• Private cloud– Windows Server 2012– SQL Server 2012– System Center 2012• Microsoft cloud products are enterprisegrade and ready to scale and deploy
  10. 10. Keynote Highlights (cont.)• Server 2012 Hyper-V– Supports the largest virtual disk– Largest scale unit: 64-node cluster. Capable of hosting8,000 VMs• A few fun facts:– Microsoft’s test environment provisioned 80,000 VMs in asingle day– On an average day, spin and tear down 20,000 VMs a day– Exchange 2013 was able to host 48,000 mailboxes on asingle Hyper-V host– SharePoint server farm (5 servers) was able to host1,000,000 users on a single Hyper-V server
  11. 11. Keynote Highlights (cont.)• Hyper-V is THE BEST platform for allMicrosoft workloads (SQL, Exchange,Lync, System Center, etc.)• Watch the keynote online at:
  12. 12. Keynote Debrief• Went through and showed how every demo inthe keynote was created• Showed there were no smoke and mirrors(although there was the occasional 10GBconnection)• Showed that they actually use their productsto do incredible things• Watch it online:
  13. 13. Domino’s Pizza Case Study• 15,000 Hyper-V VMs managed with SystemCenter• 99% reduction in help desk calls over “theother guys”• 28% faster hard drive reads• 38% faster memory operationsCase study video overview: study:
  14. 14. V-SCOOPEDVirtual Machine ManagerService ManagerConfiguration ManagerOrchestratorOPerations ManagerEndpoint ProtectionData Protection Manager
  15. 15. System CenterVirtual Machine Manager• Heterogeneous Hypervisor ManagementMicrosoft, VMware, Citrix (Public and Private Cloud)• Enterprise Toolset for Hyper-VLibraries, Templates, Live-Migration, Backup, Dynamic Optimization• Service and Application ManagementIntegrates with App Controller, App-V, and Azure• Optimization and StandardizationPower, Compute Resources, Bare Metal Hypervisor Deployment• New in SP1: Highly Available VMM MSSMB 3.0, Cluster-Free Live Migration, Network Virtualization
  16. 16. System CenterVirtual Machine Manager
  17. 17. DEMO
  18. 18. Managing Services in Multiple CloudsPublicPrivatePrivatePublic
  19. 19. App Controller SP1– Common experience acrosspublic and private clouds– Platform as a Serviceapplication– Windows Azure virtual machine(SP1)– Start, stop, remote desktop– Scale, upgrade
  20. 20. App Controller is Cloud IndependentWindows Azure Hosted SiteOn-PremiseDR Site
  21. 21. System CenterService Manager• ITIL / MOF Aligned IT ProcessesIncident, Problem, Change, Knowledge Management - CMDB• Integrations with SC2012 SuiteOpsManager, ConfigMgr, Orchestrator, VMM• Integration with Microsoft InfrastructureExchange, Active Directory, SharePoint, Project, Azure• User Self Service CatalogDriven by Workflows and Orchestrator Runbooks• New in SP1: Cost Center ChargebackSQL 2012 & OLAP, Windows 8 SSP Support
  22. 22. System CenterService Manager
  23. 23. Stacking Up SCSM• There are NO LEADERS• SCSM hasn’t even made itto “the quadrant”*• Big players are BMC,ServiceNow, LANDesk,IBM, CA• Deployment is highlyprovider focused*Do you really care?
  24. 24. SCSM: Perspective• Biggest strength is the suite• Green field: for better or worse• Single pain of glass…• Designed for scale• Console is not elegant
  25. 25. SCSM: Server Roles• Management Server• SQL Server: CMDB• Data Warehouse Management Server• SQL Server: DW• Self Service Portal• Service Manager Console
  26. 26. SCSM: Server RolesSource: SCSM Infrastructure Planning and Design Guide
  27. 27. SCSM IPD GuideSource: SCSM Infrastructure Planning and Design Guide
  28. 28. After Installation• Establish Process• Customize Lists• Author Templates• Runbook Automation• Authoring Tool• Integrate System Center Suite• Third Party Offerings
  29. 29. System CenterConfiguration Manager• Client Application and Desktop DeploymentUpdates Management, Operating System Deployment• Multi-Platform Device ManagementiOS, Android, Mac, Linux, Unix• EndPoint Protection• Hardware and Software InventoryReporting, Asset Intelligence• New in SP1: Windows 8 and Mobile DeviceIntune Integration for On-Demand MDM, Robust Alerting
  30. 30. System CenterConfiguration Manager
  31. 31. Gartner Magic Quadrant –Client Management Tools
  32. 32. SCCM 2012New• Improved settingsmanagement withremediation• Integrated anti-malware• Delegated administrationBenefits• Reduce compliancecomplexity• Reduce cost throughintegrated securitySP1 release includes the ability to manage and deploy thinclients, POS devices, and other Windows embeddeddevices, as well as create and provision Windows To Goportable workspaces
  33. 33. SCCM 2012 Feature Set• Systems Management/Remote Control• Inventory• Software Metering• Software Updates• Application Management• Operating System Deployment• Endpoint Protection• Mobile Device Management
  34. 34. Software Updates• Integrated with Windows Server UpdateServices (WSUS)– Leverages the client agent– No need for GPOs in this case• Create packages of updates for deployment(just like applications)• Updates can be configured for automaticapproval– Endpoint Protection definition updates
  35. 35. Application Deployment• Deployment Type• Detection Method• Install Command• Requirement Rules• Dependencies• Supersedence• Updates
  36. 36. System CenterOrchestrator• Graphical IT Workflow EngineActivities Managed through Custom Workflows• Automation for System Center SuiteOpsManager, ConfigMgr, ServiceMgr, DPM, VMM, Self-Service• Extends to entire Microsoft stackWindows Server, SQL, Exchange, SharePoint, FTP• Extensive Third Party IntegrationVMware, HP, IBM• New in SP1: Server 2012 and SQL 2012
  37. 37. System CenterOrchestrator
  38. 38. Orchestrator Automation• Several good sessions on Orchestratorautomation and organization• Automate as much as you can• Not everything makes sense to automate• Orchestrator ties into all of the SystemCenter applications• With the ability to call PowerShell scriptsand EXEs the power of Orchestrator isseemingly limitless.
  39. 39. DEMO
  40. 40. System CenterOperations Manager• Server and Application MonitoringExtensible through Management Packs• Alerts and Incident GenerationIntegrates with Exchange and/or ServiceMgr• Agentless MonitoringUnix, Linux, Network Devices, Web Applications• Synthetic TransactionsSimulate Client Activities• New in SP1: Improved Application Monitor360 .NET Dashboards, TFS Integration, Global Service Monitoring, System CenterAdvisor
  41. 41. System CenterOperations Manager
  42. 42. Why SCOM is so rarely installed• First iterations were less than stellar• Easy to install poorly• More complicated than it looks• Poor planning• Not understanding what SCOM really does• Bad reputation from people who use orinstall it incorrectly
  43. 43. Why it’s a mistake not to install:SCOM in real life• Notifications of system issues• Notifications of possible problems• Alerts of performance issues• Correct issues with the use of scripts• Generates help desk tickets
  44. 44. SCOM Installation Tips• Decide ahead of time what MPs to install– Exchange / IIS / SharePoint / SQL / etc.• Install one MP at a time– Let it bake a week or two– Start with Windows Core– Create custom MP for each installed MP foroverrides– Name each custom MP with the same startingletters• Alert Monitors vs. Alert Rules
  45. 45. Monitoring Services
  46. 46. Monitoring Services
  47. 47. Synthetic Transactions• Real time actions performed on monitoredobjects– Test website responsiveness– Monitor database performance– TCP port monitoring
  48. 48. System CenterEndpoint Protection• Enterprise Malware and Security PlatformAntivirus, Firewall• Integrates with ConfigMgr• Seamless UpdatesSoftware Update Point, Automatic Deployment Rules• New in SP1: ADR Template
  49. 49. System CenterEndpoint Protection
  50. 50. System CenterData Protection Manager• Volume Shadow Copy Based Backup• Disk-to-Disk: Archive to Tape• SQL, Exchange, Hyper-V, SharePoint• New in SP1: Live Migration SupportAzure Online Backup, “Phase 13”
  51. 51. System CenterData Protection Manager
  52. 52. V-SCOOPED
  53. 53. Data Center Automation• Template Based VM Deployment• Monitoring of Critical Servers• Backup and Disaster Recovery• Dynamic Scaling of Heavy Use Applications
  54. 54. Client Automation• User Driven Incident Management• Self-Service Request Portal• Automated Provisioning• Web Based Knowledgebase
  55. 55. Service Desk Automation• Automated Incident Remediation• Change Management Workflows• Runbook Driven Escalation• ITIL / MOF Aligned Knowledge Management
  56. 56. SQL Server Configuration• Proper installation and configuration of MicrosoftSQL Server is critical for System Center products.• Misconfiguration of SQL Server can cause issues:– High CPU– Memory shortages– Inbox/file backlogs– Workflow delays– Stale or inaccurate data in reports• Carefully consider and plan for data volumeSystem Center products generate and the loadthis will place on SQL server
  57. 57. SQL 2012: What’s new?• Increased performance and scalability• Power View – SQL Reporting Servicesadd-in for SharePoint• PowerPivot - Excel add-in• PowerShell support to enable automation• AlwaysOn
  58. 58. SQL 2012 AlwaysOnWhat is AlwaysOn?• Provides SQL server high availability and disasterrecovery for databases• Failover cluster instance for SQL server instances• Uses Windows Server failover clustering• Supported in several System Center 2012 products• Requires SQL 2012 Enterprise edition
  59. 59. SQL 2012 AlwaysOn & SystemCenter 2012SQL Server 2012 AlwaysOn supported on:• App Controller• Operations Manager• Orchestrator• Service Manager• Virtual Machine ManagerSQL Server 2012 AlwaysOn not currently supportedon:• Data Protection Manager• Configuration Manager
  60. 60. SQL Memory• Buffer Pool• Consists of 8KB pages• Data cache stored here• Execution plans that is less that 8KB• SQL engine• SQL components• Execution plan that is more than8KB• SQL CLR (Common LanguageRuntime)• Also called MemToLeave 60
  61. 61. Maximum Server MemoryConsider limiting SQL to 50%-80% of total memory if SQL willco-exist with another System Center productExample: One server running ConfigMgrprimary site server & SQL databaseConsider limiting SQL to 80%-90% if SQL server is dedicatedExample: Dedicated SQL server that onlyhosts databases or a SQL clusterNOTE: Setting the maximum and/or minimum server memorysettings only controls the Buffer Pool MemorySQL: Memory Settings
  62. 62. SQL: Memory SettingsMinimum Server Memory• SQL does not allocate Minimum Server Memory at start up• Grows until reaches maximum• Once Buffer Pool hits Minimum Server Memory, SQL will notrelease the memoryNOTE: Setting the Maximum and/or Minimum Server memory settingsonly controls the Buffer Pool Memory
  63. 63. Detecting SQL Memory Pressure• SQL Buffer Pool Memory pressure happenswhen SQL does not have enough memory tohold data in memory• Can result in excessive I/O• Check the following perfmon counters:– SQL: Buffer Manager  Lazy writes/sec goes up– SQL: Buffer Manager  Page Life Expectancygoes down– SQL: Buffer Manager  Free Pages goes down
  64. 64. SQL: Useful SQL PerfmonCounters• SQL Server: Buffer Manager– Buffer cache hit ratio(>90-95%)– Free pages(>640)– Lazy writes/sec (<20)– Page life expectancy (>300)– Page reads/sec (<90)– Page writes/sec (<90)• SQL Server: Memory Manager– Target Server Memory (KB) (Target >= Total)– Total Server Memory (KB) (Target >= Total)
  65. 65. Monitor SQL Performance• SQL Server: Memory Manager: Tellshow much memory SQL Server wouldlike to use to operate efficiently• SQL Server: Memory Manager: Tellshow much memory SQL Server isusing• If Total Server Memory >= TargetServer Memory, may indicate SQL isunder memory pressure
  66. 66. • CPU– Processor: %Processor Time – If 80-90% for asustained period, identify the process withProcess: %Processor Time and determine iffaster/more processors are needed– Processor: %Privileged Time – If counter isconsistently high and in-line with Physical Diskcounters, disk sub-system is bottleneck• Memory– SQL Server: Buffer Manager: Buffer Cache HitRatio – less than 90% indicates memorypressure– Memory: Pages/sec – a high rate for thiscounter indicates excessive pagingMonitor SQL Performance
  67. 67. Monitoring via Operations Manager• Deploy the System Center Management Packfor SQL Server• Monitors SQL Server 2005, 2008, 2008 R2 and2012• Monitors the database instances, the databasesthemselves, and the SQL agents• Provides a wealth of data around performance,availability and configuration.
  68. 68. SQL: AutoGrowIf Autogrow setting is too small:• SQL spends significant processingtime autogrowing the database• Each file grow in log file creates aVirtual Log File (VLF)• Excessive VLF may causeperformance issues:– When VLF>250, performance will be impacted– When VLF >10000, SQL will take longer tobring up databaseAdditional information on VLFs available at
  69. 69. SQL: AutoGrowIf Autogrow setting is too large:• During autogrow, SQL will write zeroes in thespace that is grown.• During autogrow, queries involving updates,inserts, deletes may be blocked.• Can enable Instant File Initialization for the DB butpossible security risk as deleted data may still beviewable• Instant File Initialization does not work for log fileAdditional information available at
  70. 70. TempDB• TempDB database typically heavily used• Consider pre-sizing the data file. Don’t rely onautogrow.• If you need to autogrow, use fixed amount to avoidfrequent growth intervals, which affects performance(10% of tempdb size good starting point)• Divide TempDB into multiple files, one data file perCPU, and each file should be set to the same size• Additional information here:
  71. 71. Storage• Isolate transaction log files from database filesat disk level• Recommended to have at least 20% free diskspace on all drives. Important for performanceand to prevent running out of space.
  72. 72. • SQL Server and System Center 2012 supportedon physical and virtual servers• More customers using virtual servers for SQL andSystem Center infrastructure. Benefits include:– Reduced server hardware costs– Reduced data center costs– Easier to move virtual servers from one host to another– Easy to add/remove memory, CPU, etc. to/from guestOS– Snapshot technology allows rollback for issues, upgradefailure, etc.
  73. 73. • If you use virtual servers:– Verify host server can handle the additional load– Slow disks, low memory and high CPU utilization can havemajor impact on SQL Server and System Center products– Avoid using dynamic virtual drives (VHDs) as they candecrease performance– Allocate at least two virtual CPUs for SQL Server instance– Do not allocate more virtual CPUs than the number ofavailable logical CPUs• Ensure recommended memory/CPU/disk requirementsare at least met, if not exceeded. Don’t reduceresources because it’s a VM
  74. 74. SQL: Local or RemoteFor System Center 2012 product X,should I use local or remote SQL server?Answer: It depends!
  75. 75. Product Specific GuidanceLook at product specific planning guidance.Some links below:• Configuration Manager:• Service Manager: SM Sizing Helper Tool, part of SM jobaids• Operations Manager: OM 2012 Sizing Helper Tool
  76. 76. Global Service Monitoring• Azure based service that ties into SCOM• Available free with Software Assurance• Monitors from both inside and outside– Monitor applications from 15 different locations• Two kinds of monitors– Web Application Availability– Visual Studio Web Tests
  77. 77. Global Service Monitoring -Installation• Signup for GSM:• If doing Visual Studio tests, import the AlertAttachment MP:• Import the GSM MPs into OpsMgr 2012 SP1• Configure GSM in OpsMgr 2012 SP1 withyour GSM account• Start configuring tests!
  78. 78. Web Application Availability Monitor• Test is defined as one URL from onelocation• One test every 5 minutes is the mostfrequent interval• Total tests = # tests * # locations• Total tests cannot exceed 25 persubscription
  79. 79. Visual Studio Web Tests• Test is defined as one .webtest file• One test every 5 minutes is the mostfrequent interval• Total tests = # tests times # locations• Total tests cannot exceed 25 persubscription• Microsoft Visual Studio Ultimate 2010 or2012 required to view test results
  80. 80. Global Service Monitor
  81. 81. DEMO
  82. 82. System Center Advisor• Cloud-based service that examines yourMicrosoft-based installations• Available free to everyone• Alerts generated due to improperconfiguration, potential issues, missingpatches, or simply straying from bestpractices• Remediation recommendations based onthousands of MS Support cases
  83. 83. How System Center Advisor worksSERVERCONFIGURATIONSMicrosoft ServersBEST PRACTICES& RECOMENDATIONS
  84. 84. System Center Advisor
  85. 85. Royal Oak306 S. Washington Ave.Suite 212Royal Oak, MI 48067(248) 546-1800Grand Rapids15 Ionia SWSuite 270Grand Rapids, MI 49503(616) 776-1600Thank