Implementing System Center Implementing System Center Operations Manager 2007 at MicrosoftOperations Manager 2007 at Microsoft

Published: February 2007Updated:February 2008

• Microsoft IT wanted Microsoft IT wanted to improve and to improve and streamline its streamline its monitoring services. monitoring services. Decentralization of Decentralization of monitoring services monitoring services increased support increased support costs and caused a costs and caused a significant significant duplication of effort.duplication of effort.

Solution OverviewSolution Overview

Business ChallengeBusiness Challenge SolutionSolution Results/BenefitsResults/Benefits

• Microsoft IT Microsoft IT implemented a implemented a centralized centralized monitoring service monitoring service by deploying System by deploying System Center Operations Center Operations Manager 2007 within Manager 2007 within its corporate its corporate network network environment.environment.

• A more robust A more robust monitoring servicemonitoring service

• Elimination of Elimination of monitoring monitoring fragmentation and fragmentation and better utilization of better utilization of resourcesresources

• Ability to take Ability to take advantage of advantage of previous efforts in previous efforts in creating, tuning, and creating, tuning, and managing managing management packsmanagement packs

Products and TechnologyProducts and Technology

● System Center Operations System Center Operations Manager 2007Manager 2007

● Microsoft Operations Microsoft Operations Manager 2005Manager 2005

● Windows Server 2003Windows Server 2003● SQL Server 2005 SP1SQL Server 2005 SP1● Active DirectoryActive Directory

Challenges of Using Operations Challenges of Using Operations Manager 2005 for MonitoringManager 2005 for Monitoring

● Significant duplication of effort to provide Significant duplication of effort to provide fault monitoringfault monitoring

● Gaps in the service offeringGaps in the service offering● No comprehensive, holistic view of the No comprehensive, holistic view of the

health of the network environmenthealth of the network environment● Dependence on a single expert to manage Dependence on a single expert to manage

each group’s Operations Manager 2005 each group’s Operations Manager 2005 implementationimplementation

Benefits of Using Operations Manager Benefits of Using Operations Manager 2007 for Monitoring2007 for Monitoring

● Centralized monitoring, better resource utilizationCentralized monitoring, better resource utilization● Rapid development of management packsRapid development of management packs● Retention of previous work on management packsRetention of previous work on management packs● Use of health modelsUse of health models● More robust monitoring serviceMore robust monitoring service● Reduction of agent deployment effortsReduction of agent deployment efforts● Efficient collection/storage of security event logsEfficient collection/storage of security event logs● SDK that provides an interface for automation of SDK that provides an interface for automation of

administrative tasksadministrative tasks

Microsoft IT Monitoring SolutionMicrosoft IT Monitoring Solution

● Operations Manager 2007 enabled Microsoft IT to Operations Manager 2007 enabled Microsoft IT to completely rebuild its monitoring infrastructurecompletely rebuild its monitoring infrastructure

● Application has significantly improved features Application has significantly improved features introduced in previous versionsintroduced in previous versions

● Phases for building and deploying the new Phases for building and deploying the new monitoring solution:monitoring solution:

1. Planning the environment1. Planning the environment

2. Designing the infrastructure2. Designing the infrastructure

3. Deploying Operations Manager 20073. Deploying Operations Manager 2007

Planning the Operations Manager Planning the Operations Manager 2007 Environment2007 Environment

● Main objectives for the design of the Main objectives for the design of the environment:environment:● Provide a complete monitoring service offeringProvide a complete monitoring service offering● Provide a centralized and holistic monitoring Provide a centralized and holistic monitoring

platformplatform● Reduce resources devoted to monitoringReduce resources devoted to monitoring

Designing the Infrastructure: Server Designing the Infrastructure: Server RolesRoles

● Operational database serverOperational database server● Root management serverRoot management server● Management serversManagement servers● Gateway serversGateway servers● Audit collection serversAudit collection servers● Data warehouse and reporting serverData warehouse and reporting server

Designing the Infrastructure: Pre-Designing the Infrastructure: Pre-production Environmentproduction Environment

Designing the Infrastructure: Designing the Infrastructure: Production EnvironmentProduction Environment

Designing the Infrastructure: Microsoft Designing the Infrastructure: Microsoft IT Hardware Specs for ServersIT Hardware Specs for ServersServer role Server role Number of servers per unit Number of servers per unit ProcessorProcessor MemoryMemory Operating systemOperating system Disks*Disks*

