1 / 50

Operations Manager 2007 Components Overview

Operations Manager 2007 Components Overview. OpsMgr history . In the beginning there was OnePoint… Then Microsoft bougth them. Now the product rules!!. Why use OpsMgr 2007? . Central Monitoring of Servers, Applications, Services and Clients End-to-end application monitoring

georgia-stanley
Download Presentation

Operations Manager 2007 Components Overview

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. Operations Manager 2007 Components Overview

  2. OpsMgr history • In the beginning there was OnePoint… • Then Microsoft bougth them. • Now the product rules!!

  3. Why use OpsMgr 2007? • Central Monitoring of Servers, Applications, Services and Clients • End-to-end application monitoring • Central Reporting • Alerting • Notifications by SMS or E-mail • Knowledge is in the product by importing MP’s • Create own MP’s

  4. Use it to… • Become a happy admin – less users at your desk • Get the joy of life back – no more logdigging • Become the boss’s best friend – reports • Go home at 17:00 and still be in charge of your systems • …

  5. Monitoring • Text logs • Event logs • Performance counters • Scripts i.e. WMI, VB, Jscript etc. • SNMP

  6. OpsMgr 2007 Components • Operational Database • - Operational data store • - Configuration store • What’s New? • Customizable database name • Installed using a SQL script • Remote database setup using command line Root Management Server - Central point for configuration management and extensibility - Supports high availability Management Server - Sends configuration and receives data from Agents - Same as MOM 2005 • Console • Integrated experience for operators and • administrators • Role based security ensures optimized • experience for all users • What’s New? • Unified Console • Command Shell

  7. OpsMgr 2007 Components • What’s New? • Multiple management groups • Custom data warehouse name • Reporting Data Warehouse • Long term data store • Supports high availability • Reporting Server • - Provides reports • Installed on SQL Reporting Services • 2005 SP1 • What’s New? • Console integration • Agent • Used to monitor servers and clients • What’s New? • Leverages Active Directory • Can be deployed using SMS, Sys-prep or Command Shell

  8. New OpsMgr 2007 Components Audit Database - Stores security events - Supports high availability Audit Collector - Collects events from the Audit Collection enabled agents Web Console Server - Thin client much like OWA - View Topology diagrams and performance charts - Run Tasks Gateway Server - Monitors Agents in untrusted domains - Requires certificates

  9. What about System Center Essentials • For smaller customers • Limited SCCM function • Limited SCOM function • Limited Reporting

  10. Common Customer Deployment Topologies • Three typical categories of customers • Consolidated environment • Distributed environment

  11. Three Typical Categories of Customers Topology: Single AD Forest Servers: 15 – 500 M Medium Topology: Single/Multiple AD Forests Servers: 500 – 2500 L Large Topology: Multiple AD Forests Servers: 2500 + E Enterprise

  12. Medium OrganizationManaging 15 to 500 servers M

  13. Large OrganizationManaging 500 to 2500 servers L

  14. Enterprise OrganizationManaging 2500 plus servers Redmond Management Group Asia Management Group E Europe Management Group

  15. Installing SCOM 2007 – I: overview • Choose one of the models • Run SCCP 2007 • Buy your boxes • Install DB • Install RMS • Install additional MS’s • Install Reporting

  16. System Center Capacity Planner • SCCP V1 SP1 - October 2006 • Added supported for Vista • Exchange 2003 and MOM 2005 only • SCCP V2 – Beta H1 2007 • Models for OpsMgr 2007 and Exchange 2007 • SCCP V2 is the official tool for OpsMgr 2007 Deployment Planning • Accounts for new OpsMgr topologies

  17. Installing SCOM 2007 – II: prereq: Active Directory Domain Services • Domain: Windows 2000 Native or later • Forest: Windows 2000 Native or later

  18. Installing SCOM 2007 – III prereq: Database Server • X86 or X64 @ 1.8 GHz • 1 GB • 10 GB Database Size • Windows Server 2003 SP1 (or R2) STD or ENT edt. • SQL Server 2005 SP1 STD or ENT edt.

  19. Installing SCOM 2007 – IV prereq Management Server (RMS or MS) • X86 or X64 @ 1.8 GHz • 1 GB • 5 GB Files Size • Windows Server 2003 SP1 (or R2) STD or ENT • .NET Framework 2.0 and 3.0 • Microsoft Core XML Services 6.0

  20. Installing SCOM 2007 – V prereq Operations Console • X86 or X64 @ 1 GHz • 1 GB • 5 GB Files Size (check only) • Windows Server 2003 SP1 (or R2) STD or ENT • Windows XP Professional SP2 • .NET Framework 2.0 and 3.0 • Office Word 2003 with .NET Programmability Support • Powershell 1.0 • Visual Studio Tools for Office (knowledge authoring)

  21. Installing SCOM 2007 VI prereqAgents • X86, X64 or IA-64 OS minimum • OS minimum • 30 MB (Files Size) • Windows Server 2003 SP1 (or R2) STD, ENT, Datacenter, SBS or STG • Windows 2000 SP 4 Pro, STD, ENT or Datacenter • Windows XP Pro SP2 • Windows Vista Business, ENT or Ultimate • Core XML 6.0 and Windows Installer 3.1

  22. Installing SCOM 2007 – VII prereq: Reporting Database Server • X86 or X64 @ 1.8 GHz • 1 GB • 10 GB Database Size • Windows Server 2003 SP1 (or R2) STD or ENT edt. • IIS 6.0 • SQL Server 2005 SP1 STD or ENT edt.

  23. Installing SCOM 2007 – VIII prereq Gateway Server (same as RMS/MS) • X86 or X64 @ 1.8 GHz • 1 GB • 5 GB Files Size • Windows Server 2003 SP1 (or R2) STD or ENT • .NET Framework 2.0 and 3.0 • Microsoft Core XML Services 6.0

  24. Installing SCOM 2007 – IX prereqACS Database Server • X86 or X64 @ 1.8 GHz • 1 GB • 20 GB Database Size • Windows Server 2003 SP1 (or R2) STD or ENT • SQL Server 2005 STD or Ent

  25. Installing SCOM 2007 – X prereqMS with ACS or AEM Fileshare • X86 or X64 • 1 GB • 10 GB free • Windows Server 2003 SP1 (or R2) STD or ENT • .NET Framework 2.0 and 3.0 • Microsoft Core XML Services 6.0

  26. Installing SCOM 2007 – XI creating accounts • Management Server Action Accnt • Needs admin rights on Server that will be monitord by Agents • Used to install agents and for responses • Agent Action Accnt • Used to monitor and respond • Local users, local performance users, log on locally • SDK and Config Svc Accnt • Used to access the database • Should be local system, could be domain user • OpsMgr Admins • Used to Administer SCOM • Is a group

  27. After Installation • Update AD • MOMADAdmin.exe. <ManagementGroupName> <OpsMgrAdminsGroup> <RootHealthSvcComputer> <DomainName> • Creates AD objects for SCOM • Make MS’s register in AD • HKLM\System\CurrentControlSet\Services\HealthService\Parameters\ConnectorManager => EnableADIntegration=1

  28. Configuring New OpsMgr 2007 Features • Deploying in untrusted domains • Deploying Audit Collection components • Deploying reporting components

  29. Deploying in Untrusted DomainsCertificate Based Authentication No Trust Domain A Domain B Agent Agent Mutual Auth: Kerberos Port: 5723 Mutual Auth: Cert Based Agent

  30. Deploying in Untrusted DomainsUsing Gateway Server No Trust Domain A Domain B Agents Mutual Auth: Kerberos Agents Port: 5723 Mutual Auth: Cert Based

  31. Deploying in Untrusted DomainsUsing Gateway Server Mutual authentication is required by OpsMgr 2007 Benefits of Gateway Server: • Multiple management groups are not required • Only two certificates need to be installed and updated • Network traffic across the firewall is only between Gateway Server and Management Server • No direct communication between Gateway Server and Operational Database Server or Root Management Server • Support for Certificate Authority issued certificates or third party certificates

  32. Deploying the Audit Collection ComponentsInstalling Audit Database and Collector • What is Audit Collection? • Functionality to collect security events from computers • Helps with security legislation requirements • How to deploy Audit Collection? • Install Audit Database • Install Audit Collector • Enable Audit Collection on OpsMgr Agent by running a task in the Console

  33. Deploying the Audit Collection ComponentsInstalling Audit Database and Collector

  34. Deploying the Audit Collection ComponentsInstalling Audit Database and Collector Audit Collector cannot be clustered Each Collector will need its own individual Audit Database Gateway Server can be used as an Audit Collector Audit Collector and Audit Database components can be installed on the same server

  35. Deploying the Reporting ComponentsUnderstanding Reporting Components Data Flow Writes to OpsDB Writes to DW Communicates with Health Service Sync data from DB to DW Connects to SDK Reports Access Report Parameters

  36. Deploying the Reporting ComponentsInstalling Reporting Database and Server Users must have a dedicated SQL Reporting Services instance for OpsMgr 2007 (RC1 Reporting Setup caveat only) Data Reader Account must be a Local Admin on the SQL Reporting Services 2005 Server (RC1 Reporting Setup caveat only)

  37. Upgrade and Migration Considerations • Supported upgrade/migration paths • Steps to upgrade from RC2 to RTM • Transitioning from MOM 2005 to OpsMgr 2007

  38. Supported Upgrade/Migration Paths MOM 2005 MOM 2005 SP1 OpsMgr 2007 Beta 2 OpsMgr 2007 RC 1 OpsMgr 2007 RC 2 OpsMgr 2007 RTM Upgrade MP Conversion

  39. Side by Side MigrationSame Hardware Approach Management Group 1 - 2005 2005 2007 2005 2007 2005 2007 Management Group 2 –2007

  40. Side by Side MigrationNew Hardware Approach Management Group 1 - 2005 Management Group 2 - 2007 2005 2007 2005 2007 2005 2007

  41. Advanced Topics • High Availability considerations • Clustering the Root Management Server • Deployment security considerations • Troubleshooting tips and tricks

  42. High Availability Consideration

  43. High Availability Consideration

  44. Clustering the Root Management Server Setup experience is different from standalone database cluster setup Documentation is provided in RC1 to setup Root Management cluster Promotion of a Management Server to Root Management Server for disaster recovery will available by RTM

  45. Deployment Security Considerations

  46. Deployment Firewall/Security Considerations

  47. Troubleshooting Tips and Tricks • Prerequisite Checker • Open Log File which can be found in the %Temp% directory and find prereqreport.xml • Run Debug View Tool while running prerequisite checker • http://www.sysinternals.com/Utilities/DebugView.html • Setup • Open Log File which can be found in the %Temp% directory and look for ‘value 3’ return code • HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups\<MS Name>

  48. Troubleshooting Tips and Tricks Management Server Event ID: 29102 Health Service asking for new configuration Event ID: 29102 MOM Health Service running on “MS" has contacted MOMCFG Service to get configuration. Event ID: 21025 Health Service received new configuration Agent Event ID: 21024 Health Service asking for new configuration Event ID: 1200 Health Service requests new Management Packs Event ID: 1201 New Management Packs have been received %Program Files%\System Center Operations Manager 2007\Health Service State\Management Packs %Program Files%\System Center Operations Manager 2007\Health Service State\Connector Configuration Cache\<MG name>\MOMConnector.Config.xml

  49. Troubleshooting Tips and Tricks • Servers and Clients Discovery • http://blogs.technet.com/momteam/archive/2006/10/24/having-trouble-discovering-computers-using-the-opsmgr-2007-discovery-wizard.aspx • Reporting Server • Check to see if you can open http://<servername>/reports and http://<servername>/reportserver • Run Reporting Services Configuration Manager to verify SQL Reporting Services is healthy

  50. Summary • OpsMgr 2007 is simple and cost effective to plan and deploy • Simple but not simplistic it’s robust enough to handle the most complex topologies • Take advantage of new features to consolidate functions and add more value to your organization

More Related