210 likes | 594 Views
Deploying SCOM 2007 . Eric Denekamp Trainer Consultant http://blogs.infosupport.com/ericd. Agenda. Why SCOM 2007 Architecture Prerequisites and additional software Deployment steps Migrating Management Packs from 2005 Q&A. Why SCOM 2007?. Monitor your Services… …and Devices
E N D
Deploying SCOM 2007 Eric Denekamp Trainer Consultant http://blogs.infosupport.com/ericd
Agenda • Why SCOM 2007 • Architecture • Prerequisites and additional software • Deployment steps • Migrating Management Packs from 2005 • Q&A
Why SCOM 2007? • Monitor your Services… • …and Devices • Pro-active as well as Re-active management • Keep track of health of • Systems • Devices • Applications
Entity SQL SVR Service Windows Service State Basic Health Model Of An Entity Overall Health Availability Health Performance Health Security Health Configuration Health
Basic Model - Distributed Application Structure “Messaging” Health Models
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
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 • Agent • Used to monitor servers and clients • What’s New? • Leverages Active Directory • Can be deployed using SMS, Sys-prep or Command Shell
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
Prerequisites SCOM • Windows Server 2003 SP1 • SQL server 2005 SP1 • .Net Framework 3.0 (so also 2.0) • Windows Powershell • MDAC Version 2.8.1022.0 • World Wide Web Service (optional for the WebConsole)
Prerequisites SCOM reporting • Windows Server 2003 SP1 • SQL server 2005 Reporting Services SP1 • .Net Framework 3.0 (so also 2.0) • Windows Powershell • World Wide Web Service
Deployment Steps • Install prerequisites • Install SCOM 2007 • Install agents • Deploy management pack • Tune management pack • Deploy management pack…
Find Systems Install agents Monitor services
Migrating Management Packs • Normal AKM files (MOM2005) migrate in Two steps: • Convert from AKM to XML • Convert from XML (2005) to XML (2007)
Links • http://www.microsoft.com/systemcenter/sccp/default.mspx • http://www.microsoft.com/systemcenter/ • http://blogs.infosupport.com/michelk/