Operational database serverOperational database server Two per management group—Two per management group—Windows Clustering clusterWindows Clustering cluster

Two dual coreTwo dual core 8 GB8 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bitwith SP1, 64 bit

SANSANWindows Clustering Quorum: 5 GBWindows Clustering Quorum: 5 GBSQL data: 130 GB RAID 10SQL data: 130 GB RAID 10SQL log: 10 GB RAID 5SQL log: 10 GB RAID 5TempDB: 10 GB RAID 5TempDB: 10 GB RAID 5

Root management server Root management server Two per management group—Two per management group—Windows Clustering clusterWindows Clustering cluster

Two dual coreTwo dual core 16 GB16 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bit with SP1, 64 bit

SANSANWindows ClusteringWindows ClusteringRoot management server state Root management server state drive: 5 GB drive: 5 GB

Failover database server Failover database server One per management group One per management group One dual coreOne dual core 8 GB8 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bit with SP1, 64 bit

SANSANSQL data: 130 GB RAID 10SQL data: 130 GB RAID 10SQL log: 10 GB RAID 5SQL log: 10 GB RAID 5TempDB: 10 GB RAID 5TempDB: 10 GB RAID 5

Operations Manager 2007 Operations Manager 2007 Audit Collection databaseAudit Collection database

One per Operations One per Operations Manager 2007 Audit Manager 2007 Audit Collection deploymentCollection deployment

Two dual coreTwo dual core 8 GB8 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bit with SP1, 64 bit

SANSANSQL data: 1 terabyte RAID 10SQL data: 1 terabyte RAID 10SQL log: 50 GB RAID 5SQL log: 50 GB RAID 5TempDBTempDB

Management serverManagement server Two per management groupTwo per management group One dual coreOne dual core 4 GB4 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bit with SP1, 64 bit

Not applicableNot applicable

Management Server and Management Server and Operations Manager 2007 Operations Manager 2007 Audit CollectionAudit Collection

One per Operations One per Operations Manager 2007 Audit Manager 2007 Audit Collection deploymentCollection deployment

One dual core One dual core 4 GB4 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bitwith SP1, 64 bit

Not applicableNot applicable

Data warehouseData warehouse One per the entire deploymentOne per the entire deployment Four dual Four dual corecore

16 GB16 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bitwith SP1, 64 bit

SANSANSQL data: 400 GB RAID 10SQL data: 400 GB RAID 10SQL log: 30 GB RAID 10SQL log: 30 GB RAID 10TempDB: 30 GB RAID 10 TempDB: 30 GB RAID 10

Gateway serverGateway server Two per security-enhanced Two per security-enhanced environment environment

Two dual coreTwo dual core 4 GB4 GB Windows Server 2003 Windows Server 2003 with SP1, 64 bit with SP1, 64 bit

Not applicableNot applicable

Designing the Infrastructure: Designing the Infrastructure: Redundancy and Disaster RecoveryRedundancy and Disaster Recovery

RoleRole Redundancy/high availabilityRedundancy/high availability Disaster recoveryDisaster recovery

Management serverManagement server Approach: Deploy multiple management servers for agent failover. Approach: Deploy multiple management servers for agent failover.

Description: In a management group, if one management server goes Description: In a management group, if one management server goes offline, the agents and gateway systems reporting to it will fail over to offline, the agents and gateway systems reporting to it will fail over to another management server in the management group. In Microsoft IT, another management server in the management group. In Microsoft IT, agent failover behavior is defined in Active Directory, where agents can agent failover behavior is defined in Active Directory, where agents can automatically discover it. automatically discover it.

Approach: Deploy management servers in multiple locations. Approach: Deploy management servers in multiple locations.

Description: If one site goes offline, the agent will fail over to the Description: If one site goes offline, the agent will fail over to the management server in another site, assuming that the site’s failover management server in another site, assuming that the site’s failover configuration allows this. Microsoft IT is considering having management configuration allows this. Microsoft IT is considering having management servers hosted on virtual machines in the failover location, as opposed to servers hosted on virtual machines in the failover location, as opposed to procuring more dedicated hardware. procuring more dedicated hardware.

Root management serverRoot management server Approach: Cluster the root management server. Approach: Cluster the root management server.

Description: By using Windows Clustering, Microsoft IT has deployed Description: By using Windows Clustering, Microsoft IT has deployed the root management server role onto a two-node cluster to allow the the root management server role onto a two-node cluster to allow the underlying servers to go offline without having to take the role itself underlying servers to go offline without having to take the role itself offline for a prolonged amount of time.offline for a prolonged amount of time.

Approach: Promote a remote management server to root management Approach: Promote a remote management server to root management server. server.

Description: If the root manager server cluster becomes unavailable, Description: If the root manager server cluster becomes unavailable, Microsoft IT will promote one of its remaining management servers into the Microsoft IT will promote one of its remaining management servers into the root management server role. Management servers are deployed in remote root management server role. Management servers are deployed in remote locations to account for a site-wide outage. locations to account for a site-wide outage.

Gateway serverGateway server Approach: Deploy multiple gateway servers per location.Approach: Deploy multiple gateway servers per location.

Description: The approach is the same as management servers, with Description: The approach is the same as management servers, with two notable exceptions. First, multiple gateway servers need to be two notable exceptions. First, multiple gateway servers need to be deployed in each distinct network/Active Directory space where the deployed in each distinct network/Active Directory space where the gateway's agents are located. Second, gateway servers need to have gateway's agents are located. Second, gateway servers need to have multiple management servers that they can communicate with to multiple management servers that they can communicate with to ensure that they themselves can fail over if necessary.ensure that they themselves can fail over if necessary.

None: Because the gateway servers are located in the same physical None: Because the gateway servers are located in the same physical segment as the agents, if the location is offline, the agents will be offline as segment as the agents, if the location is offline, the agents will be offline as well.well.

Operational database Operational database serverserver

Approach: Cluster the SQL Server–based server that the Operational Approach: Cluster the SQL Server–based server that the Operational database is hosted on. database is hosted on.

Description: By using Windows Clustering, Microsoft IT has deployed Description: By using Windows Clustering, Microsoft IT has deployed the SQL Server–based server that the Operational database role is the SQL Server–based server that the Operational database role is running on onto a two-node cluster to allow the underlying servers to go running on onto a two-node cluster to allow the underlying servers to go offline without having to take the role itself offline for a prolonged offline without having to take the role itself offline for a prolonged amount of time.amount of time.

Approach: Implement log shipping to a remote SQL Server–based server. Approach: Implement log shipping to a remote SQL Server–based server.

Description: A stand-alone SQL Server–based server has been deployed Description: A stand-alone SQL Server–based server has been deployed in a remote location and log shipping was set up to replicate data from the in a remote location and log shipping was set up to replicate data from the primary Operational database to the failover SQL Server–based server. If a primary Operational database to the failover SQL Server–based server. If a disaster occurs, the management group can be manually pointed to use disaster occurs, the management group can be manually pointed to use the failover database.the failover database.

Operations Manager 2007 Operations Manager 2007 Audit Collection collector Audit Collection collector

None.None. None.None.

Operations Manager 2007 Operations Manager 2007 Audit Collection database Audit Collection database

None.None. None.None.

Data warehouseData warehouse None.None. Approach: Use database backups. Approach: Use database backups.

Description: Scheduled periodic database backups with off-site storage are Description: Scheduled periodic database backups with off-site storage are implemented. If a disaster occurs, the latest backup sequence is restored implemented. If a disaster occurs, the latest backup sequence is restored to a new server.to a new server.

Deploying Operations Manager 2007Deploying Operations Manager 2007

1. Conducting lab validation1. Conducting lab validation

2. Deploying the infrastructure2. Deploying the infrastructure

3. Deploying the data warehouse and reporting servers3. Deploying the data warehouse and reporting servers

4. Deploying management and gateway servers4. Deploying management and gateway servers

5. Deploying Audit Collection components5. Deploying Audit Collection components

6. Running workflows to create necessary objects in Active 6. Running workflows to create necessary objects in Active Directory for agent deploymentDirectory for agent deployment

7. Deploying agents7. Deploying agents

8. Deploying management packs8. Deploying management packs

9. Deploying the UIs9. Deploying the UIs

10. Deploying additional integration10. Deploying additional integration

Conducting Lab ValidationConducting Lab Validation

● Goals of lab validation:Goals of lab validation:● Perform rudimentary tests against the Perform rudimentary tests against the

applicationapplication● Verify that the server and client components Verify that the server and client components

would not adversely consume resourceswould not adversely consume resources● Verify that the build was suitable for production Verify that the build was suitable for production

deployment by observing resource utilizationdeployment by observing resource utilization● Deploy basic management packs and confirm Deploy basic management packs and confirm

no adverse effects on resource utilizationno adverse effects on resource utilization

Deploying the InfrastructureDeploying the Infrastructure

● Procure hardwareProcure hardware● Implement necessary ACLs and firewall policiesImplement necessary ACLs and firewall policies● Deploy Operational database and root Deploy Operational database and root

management server cluster with three management server cluster with three management groups:management groups:● Quorum resource groupQuorum resource group● SQL Server resource groupSQL Server resource group● Root management server resource groupRoot management server resource group

Deploying the Data Warehouse and Deploying the Data Warehouse and Reporting ServersReporting Servers

● To prepare for warehouse installation, Microsoft To prepare for warehouse installation, Microsoft IT: IT: ● Installed and configured prerequisite softwareInstalled and configured prerequisite software● Determined the service account to be used for Determined the service account to be used for

the Write Action and Data Reader accountsthe Write Action and Data Reader accounts● Configured service account securityConfigured service account security● Obtained information for the installationObtained information for the installation● Set up ACLsSet up ACLs● Ran the prerequisite checkerRan the prerequisite checker

Deploying Management and Gateway Deploying Management and Gateway ServersServers

● Microsoft IT:Microsoft IT:● Installed two management servers per Installed two management servers per

management group and then set up gateway management group and then set up gateway serversservers

● Requested one certificate for each server and Requested one certificate for each server and imported them into the local certificate storeimported them into the local certificate store

● Followed setup steps in deployment guidesFollowed setup steps in deployment guides● Deployed two gateway servers per network or Deployed two gateway servers per network or

Active Directory spaceActive Directory space

Deploying Audit Collection Deploying Audit Collection ComponentsComponents● Operations Manager 2007 Audit Collection Operations Manager 2007 Audit Collection

provides security-enhanced, real-time export of provides security-enhanced, real-time export of security eventssecurity events

● Server roles affect how many servers can be Server roles affect how many servers can be monitored on a single collectormonitored on a single collector

● Current scope of this deployment of Audit Current scope of this deployment of Audit Collection is 135 domain controllers and 3,500 Collection is 135 domain controllers and 3,500 member serversmember servers

● Event filtering method affects storage Event filtering method affects storage requirements and data retentionrequirements and data retention

Deploying Audit Collection Deploying Audit Collection ComponentsComponents

● Data retention goal is 30 daysData retention goal is 30 days● Deployment method for Audit Collection is SMSDeployment method for Audit Collection is SMS● Microsoft IT had to consider its audit policies and Microsoft IT had to consider its audit policies and

plan for scalabilityplan for scalability● Audit Collection includes performance monitors Audit Collection includes performance monitors

and AdtAdmin.exe command-line tooland AdtAdmin.exe command-line tool● DNS service records point agents to collectorsDNS service records point agents to collectors

Running Workflows to Create Running Workflows to Create Necessary Objects in Active DirectoryNecessary Objects in Active Directory

● To provision the necessary Active Directory To provision the necessary Active Directory containers, Microsoft IT:containers, Microsoft IT:● Gathered a list of servers that needed agentsGathered a list of servers that needed agents● Gathered a list of domains where agents would Gathered a list of domains where agents would

residereside● Mapped domain names to management groupsMapped domain names to management groups● Ran MOMAdAdmin.exe to provision containersRan MOMAdAdmin.exe to provision containers● Created agent assignment rules and executed Created agent assignment rules and executed

workflowsworkflows

Deploying AgentsDeploying Agents

● Earlier infrastructure relied on Operations Earlier infrastructure relied on Operations Manger 2005 for push installationsManger 2005 for push installations

● Microsoft IT now deploys agents through Microsoft IT now deploys agents through SMS advertisementSMS advertisement

● Package was created to contain agent Package was created to contain agent installation filesinstallation files

● Systems rights let agents enter Systems rights let agents enter management groups via Active Directorymanagement groups via Active Directory

Deploying Management PacksDeploying Management Packs

● Microsoft IT took action based on Microsoft IT took action based on categorization of management packs:categorization of management packs:● Identify and convert existing management Identify and convert existing management

packspacks● Identify and disable existing management Identify and disable existing management

packs not to be deployedpacks not to be deployed● Deploy new Operations Manager 2007 Deploy new Operations Manager 2007

management packsmanagement packs

Deploying the User InterfacesDeploying the User Interfaces

● Customers of the monitoring service can use the Customers of the monitoring service can use the operations console to work with operational dataoperations console to work with operational data

● E-mail notifications can be generated in response E-mail notifications can be generated in response to alertsto alerts

● Web console contains trimmed-down functionality Web console contains trimmed-down functionality as an alternative to the operations consoleas an alternative to the operations console

● Connector converts alerts to trouble ticketsConnector converts alerts to trouble tickets

Deploying Additional IntegrationDeploying Additional Integration

● Microsoft partners supply connectors that Microsoft partners supply connectors that integrate their applications with Operations integrate their applications with Operations ManagerManager

● Microsoft IT uses EMC Smarts to monitor network Microsoft IT uses EMC Smarts to monitor network devicesdevices

● Microsoft IT wrote a custom connector to integrate Microsoft IT wrote a custom connector to integrate Operations Manager with trouble ticketingOperations Manager with trouble ticketing

● Users of the operations console can use ticketing Users of the operations console can use ticketing functionality via customer resolution statesfunctionality via customer resolution states

Deploying Additional IntegrationDeploying Additional Integration

● Microsoft IT used the SDK to automate Microsoft IT used the SDK to automate administrative tasksadministrative tasks

● Custom management pack uses the SDK to Custom management pack uses the SDK to extend the base system class in Operations extend the base system class in Operations Manager 2007Manager 2007

● Custom management pack placed a service Custom management pack placed a service offering attribute on every new base system offering attribute on every new base system classclass

Best PracticesBest Practices

● Gather feedback from end users in advanceGather feedback from end users in advance● Consider new server roles and featuresConsider new server roles and features● Consider the number of systems to be monitored Consider the number of systems to be monitored

and the number of rules that will be runand the number of rules that will be run● Consider the performance capabilities of the Consider the performance capabilities of the

servers that will host the Operational databaseservers that will host the Operational database● Use the configuration advice in Help files and in Use the configuration advice in Help files and in

System Center Capacity PlannerSystem Center Capacity Planner

Best PracticesBest Practices

● In a migration from Operations Manager 2005:In a migration from Operations Manager 2005:● Evaluate which management packs can be carried Evaluate which management packs can be carried

forwardforward● Run the two infrastructures in tandem during the Run the two infrastructures in tandem during the

transitiontransition● Deploy management servers and gateway servers in Deploy management servers and gateway servers in

pairspairs● Use SMS to distribute agentsUse SMS to distribute agents● Use Active Directory integrationUse Active Directory integration● Deploy management packs in batchesDeploy management packs in batches

ConclusionConclusion

● IT teams and product groups at Microsoft work IT teams and product groups at Microsoft work together to develop viable enterprise technologytogether to develop viable enterprise technology

● Deploying Operations Manager 2007 enabled Deploying Operations Manager 2007 enabled Microsoft IT to:Microsoft IT to:● Improve its service offerings and give feedbackImprove its service offerings and give feedback● Provide end-to-end service management in a Provide end-to-end service management in a

scalable, centralized monitoring infrastructurescalable, centralized monitoring infrastructure● Streamline how it identifies and resolves issuesStreamline how it identifies and resolves issues● Take advantage of work invested in deploying Take advantage of work invested in deploying

previous monitoring solutionsprevious monitoring solutions

For More InformationFor More Information

● Operations Manager 2007 product pages: Operations Manager 2007 product pages: http://www.microsoft.com/systemcenter/opsmgr/default.mspx

● Server roles in Operations Manager 2007: Server roles in Operations Manager 2007: http://www.microsoft.com/opsmgr

● Planning and deploying a monitoring Planning and deploying a monitoring infrastructure: infrastructure: http://www.microsoft.com/systemcenter/sccp/default.mspx

● Performance and maintenance implications of log Performance and maintenance implications of log shipping: shipping: http://support.microsoft.com/kb/314515

For More InformationFor More Information

● Additional content on Microsoft IT Additional content on Microsoft IT deployments and best practices can be deployments and best practices can be found on found on http://www.microsoft.com● Microsoft IT Showcase WebcastsMicrosoft IT Showcase Webcasts

http://www.microsoft.com/howmicrosoftdoesitwhttp://www.microsoft.com/howmicrosoftdoesitwebcastsebcasts

● Microsoft TechNetMicrosoft TechNet http://www.microsoft.com/technet/itshowcasehttp://www.microsoft.com/technet/itshowcase

This document is provided for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

© 2008 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. Microsoft, Active Directory, SQL Server, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.