System Center Operations Manager 2007 R2 Guide For Healthcare Organizations PDF

System Center Operations Manager 2007 R2
Design, Deployment and Operations Guide
Friday, 26 February 2010

Version 1.0.0.0 Baseline
Prepared by
Microsoft
Prepared by Microsoft
Copyright
This document and/or software (this Content) has been created in partnership with the National Health Service (NHS) in England. Intellectual Property
Rights to this Content are jointly owned by Microsoft and the NHS in England, although both Microsoft and the NHS are entitled to independently exercise
their rights of ownership. Microsoft acknowledges the contribution of the NHS in England through their Common User Interface programme to this Content.
Readers are referred to www.cui.nhs.uk for further information on the NHS CUI Programme.
All trademarks are the property of their respective companies. Microsoft and Windows are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Microsoft Corporation 2010. All rights reserved.
Disclaimer
At the time of writing this document, Web sites are referenced using active hyperlinks to the correct Web page. Due to the dynamic nature of Web sites, in
time, these links may become invalid. Microsoft is not responsible for the content of external Internet sites.
Page ii
System Center Operations Manager 2007 R2 Design, Deployment and Operations Guide
Prepared by Microsoft, Version 1.0.0.0
Last modified on 26 February 2010
The following diagram illustrates the different sections of this document:
Figure 1: MSF Process Model Phases and Document Structure
Page 11
Step Description
Screenshot
4.
In the Welcome to the Microsoft

SQL Server Installation Wizard
screen, click Next.
5.
From System Configuration Check

screen, a check on the SQL Server
2005 prerequisites is automatically
performed.
Note
If any prerequisites are not installed,
these will show as Failed. You
should resolve these and re-run the
operation before installation can
continue.
Click Next.
Page 25
Step Description
14.
Screenshot
In the Ready to Install screen, verify

the components listed for installation
are correct.
Click Install.
Table 4: Installing SQL Server 2005
Page 30
Step Description
12.
Screenshot
Select the Collation tab.

Ensure that the collation for
Database Engine is set to
Latin1_General_CI_AS.
Click Next.
13.
In the Database Engine

Configuration screen, select
Windows authentication
mode.
Click the Add Current User
or the Add... button to grant at
least one user (or group) SQL
Server Administrator access to
the Database Engine.
Click Next.
14.
Select the Data Directories

tab. Enter the desired default
locations for:
Data root directory
User database directory
User database log directory
Temp DB directory
Temp DB log directory
Backup directory
Click Next.
Page 35
Step Description
6.
Screenshot
In the Prerequisites Check

screen, if any of the prerequisite
checks failed, these will need to
be resolved before the
installation can continue. Click
View Log to display details of
any failed checks.
Click Next.
7.
In the Management Group

Configuration screen, enter the
Management Group name.
Click Next.
8.
In the SQL Server Database

Instance screen, select the
SQL Server database instance
from the drop-down list.
Click Next.
Page 40
Step Description
Screenshot
2.
In the Welcome to the System

Center Operations Manager
2007 Setup Wizard screen,
click Next.
3.
In the End-User License

Agreement (EULA) screen,
read the terms of the license
agreement and click I accept
the terms in the license
agreement.
Click Next.
4.
In the Product Registration

screen, enter the User Name
and Organization.
Click Next.
Page 49
Step Description
3.
Screenshot

agreement.
Click Next.
4.

screen, enter your User Name
and Organization.
Click Next.
5.
In the Custom Setup screen,

ensure that only the
Management Server
component is selected for
installation.
Click the Browse button and
select a location for the
installation of Operations
Manager 2007.
Click Next.
Page 54
Step Description
6.
Screenshot

View Log to view details of any
failed checks.
Click Next.
7.
In the Customer Experience

Improvement Program screen,
select I dont want to join the
program at this time.
Click Next.
8.
In the Ready to Install the

Program screen, click Install.
Table 10: Installing the Operations Console

Page 59
Step
Description
Screenshot
2.
In the Welcome to Operations

Manager 2007 R2 Reporting
Setup screen, click Next.
3.

Agreement screen, select I
accept the terms in the
license agreement.
Click Next.
4.

and Organization.
Click Next.
Page 64
Step
6.
Description
Screenshot

any failed checks.
Click Next.
7.
In the Connect to Root

Management Server screen,
enter the name of the Root
Management Server.
Click Next.
8.
In the Connect to the

Operations Manager Data
Warehouse screen, enter the
name of the server that the
Data Warehouse was installed
to and the SQL instance for the
SQL Server database
instance.
Click Next.
Page 69
Step Description
Screenshot
3.
In the Destination Folder

screen, leave the default
installation folder as
C:\Program Files\System
2007, and click Next.
4.

Specify Management Group
information.
Click Next.
5.

Configuration screen enter the
Management Group Name and
Management Server.
Click Next.
Page 74
6.5
Reporting
Reporting is an essential part of the Operations Manager 2007 solution. It is important to ensure
that all aspects of Reporting are working as expected, prior to deploying Operations Manager in a
live network environment. The following reporting components should be thoroughly tested:
The Reporting section is available in the Operations Console
Reports can be launched from the Operations Console
Subscribing to reports
Graphs are displayed correctly
Page 79
Step Description
Screenshot
3.
On the Error Reporting tab,

select Dont generate error
reports.
4.
On the Error Transmission

tab, leave the boxes as
unchecked.
Table 18: Specifying Settings for the Windows Customer Experience Improvement Program
Page 88
OPERATE
During the Operate phase, solution components are proactively managed as an end-to-end IT
Service to ensure the service provides the required levels of solution functionality, reliability,
availability, supportability and manageability. Successfully bringing a well-designed service into a
production environment takes efficient planning to balance speed, cost and safety, while ensuring
minimum disruption to operations and supporting the 'business as usual' delivery of the
organisation's IT requirements.
Figure 13 acts as a high-level checklist, illustrating the critical components for which an IT
Professional is responsible for maintaining in a managed and operational Operations Manager
2007 deployment:
Figure 13: Sequence for Operating System Center Operations Manager 2007
8.1
Managing Management Packs
Management Packs contain all of the knowledge that is used for monitoring in Operations Manager
2007. In many cases, the rules and monitors defined within vendor-supplied Management Packs
can be left to run with their default settings. There are, however, cases where some configuration is
required, and this is usually achieved by creating an override for an existing rule or monitor. Most
vendor-supplied Management Packs are sealed, which means they cannot be altered. In order to
save an override, an unsealed management pack needs to exist prior to setting up the override.
By default, overrides and other customisations are saved to the Default Management Pack (an
unsealed Management Pack created during installation). However, as a best practice, separate
unsealed Management Packs should be created for each sealed Management Pack that requires
changes to be made.
Any customisations that are made to an unsealed Management Pack introduce a dependency
relationship with the sealed Management Pack. As a result, if the sealed Management Pack ever
needs to be deleted, the unsealed Management Pack with customisations must also be deleted.
Page 93
APPENDIX B
DOCUMENT INFORMATION
PART I TERMS AND ABBREVIATIONS

Abbreviation
Definition
ACS
Audit collection Service
CUI
Common User Interface
DB
Operations Database
DNS
Domain Name System
DS
Domain Services
DW
Reporting Data Warehouse
EULA
End-User License Agreement
FQDN
Fully Qualified Domain Name
IIS
Internet Information Services
IM&T
Information Management & Technology
MDAC
Microsoft Data Access Components
ML
Management License
MS
Management Server
MSXML
Microsoft XML Core Services
NAT
Network Address Translation
OVO
OpenView Operations
RMS
Root Management Server
RS
Reporting Server
SIP
Session Initiation Protocol
SMB
Server Message Block
SMS
Short Message Service
SMTP
Simple Mail Transfer Protocol
SP
Service Pack
SPN
Service Principal Name
WS
Web Services
XML
Extensible Markup Language
Table 21: Terms and Abbreviations
Page 100
PLAN
The Plan phase is where the bulk of the implementation planning is completed. During this phase
the areas for further analysis are identified and a design process commences.
Figure 2 acts as a high-level checklist illustrating the sequence of events that the IT Manager and
IT Architect need to determine when planning for Operations Manager 2007 within a healthcare
organisation:
Figure 2: Sequence for Planning System Center Operations Manager 2007
4.1
Planning Management Groups
This guidance focuses on two different deployment scenarios:

Deploying a single Management Group on a single server
Deploying a single Management Group distributed across multiple servers
The principle factor that will affect the choice of deployment scenario is the number of resources
that need to be monitored. The location of the resources to be monitored is not critical, as the best
practice for Operations Manager 2007 is keeping all of the server roles, except for the Gateway
Server, co-located.
Page 13
Included within the hardware recommendations is information about disk partitioning. It is best
practice to split applications and data across multiple partitions, to improve performance and
resilience. With regard to the disk recommendations covered in the tables below, the disk partitions
are described as follows:
System The operating system should be installed to this partition
Application Any additional applications, such as Operations Manager 2007 or SQL
Server 2008, should be installed to this partition
Database The database files (.MDB) should be located on this partition
Database Logs The database log files (.LDB) should be located on this partition
4.1.1
Deploying a Single Management Group on a Single Server
In this scenario, all of the Operations Manager 2007 R2 server roles are installed on a single server.
These roles are:
Root Management Server (RMS)
Operations Database (DB)
Reporting Server (RS)
Reporting Data Warehouse (DW)
A single server would be suitable for a healthcare organisation that is planning to monitor up to 250
servers, but will not provide any redundancy in the event of hardware failure. The base hardware
recommendation for this scenario is shown in Table 2:
Number of
Server Roles
Monitored Servers
Architecture Processor
Memory
Disk
Up to 250 Windows
servers
x64
8GB RAM
4 Disk Partitions
RMS, DB, RS, DW
Quad Processor
System (Raid 1)
Application (Raid 1)
Database (Raid 1+0)
Database Logs (Raid 1)
Table 2: Server Hardware for a Single Server Scenario
4.1.2
Deploying a Single Management Group across Multiple Servers
For healthcare organisations with monitoring requirements for more than 250 servers, the
Operations Manager 2007 server roles will need to be split out across multiple servers.
Number of
Server Roles
Monitored Servers
Memory
Disk
250-500 Windows
Servers
x64
4GB
2 Disk Partitions:
RMS
Dual Processor
System (Raid 1)
DB, RS, DW
x64
Dual Processor
4GB
4 Disk Partitions:
System (Raid 1)
Database (Raid 1+0)
Page 14
Number of
Server Roles
Monitored Servers
Memory
Disk
500-750 Windows
Servers
x64
8GB
2 Disk Partitions:
RMS
Dual Processor
System (Raid 1)
Management
Server (MS)
x64
Dual Processor
4GB
2 Disk Partitions:
System (Raid 1)
DB
x64
Dual Processor
4GB
4 Disk Partitions:
System (Raid 1)
Database (Raid 1+0)
RS, DW
x64
Dual Processor
4GB
4 Disk Partitions:
System (Raid
1)Application (Raid
1)Database (Raid
1+0)Database Logs
(Raid 1)
750-1000 Windows
Servers
RMS
x64
Dual Processor
8GB
2 Disk Partitions:
System (Raid
1)Application (Raid 1)
MS
x64
Quad Processor
8GB
2 Disk Partitions:
System (Raid
DB
x64
Dual Processor
8GB
4 Disk Partitions:
System (Raid
1)Application (Raid
1)Database (Raid
1+0)Database Logs
(Raid 1)
RS
x64
Dual Processor
4GB
2 Disk Partitions:
System (Raid
DW
x64
Dual Processor
8GB
4 Disk Partitions:
System (Raid
1)Application (Raid
1)Database (Raid
1+0)Database Logs
(Raid 1)
Table 3: Server Hardware for Multiple Server Scenarios
This guidance assumes that there are no healthcare organisations that manage server estates
exceeding 1,000 servers. If further guidance on server sizing is required for an estate that exceeds
1,000 servers, please refer to the Operations Manager 2007 R2 Design Guide {R2}.
Page 15
4.2
Planning Database Selection and Sizing
The R2 version of Operations Manager 2007 is supported on both SQL Server 2005 and SQL
Server 2008. The Standard Edition of SQL Server provides all of the functionality required for an
13
Operations Manager solution, as described in the scope of this document .
The amount of disk space required for the Operations Database and Reporting Data Warehouse
will depend on the number of agents deployed, management packs implemented, and the data
retention periods specified. The Operations Manager 2007 Product Group has provided a
14
Database Size Calculator to help estimate the amount of disk space required.
4.3
Planning Availability
In a healthcare organisation where constant monitoring is required, the availability of an Operations

Manager 2007 solution can be improved by implementing redundancy in the various server roles.
The following redundancy options can be implemented:
Operations Database The database can be installed on Windows Servers with Failover
Clustering enabled. The cluster nodes will provide redundancy for the SQL Server
application. To provide a geographically redundant solution, SQL Log Shipping can be
enabled to copy the database to a server at another location
Root Management Server The RMS is a single point of failure within a Management
Group as it runs the SDK service which provides access to the Operations Database and
the Config service which manages agent monitoring. If the Management Group contains
another Management Server, it is possible to promote it to the RMS role, but this requires
manual intervention. To ensure maximum availability the RMS can be installed on a twonode failover cluster
Management Servers If a Management Server fails, the agents and Gateway Servers
reporting to it can failover automatically to another Management Server. Having more than
one Management Server provides a solution for ensuring agents maintain contact, as well
as providing potential redundancy for the RMS role
Gateway Server If a Gateway Server fails, the agents reporting to it can failover
automatically to another Gateway Server or Management Server (assuming communication
between the agents and the redundant servers is possible)
4.4
Server Role Best Practice
This section provides information to keep in mind when determining the hardware to provide for an
Operations Manager 2007 solution. The following universal considerations should be kept in mind
when choosing hardware and locations for the various server roles:
The RMS provides console connectivity to the Operations Database and Reporting Data
Warehouse. The RMS and other Management Servers insert data regularly into the
Operations Database and Reporting Data Warehouse. The Operations Database
synchronises updated alert data with the Reporting Data Warehouse. All of these server
roles should be physically co-located, that is, with network connectivity on the same switch,
as this would improve performance and reduce impact on other network segments
Where possible, deploy all server roles on the x64 platform to facilitate an easier upgrade
path beyond 4GB RAM
13
The Enterprise Edition of SQL Server is preferred for an ACS database, as this supports continued data insertion during
maintenance periods.
14
Microsoft TechNet OPSMGR 2007 Database and Data Warehouse Size Calculator {R11 }:
http://blogs.technet.com/momteam/archive/2007/10/15/opsmgr-2007-database-and-data-warehouse-size-calculator.aspx
Page 16
4.4.1
The RMS calculates the required configuration for each monitored agent and keeps a copy of this
configuration in RAM. It also provides connectivity between the Operations Consoles and the
Operations Database and Reporting Data Warehouse, and each of these connections uses
additional RAM. The following considerations should be kept in mind when determining the RMS
hardware requirements:
Each additional agent deployed will require additional RAM on the RMS to calculate and
store its configuration
Each console connection will require additional RAM
Each agent connection sending data, which needs to be submitted to the Operations
Database or Reporting Data Warehouse, will require additional RAM. Where possible, all
agent communications should be directed to other Management Servers to eliminate this
additional requirement from the RMS
As the RMS role is very RAM intensive, it is recommended that this role is not virtualised
4.4.2
Operations Database and Data Warehouse
The Operations Database stores the monitoring data and resulting alerts, as well as the agent
configurations and server settings. The Reporting Data Warehouse archives monitoring and
alerting data in order to facilitate historical reporting. Data is submitted to both databases from all of
the Management Servers, the data is queried via the RMS, and the Operations Database also
synchronises alert updates with the Reporting Data Warehouse. The following points should be
considered when determining the Operations Database and Reporting Data Warehouse hardware
requirements:
The primary function of this server is data access for which disk performance is most
important. The database file should have a dedicated volume using RAID 1+0 for optimal
performance
The database log file should have a dedicated volume using RAID 1 for optimal
performance
A write-caching disk controller can help improve disk performance, but should only be used
with a battery backup system in place to prevent data loss
4.4.3
Management Server
Management Servers act as a hub between monitored agents and the Operations Database and
Reporting Data Warehouse. The following points should be considered when determining the
Management Server hardware requirements:
The primary activity is data insertion, which requires CPU as its most important resource
Additional agents and management packs will increase the RAM requirements, as the data
insertion queue is maintained in memory
Having at least one Management Server, other than the RMS, is recommended for
availability and reducing load on the RMS
Management Servers should only be deployed in proximity to the databases, as
Management Servers separated from the databases by a WAN will increase the volume of
network traffic (versus agent traffic) and likely introduce SQL deadlocking issues during
data insertion. Gateway Servers should be used if there is a requirement to consolidate
agent traffic across the WAN
Page 17
While there is no hard limit to the number of agents that can be supported by a
Management Server, it is recommended not to exceed 3,000 agents per Management
Server. 2,000 agents or less per Management Server will maintain optimal performance
As the Management Server is not as disk or RAM-intensive as other roles, it is suitable for
virtualisation
4.4.4
Gateway Server
Gateway Servers serve two roles: facilitating certificate authenticated communication with agents
outside trust boundaries, and consolidating agent traffic across a WAN. The Gateway Server
communicates with agents and Management Servers. The following points should be considered
when determining Gateway Server hardware requirements:
If WAN traffic is an issue, use a Gateway Server to manage it. Doing so will reduce the
WAN traffic to a single connection, rather than multiple connections from agents. Also, the
Gateway Server will compress all its communications with the Management Servers
While there is no hard limit to the number of agents that can be supported by a Gateway
Server, it is recommended that 1,500 agents per Gateway Server is not exceeded. 1,000
agents or less per Management Server will maintain optimal performance
In a healthcare organisation with a large number of Gateway Servers or gateway connected
agents, a dedicated Management Server (with no agents of its own) should be provided
The primary activity is data insertion which has CPU capacity as its most important
resource
As the Management Server is not as disk or RAM-intensive as other roles, it is suitable for
virtualisation
4.5
Agent Deployment
In Operations Manager 2007, agents can be deployed via the Operations Console using a
discovery-based mechanism, or they can be manually installed. The installation process can be
automated to allow distribution through a software deployment mechanism, such as Microsoft
System Center Configuration Manager or Group Policy Software Installation. The agent can also be
pre-installed as part of a server build image.
4.5.1
Discovery-Based Agent Installation
Discovery-based installation is available through the Discovery Wizard in the Administration Node
of the Operations Console. The Discovery Wizard can search for servers based upon specified
criteria, and then push the agent to the servers it discovers.
To use Discovery-based installation an account with administrator rights on the targeted servers is
required, in order to successfully complete the push installation. The account credentials can be
specified during the discovery process, and will be discarded after the installation. During the
installation process the credentials are encrypted before being passed to the agent for installation.
A Management Server uses the Server Message Block (SMB) port (TCP/UDP 445) and the RPC
port (TCP 135) to deliver the files needed for agent installation and for updating agent settings after
installation. If these outgoing ports are blocked on the Management Server, the incoming ports are
blocked on any of the targeted servers, or if any of the target servers and the Management Server
is separated by a firewall, discovery-based installation will fail.
Agents deployed using discovery-based installation are not able to use Active Directory Integration.
Page 18
4.5.2
Manual Agent Installation
Manual installation of agents is available where discovery-based installation is unsuitable. This

might include the following scenarios:
An existing software deployment mechanism exists
The agent is located outside the trust boundaries of the Management Group
Active Directory Integration will be used to assign agents to a specific Management Server
or Management Group
Page 19
DEVELOP
During the Develop phase the solution components are built based on the planning and designs
created in the earlier phases. Further refinement of these components will continue into the
Stabilisation phase.
Figure 3 acts as a high-level checklist, illustrating the tasks that an IT Professional needs to
perform when developing Operations Manager 2007 within a healthcare organisation:
Figure 3: Sequence for Developing System Center Operations Manager 2007
Page 20
5.1
Software Prerequisites
The Operations Manager 2007 server roles can be installed on machines with the following
operating systems:
Windows Server 2003 SP1 (or later)
Windows Server 2003 R2 SP1 (or later)
Windows Server 2008 SP1 (or later)
Windows Server 2008 R2
Each of the server roles have specific prerequisites which are detailed below:
RMS/Management Server:
Microsoft .NET Framework v2.0
Microsoft Core XML Services (MSXML) 6.0
Operations Database:
SQL Server 2005 SP1 (or later) or SQL Server 2008 SP1
Microsoft Data Access Components (MDAC) v2.80.1022.0 or higher
Reporting Server:
Microsoft .NET Framework 2.0
Microsoft SQL Server 2005 Reporting Services SP1 (or later) or SQL Server 2008
Reporting Services SP1
Reporting Data Warehouse:
Microsoft SQL Server 2005 SP1 (or later) or SQL Server 2008 SP1
MDAC v2.80.1022.0 or higher
Operations Console:
Windows PowerShell
Web Console:
Microsoft Internet Information Services (IIS) 6.0, IIS 7.0 or IIS 7.5
ASP.NET 2.0 AJAX Extensions 1.0
The following software prerequisites need to be in place on all servers before deploying the
Operations Manager 2007 agent:
Windows 2000 Server SP4, Windows Server 2003 SP1 (or later), or Windows Server 2008
SP1 (or later)
MSXML 6.0
15
15
Microsoft Core XML Services 6.0 requires Windows Installer 3.1

Page 21
5.2
Licensing
The following options exist for licensing the Operations Manager 2007 server components:
Operations Manager Server 2007 R2
Operations Manager Server 2007 R2 with SQL Server Technology
The following options exist for licensing the Operations Manager 2007 agent:
Enterprise Server Management License (ML) Required for full application and server
management, for example, Windows Server 2008 Active Directory and Microsoft Exchange
Server 2007.
Standard Server ML Used for server operating system and basic workload management.
This license is only suitable for dedicated file and print servers, with no other applications
being monitored on them.
Client ML Used for desktop operating system and application management. This license
is only suitable for computers running a desktop operating system.
System Center Server Management Suites Enterprise This license is available to
Volume Licensing customers. The suite includes the Enterprise Server ML for:
System Center Configuration Manager 2007 R2
System Center Virtual Machine Manager 2008 R2
System Center Data Protection Manager 2007
The license is per physical server and covers agents installed on up to four virtually hosted
operating systems.
System Center Server Management Suites Datacenter This license is available to
Volume Licensing customers. The suite includes the Enterprise Server ML for:
System Center Configuration Manager 2007 R2
System Center Virtual Machine Manager 2008 R2
System Center Data Protection Manager 2007
The license is per processor (with a minimum of two processors), and covers unlimited
agents installed on virtually hosted operating systems.
5.3
Installing Internet Information Services
Operations Manager 2007 requires IIS to be installed on the server that will host the Operations
Manager 2007 Web Console. SQL Server 2005 Reporting Services also requires IIS to be installed.
Page 22
To install IIS 6.0 on Windows Server 2003:

1. Click Start, open the Control Panel, and double-click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. In the Components list, select Application Server.
4. Click Details and ensure ASP.NET is selected.
5. Click OK.
6. Click Next.
7. Follow the instructions on the screen.
To install IIS 7.0 on Windows Server 2008 or IIS 7.5 on Windows Server 2008 R2:
1. Click Start, open the Control Panel, select Administrative Tools, and then Server
Manager.
2. In Server Manager, select Roles in the navigation pane.
3. Click Add Roles in the main pane.
4. In the Add Roles wizard, select Web Server (IIS).
5. Click Next.
6. On the Role Services page:
Expand Common HTTP Features, and select the following:

Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
Expand Application Development, and select ASP.NET. When prompted to add

required role services, click OK.
Expand Security, and select Windows Authentication.
Expand Management Tools, expand IIS 6 Management Capability, and select the
following:
IIS Metabase Compatibility
IIS 6 WMI Compatibility
IIS 6 Scripting Tools
IIS 6 Management Console
7. Click Next.
8. Click Install.
5.4
5.4.1
Installing SQL Server

Installing SQL Server 2005
Follow the steps provided in Table 4 below to install SQL Server 2005.
Page 23
Step Description
1.
Screenshot
Execute Default.hta from the folder

that contains the source files for SQL
Server 2005. The SQL Server 2005
screen displays.
Click Server components, tools,
Books Online, and samples.
2.
In the End User License

Agreement screen, read the terms
of the license agreement and select I
accept the licensing terms and
conditions.
Click Next.
3.
In the Installing Prerequisites

screen, click Install.
Once the installation has completed
successfully, click Next.
Page 24
Step Description
Screenshot
4.
In the Welcome to the Microsoft

SQL Server Installation Wizard
screen, click Next.
5.
From System Configuration Check

screen, a check on the SQL Server
2005 prerequisites is automatically
performed.
Note
If any prerequisites are not installed,
these will show as Failed. You
should resolve these and re-run the
operation before installation can
continue.
Click Next.
Page 25
Step Description
6.
Screenshot
In the Registration Information

screen, enter the Name and
Company.
Click Next.
7.
In the Components to Install

screen, select the following options:
SQL Server Database Services
Reporting Services
Workstation Components,
Books Online and development
tools
Click Advanced and select a
location for the installation of SQL
Server 2005.
Click Next.
Page 26
Step Description
8.
Screenshot
In the Instance Name screen, select

Named instance and enter a name
for the SQL Server 2005 instance.
Click Next.
9. In the Service Account screen,

select Customize for each service
account.
For each service, select Use a
domain user account and enter the
Username, Password and Domain.
Select the following options in the
Start services at the end of setup
panel:
SQL Server
SQL Server Agent
Reporting Services
Click Next.
Page 27
Step Description
Screenshot
10. In the Authentication Mode screen,

select Windows Authentication
Mode.
Click Next.
11. In the Collation Settings screen,

select Collation designator and
sort order.
Select Latin1_General from the
drop-down list provided.
Select Accent sensitive.
Click Next.
Page 28
Step Description
12.
Screenshot
In the Report Server Installation

Options screen, select the Install
the default configuration option.
Click Next.
13.
In the Error and Usage Report

Settings screen, select any
appropriate options and click Next.
Page 29
Step Description
14.
Screenshot
In the Ready to Install screen, verify

the components listed for installation
are correct.
Click Install.
Page 30
5.4.2
Installing SQL Server 2008
Follow the steps provided in Table 5 below to install SQL Server 2008.
Step Description
1.
Screenshot
Execute Setup.exe from the

folder that contains the
source files for SQL Server
2008. The SQL Server
Installation Center screen is
displayed.
Click Installation in the left
pane.
2.
Click New SQL Server

stand-alone installation or
add features to an existing
installation in the right pane.
Page 31
Step Description
3.
Screenshot
From the Setup Support

Rules screen, a check on the
SQL Server Setup support
files is automatically
performed.
Note
If any problems are
identified that may occur
during the installation of
the support files, these
will show as Failed and
should be resolved, and
the operation re-run,
before installation can
continue.
Click OK.
4.
In the Product Key screen,

select Enter the product key
and enter the product key if it
is not already displayed.
Click Next.
5.
In the License Terms, read

the terms of the license
the license terms.
Click Next.
Page 32
Step Description
Screenshot
6.
In the Setup Support Files

screen, click Install.
7.
In the Setup Support Rules

screen, a check on the SQL
Server Setup support files is
automatically performed.
Note
If any problems are
identified that may occur
during the installation of
the support files, these
will show as Failed and
should be resolved, and
the operation re-run,
before installation can
continue.
Click Next.
8.
In the Feature Selection

screen, select the following:
Database Engine Services
Reporting Services
Client Tools Connectivity
Management Tools - Basic
Management Tools Complete
Enter an install location in the
Shared feature directory box.
Click Next.
Page 33
Step Description
9.
Screenshot
In the Instance
Configuration screen, enter
the Named Instance.
Click Next.
10.
In the Disk Space

Requirements screen, click
Next.
11.
In the Server Configuration

screen, enter the Account
Name and the Password, and
select Automatic from the
Startup Type drop-down list
for each service listed. It is
recommended to use domainbased user accounts for SQL
Server services.
Click Next.
Page 34
Step Description
12.
Screenshot
Select the Collation tab.

Ensure that the collation for
Database Engine is set to
Latin1_General_CI_AS.
Click Next.
13.
In the Database Engine

Windows authentication
mode.
Click the Add Current User
or the Add... button to grant at
least one user (or group) SQL
Server Administrator access to
the Database Engine.
Click Next.
14.
Select the Data Directories

tab. Enter the desired default
locations for:
Data root directory
User database directory
User database log directory
Temp DB directory
Temp DB log directory
Backup directory
Click Next.
Page 35
Step Description
15.
Screenshot
Select the FILESTREAM tab.

Ensure that Enable
FILESTREAM for TransactSQL access is unselected.
Click Next.
16.
In the Reporting Services

Install the native mode
default configuration.
Click Next.
17.
In the Error and Usage

Reporting screen, select any
appropriate options and click
Next.
Page 36
Step Description
18.
Screenshot
In the Installation Rules

screen, the installation rules
are automatically checked to
see if the installation process
will be blocked.
Note
If any of the installation
rules fail, these will need
to be resolved, and the
operation re-run, before
the installation can
continue.
Click Next.
19.
In the Ready to Install

screen, verify that the
components and settings
selected are correct.
Click Install.
5.5
Deploying all Roles to a Single Server
Operations Manager 2007 requires two installation procedures to install all of the server roles on a
single server. Deployment of the RMS and Operations Database is combined in one installation, as
detailed in section 5.5.1, and the Reporting Server and Database Warehouse are combined in
another installation, as detailed in section 5.5.2.
Page 37
5.5.1
Installing the Root Management Server and Operations

Database
Follow the steps provided in Table 6 below to install the RMS and Operations Database.
Step Description
Screenshot
1.
Execute SetupOM.exe from the

folder that contains the source
files for Operations Manager
2007. The System Center
Operations Manager 2007
Setup screen displays. Click
Install Operations Manager
2007 to continue.
2.
In the Welcome to the

System Center Operations
Manager 2007 Setup
Wizard screen, click Next.
Page 38
Step Description
3.
Screenshot

agreement.
Click Next.
4.

and Organization.
Click Next.
5.

ensure that all components are
selected for installation.
Manager 2007.
Click Next.
Page 39
Step Description
6.
Screenshot

any failed checks.
Click Next.
7.

Click Next.
8.

Instance screen, select the
SQL Server database instance
from the drop-down list.
Click Next.
Page 40
Step Description
Screenshot
9.
In the Database and Log File

Options screen, click Next.
10.
In the Management Server

Action Account screen, select
Domain or Local Computer
Account.
Enter the User Account and
Password for the account to be
used for the Management
Server Action account.
Choose the Domain or local
computer from the drop-down
list provided.
Click Next.
11.
In the SDK and Config Service

Account screen, select Domain
or Local Account.
used for the SDK and Config
Service account.
list provided.
Click Next.
Page 41
Step Description
12.
Screenshot
In the Web Console

Authentication Configuration
screen, select Use Windows
Authentication
(Recommended).
Click Next.
13.
In the Operational Manager

Error Reports screen, click
Next.
14.

Click Next.
Page 42
Step Description
15.
Screenshot

Table 6: Installing the Root Management Server and Operations Database
5.5.2
Installing the Reporting Server and Data Warehouse
Follow the steps in Table 7 below to install the Reporting Server and Data Warehouse.
Step Description
1.
Screenshot

2007 Reporting to continue.
Page 43
Step Description
Screenshot
2.

3.

license agreement.
Click Next.
4.

and Organization.
Click Next.
Page 44
Step Description
5.
Screenshot

click the Browse button and
Manager 2007.
Click Next.
6.

any failed checks.
Click Next.
7.

Management Server.
Click Next.
Page 45
Step Description
8.
Screenshot

Instance screen, select the SQL
Server database instance from
the drop-down list provided.
Click Next.
9.

10.
In the SQL Server Reporting

Services Instance screen,
select the SQL Server
Reporting Services Server
from the drop-down list
provided.
Click Next.
Page 46
Step Description
11.
Screenshot
In the Data Warehouse Write

Account screen, enter the User
Account and Password for the
account to be used for the Data
Warehouse Write account.
Select the Domain from the
Click Next.
12.
In the Data Reader Account

screen, enter the User Account
and Password for the account
to be used for the Data Reader
account.
Click Next.
13.
In the Operational Data

Reports screen, Select No,
dont send operational data
reports to Microsoft.
Click Next.
Page 47
Step Description
14.
Screenshot

Table 7: Installing the Reporting Server and Reporting Data Warehouse
5.6
Deploying Roles to Multiple Servers
This section covers the installation of each of the Operations Manager 2007 server roles to a
separate server.
5.6.1
Installing the Operations Database
Follow the steps in Table 8 below to install the Operations Database.
Step Description
1.
Screenshot

2007 to continue.
Page 48
Step Description
Screenshot
2.

click Next.
3.

agreement.
Click Next.
4.

screen, enter the User Name
and Organization.
Click Next.
Page 49
Step Description
5.
Screenshot

ensure that only the Database
installation.
Manager 2007.
Click Next.
6.

failed checks.
Click Next.
7.

Click Next.
Page 50
Step Description
8.
Screenshot

Instance screen, select the SQL
Server database instance from
the drop-down list provided.
Click Next.
9.
10.

In the Operational Manager

Error Reports screen, click
Next.
Page 51
Step Description
11.
Screenshot

Click Next.
12.

Table 8: Installing the Operations Database
Page 52
5.6.2
Installing the Root Management Server/Management Server
Follow the steps in Table 9 to install the RMS or an additional Management Server.
Step Description
Screenshot
1.

2007 to continue.
2.

click Next.
Page 53
Step Description
3.
Screenshot

agreement.
Click Next.
4.

and Organization.
Click Next.
5.

ensure that only the
Management Server
installation.
Manager 2007.
Click Next.
Page 54
Step Description
6.
Screenshot

failed checks.
Click Next.
7.
In the SC Database Server

Instance screen, enter the
Operations Database was
installed to and the SQL
instance for the SC database
server.
Click Next.
8.
In the Management Server

Action Account screen, Select
Domain or Local Computer
Account.
used for the Management
Server Action account.
list provided.
Click Next.
Page 55
Step Description
9.
Screenshot
In the SDK and Config Service

Account screen, select Domain
or Local Account.
used for the SDK account.
list provided.
Click Next.
10.
Note
This step only applies to
the first Management
Server, that is the RMS,
installed into a
Management Group.
In the Web Console
Authentication
(Recommended).
Click Next.
11.

Table 9: Installing the Root Management Server/Management Server

Page 56
5.6.3
Installing the Operations Console
Follow the steps in Table 10 to install the Operations Console.
Step Description
Screenshot
1.

2007 to continue.
2.

click Next.
Page 57
Step Description
3.
Screenshot

agreement.
Click Next.
4.

and Organization.
Click Next.
5.

ensure that only the User
Interface and Command Shell
(optional) components are
selected for installation.
Manager 2007.
Click Next.
Page 58
Step Description
6.
Screenshot

failed checks.
Click Next.
7.

Click Next.
8.

Table 10: Installing the Operations Console

Page 59
5.6.4
Installing the Web Console
Follow the steps in Table 11 to install the Web Console.

Step
Description
Screenshot
1.

2007 to continue.
2.

click Next.
Page 60
Step
3.
Description
Screenshot

agreement.
Click Next.
4.

and Organization.
Click Next.
5.

ensure that only the Web
Console component is selected
for installation.
Manager 2007.
Click Next.
Page 61
Step
6.
Description
Screenshot

the failed checks.
Click Next.
7.
In the Connect to the Root

Management Server.
Click Next.
8.
Note
This step only applies to
the first Management
Server, that is the RMS,
installed into a
Management Group.
In the Web Console
Authentication
(Recommended).
Click Next.
Page 62
Step
9.
Description
Screenshot

Table 11: Installing the Web Console
5.6.5
Installing the Reporting Server
Follow the steps in Table 12 to install the Reporting Server.

Step
1.
Description
Screenshot

Page 63
Step
Description
Screenshot
2.

3.

license agreement.
Click Next.
4.

and Organization.
Click Next.
Page 64
Step
5.
Description
Screenshot

Manager 2007.
Click Next.
6.

any failed checks.
Click Next.
7.

Instance screen, select SQL
Server database instance
provided.
Click Next.
Page 65
Step
Description
Screenshot
8.

9.

Table 12: Installing the Reporting Server
Page 66
5.6.6
Installing the Data Warehouse
Follow the steps in Table 13 to install the Data Warehouse

Step
Description
Screenshot
1.

2.
In the Welcome to the

Operations Manager 2007 R2
Reporting Setup screen, click
Next.
Page 67
Step
3.
Description
Screenshot

license agreement.
Click Next.
4.

and Organization.
Click Next.
5.

Manager 2007.
Click Next.
Page 68
Step
6.
Description
Screenshot

any failed checks.
Click Next.
7.

Management Server.
Click Next.
8.
In the Connect to the

Operations Manager Data
Warehouse screen, enter the
Data Warehouse was installed
to and the SQL instance for the
SQL Server database
instance.
Click Next.
Page 69
Step
9.
Description
Screenshot
In the SQL Server Reporting

Services Instance screen,
select the SQL Server
Reporting Services Server
provided.
Click Next.
10.
In the Data Warehouse Write

Account screen, enter the
User Account and Password
for the account to be used for
the Data Warehouse Write
account.
Click Next.
11.
In the Data Reader Account

screen, enter the User
Account and Password for the
account to be used for the Data
Reader account.
Click Next.
Page 70
Step
12.
Description
Screenshot
In the Operational Data

Reports screen, select No,
dont send operational data
Click Next.
13.

Table 13: Installing the Data Warehouse
5.7
Agent Installation
5.7.1
Discovery-based
To deploy the Operations Manager 2007 agent to Windows-based computers from the
Operations Console:
1. Launch the Operations Console and select the Administration pane.
2. At the bottom of the navigation pane, click Discovery Wizard...
3. In the Discovery Type screen, select Windows computers.
4. Click Next.
5. In the Auto or Advanced? screen, select either Automatic computer discovery or
Advanced discovery.
For Automatic computer discovery, click Next.
For Advanced discovery, perform the following steps:
Page 71
a. In the Computer & Device Types list, select Servers & Clients or Server Only. If
Servers & Clients is selected, the Verify discovered computers can be contacted
may also be selected (this is optional). This is likely to increase the success rate of
agent deployment, but discovery can take longer.
b. In the Management Server list, click the Management Server or Gateway Server to
discover the computers.
c. Click Next.
d. From the Discovery Method screen, computers can be discovered by either scanning
or browsing Active Directory Domain Services (DS), or typing the computer names.
To scan Active Directory DS:
i.
Select Scan Active Directory and then click Configure.
ii. In the Find Computers box, type the criteria required for discovering computers.
iii. Click OK.
iv. Select the Domain of the computers to be discovered from the drop-down list
provided.
To browse Active Directory DS or manually type the computer names:
i.
Select Browse for, or type-in computer names, click Browse, specify the names of
the computers to be managed.
ii. Click OK.

iii. In the Browse for, or type-in computer names box, type the computer names,
separated by semi-colon, comma, or a new line.
e.
Click Next.
6. In the Administrator Account screen, perform one of the following:

Select Use selected Management Server Action Account.
Select Other user account. Enter the User name and Password for an account with
Administrator rights on the intended servers for installation and discovery, and select
the Domain from the drop-down list provided.
7. Click Discover. The Discovery Progress screen displays.

8. In the Objects to Manage screen, perform the following:
a. Select the computers to be agent-managed.
b. In the Management Mode list, click Agent and then click Next.
9. In the Summary screen, perform the following:
a. Enter the location to install the agent to in the Agent installation directory box.
b. For Agent Action Account select Local System.
c. Click Finish.
10. The Agent Management Task Status screen displays the status of each selected
computer. When the status changes from Queued to Success, the computers are ready to
be managed. If the task fails for a computer, click the targeted computer. The reason for the
failure is displayed in the Task Output box.
11. Click Close.
Page 72
5.7.2
Manual
Follow the steps in Table 14 to manually install the agent.
Step Description
Screenshot
1.

2007. On the initial splash
screen click Install Operations
Manager 2007 Agent.
2.

2007 R2 Agent Setup wizard
screen, click Next.
Page 73
Step Description
Screenshot
3.
In the Destination Folder

screen, leave the default
installation folder as
C:\Program Files\System
2007, and click Next.
4.

Specify Management Group
information.
Click Next.
5.

Configuration screen enter the
Management Group Name and
Management Server.
Click Next.
Page 74
Step Description
6.
Screenshot
In the Agent Action Account

screen, select Local System.
Click Next.
7.
In the Ready to Install screen,

confirm the settings are correct
and click Install.
Table 14: Manual Agent Installation
5.7.3
Unattended
This section provides the information required for deploying the agent silently via an existing
software deployment solution. The following files from the Operations Manager 2007 installation
media are required:
MOMAgentInstaller.exe
MOMAgentInstallerPS.dll
MOMAgent.msi
The following command line can be used to silently install the agent:
msiexec.exe /i momagent.msi /qn /l*v omagentinstall.log
MANAGEMENT_GROUP=<ManagementGroupName>
MANAGEMENT_SERVER_DNS=<ManagementServerHostName>
Page 75
Table 15 below contains a list of the available command line switches for agent installation.
Command Line Switch
Description
INSTALLDIR=<path>
USE_SETTINGS_FROM_AD=0
The agents Management Group settings will be

provided on the command line
This is the default setting that is applied when
neither USE_SETTINGS_FROM_AD or
USE_MANUALLY_SPECIFIED_SETTINGS is
specified on the command line
USE_MANUALLY_SPECIFIED_SETTINGS=0
The agents Management Group settings will be

provided by Active Directory
MANAGEMENT_GROUP=
Sets the agents Management Group
<ManagementGroupName>
MANAGEMENT_SERVER_DNS=
<ManagementServerHostName>
Sets the agents Management Server (must be a

Fully Qualified Domain Name (FQDN))
ACTIONS_USE_COMPUTER_ACCOUNT=0
The agent will use a specified domain user account,

as opposed to the Local System account
ACTIONSUSER=<AgentActionAccount>
Set the agents Action Account
ACTIONSDOMAIN=<AgentActionAccountDoma Set the agents Action Account domain

in>
ACTIONSPASSWORD=<AgentActionAccountP
assword>
Set the agents Action Account password
Table 15: Agent Installation Command Line Switches
Page 76
STABILISE
The Stabilise phase involves testing the solution components whose features are complete,
resolving and prioritising any issues that are found. Testing during this phase emphasises usage
and operation of the solution components under realistic environmental conditions.
During this phase, testing and acceptance of the Operations Manager 2007 solution and its
associated network components, will take place. The aim is to minimise the impact on normal
business operations by testing the design assumptions and verifying the deployment process in a
pilot program. It is important that this phase of testing and verifying should begin during the
Develop phase and continue through the Deploy and Operate phases.
Figure 4 acts as a high-level checklist, illustrating the areas of the Operations Manager 2007
design that an IT Professional is responsible for testing and validating:
Figure 4: Sequence for Stabilising System Center Operations Manager 2007
Page 77
6.1
Server Role Installation
Prior to deployment in a live network environment, it is important to test the installation of each of
the server role components required in the designed Operations Manager 2007 solution. This
testing should include:
Deployment and patching of all prerequisite software
Service account creation and rights/permission assignments
Server role installation, as detailed in section 6
6.2
Agent Deployment
There are a number of options to choose from for deploying the Operations Manager 2007 agent,
each of which should be fully tested prior to use in a live network environment. Once the agent has
been deployed, the Operations Console should be checked to verify that the agent is
communicating correctly with its designated Management Server. The following areas of agent
deployment should be thoroughly tested:
Deployment and patching of prerequisite MSXML 6.0
Agent deployment using the Discovery Wizard
Manual agent deployment (trusted and un-trusted)
Agent deployment as part of an automated build process
Verification of agent deployment using the Operations Console
6.3
Operations Console
The Operations Console displays data stored in the Operations Database and Reporting Data
Warehouse database. The following areas of the Operations Console should be fully tested:
Agent state is correctly displayed in the Monitoring and Administration sections of the
console
Alert data appears correctly in the Monitoring section of the console
6.4
Management Packs
Management Packs contain all of the monitors, rules and tasks that are required to successfully
monitor a software or hardware component. It is therefore essential to ensure that each
Management Pack is working as expected prior to importing it in a live network environment. The
following Management Packs features should be thoroughly tested:
Importing a Management Pack (see section 7.4) into the Operations Console
Checking that Management Pack configuration is deployed correctly to agents
Ensuring the Management Pack reports are available in the Reporting section of the
Operations Console
Page 78
6.5
Reporting
Reporting is an essential part of the Operations Manager 2007 solution. It is important to ensure
that all aspects of Reporting are working as expected, prior to deploying Operations Manager in a
live network environment. The following reporting components should be thoroughly tested:
The Reporting section is available in the Operations Console
Reports can be launched from the Operations Console
Subscribing to reports
Graphs are displayed correctly
Page 79
DEPLOY
The Deploy phase is used to manage the deployment of core solution components for widespread
adoption in a controlled environment. During the managed deployment, the solution is tested and
validated through ongoing monitoring and evaluation. The solution is then transitioned to
Operations and Support.
Figure 5 acts as a high-level checklist, illustrating the critical tasks that an IT Professional
responsible for deploying Operations Manager 2007 needs to perform:
Figure 5: Sequence for Deploying System Center Operations Manager 2007
Page 80
7.1
Operations Console
Most of the configuration and administration tasks for Operations Manager 2007 can be performed
through the Operations Console. Figure 6 shows the layout of the console:
Figure 6: The Layout of the Operations Console
7.1.1
Panes
The Operations Console is divided into a number of panes:

Navigation This pane is on the top left and provides a navigation tree. The content of the
Navigation pane is determined by the view currently selected (see Section 7.1.2)
Results This pane is in the centre of the screen and occupies the top centre of the screen
if a Details pane is also displayed. The data displayed here is determined by what is
selected in the Navigation Pane
Details This pane displays more information about the object selected in the Results
Pane. The Details pane does not exist in all views, but when displayed it occupies the
bottom centre of the screen
Actions This pane displays a list of actions that can be performed against the object
currently selected in the Results pane. The available actions are context sensitive in
relation to the current scope (see Section 7.1.3.1), view and selected object
7.1.2
Views
The available views in the Operations Console can be selected from the bottom left corner of the
Operations Console. Sections 7.1.2.1 to 7.1.2.5 provide details of what each view provides.
Page 81
7.1.2.1
Monitoring
The Monitoring view displays monitoring data such as alerts and performance data. The views are
arranged in a folder structure to make it easier to find views related to specific features or
management packs. The display options of existing views can be personalised. It is also possible to
create custom views and folders.
7.1.2.2
Authoring
The Authoring view allows the settings for all imported management packs to be viewed. The
views are arranged by generic object type, and the results are grouped based on which named
object they are applied to.
Overrides can be defined in the Authoring view to disable or alter the behaviour of an existing rule
or monitor. New Management Pack objects can also be created and configured.
7.1.2.3
Reporting
The Reporting view is only available after a Reporting Server and Data Warehouse have been
installed for the Management Group. The Reporting view provides access to all of the generic
reports and management pack specific reports. From this view, reports can be executed on an adhoc or scheduled basis, and new reports can also be created.
7.1.2.4
Administration
The Administration view is where the configuration of the Management Group takes place, which
includes:
Discovery-based installation of agents
Importing management packs
Configuring notification
Defining security for Run As accounts and users
Configuring connectors
7.1.2.5
My Workspace
The My Workspace view provides an area where custom workspaces and searches can be saved.
This provides a working environment that can be tailored to provide faster and more convenient
access to items most needed for a particular role.
7.1.3
7.1.3.1
Refining Data Selection

Scoping
Within the Operations Console, it is possible to change the scope of certain views in order to only
return objects that meet specific criteria.
Page 82
To set the scope of a view:

1. In the Operations Console, click the Monitoring button.
2. Select an available view in the Navigation pane, and then click the Scope button on the
toolbar. The Change View Scope dialog box displays.
3. Select an option from the list of Matching objects and click OK.
4. The data in the Results pane will be updated to only display objects that meet the defined
scope. The defined scope is also displayed in a status bar across the top of the results
pane.
5. To remove the scope, click on the X on the right hand side of the scope status bar at the
top of the results pane.
7.1.3.2
Find and Search
Within the Operations Console, clicking the Search button will return all objects within a result set
that meet specific criteria, whilst clicking the Find button will locate a particular object within a large
result set.
To specify search criteria:
2. In the search box on the toolbar, type the criteria, such as object type or machine name,
and click Search. The Search window will open and display a list of relevant objects.
To locate an object within a set of results:
2. Select a view from the Navigation pane to return a list of objects in the Results pane.
3. Click the Find button on the toolbar to display the Look for toolbar across the top of the
Results pane.
4. Type the criteria, such as the name of an object, in the Look for box and click Find Now.
The data in the Results pane will be updated to only display objects that meet the criteria.
5. To return to the full result set, click Clear on the Look for toolbar across the top of the
Results pane.
7.1.3.3
Time Filters
Within the Operations Console, time filters can be applied to monitoring views to limit the result set
to a specific time period.
To set a time filter:
2. Select a view from the Navigation pane to return the list of objects in the Results pane.
3. Click the Calendar button on the toolbar.
4. Select the time criteria to be used to limit the result set. The data in the Results pane will be
updated to only display objects that are relevant to the selected time period.
7.2
Server Settings
Once Operations Manager 2007 has been installed, there are a number of server settings that can
be modified. These settings can be configured in the Administration pane of the Operations
Console. This section provides information on the various settings and provides step-by-step
Page 83
instructions on how to configure these settings via the Operations Console. The majority of these
settings should not need to be modified from the default values.
7.2.1
Agent Heartbeat
Heartbeat is the mechanism in Operations Manager 2007 that keeps the RMS informed about the
status of the Health Service on an agent. This setting specifies how often the agent should send a
heartbeat packet to its Management Server. Heartbeat is covered in more detail in section 8.2.2.
The Agent Heartbeat interval should be left as the default setting of 60 seconds, as shown in Figure
7.
Figure 7: The Heartbeat Interval
Page 84
7.2.2
General Alerts
Alert resolution states allow the classification of alerts, to understand the current status of an alert
within the monitored environment. By default, there are only two states, New and Closed. More
alert resolution states can be added as required, for example, a state called Owned, to show that
someone has ownership of an alert. Follow the steps provided in Table 16 to add an Alert
Resolution state.
Step Description
Screenshot
1.
On the Alert Resolution

States tab, click New... to add
an additional resolution state.
2.
On the Auto-Resolve Alerts

tab, leave the settings at their
defaults:
Resolve all active alerts in
the new resolution state
after : 30 days
Resolve all active alerts
when the alert source is
healthy after : 7 days
Table 16: Adding an Alert Resolution State

Page 85
7.2.3
General Database Grooming
Database Grooming is used to define the point at which specific object types are removed from the
Operations Database. Grooming is necessary to maintain the performance of the Operations
Database, which would be adversely affected if it was left to grow in size due to unnecessary
records being stored. The Database Grooming settings are given in Figure 7.
Figure 8: Database Grooming Settings
It is recommended that the Database Grooming settings detailed in Table 17 are used, and that
they are only adjusted to lower values if performance becomes an issue.
Records to delete
Older than
Resolved Alerts
7 days
Event data
7 days
Performance data
7 days
Task history
7 days
Monitoring Job data
7 days
Static change events data
7 days
Performance signature
2 days
Maintenance mode history
7 days
Availability history
7 days
Table 17: Database Grooming Settings
Page 86
7.2.4
General Privacy
These settings specify whether any data from the Operations Manager 2007 deployment should be
shared with Microsoft. Follow the steps provided in Table 18 to specify the settings for the Windows
Customer Experience Improvement Program.
Step Description
Screenshot
1.
On the CEIP tab, select I dont

want to join the program at
this time.
2.
On the Operational Data

Reports tab, select No, dont
send operational data
Page 87
Step Description
Screenshot
3.
On the Error Reporting tab,

select Dont generate error
reports.
4.
On the Error Transmission

tab, leave the boxes as
unchecked.
Table 18: Specifying Settings for the Windows Customer Experience Improvement Program
Page 88
7.2.5
General Reporting
This setting, as shown in Figure 9, specifies the URL for the Reporting Server. If this is not set
correctly, reports will not be accessible via the Operations Console.
Figure 9: Reporting Server Settings
The Reporting server URL value will be automatically populated during the installation of the
Operations Manager 2007 Report Server component.
7.2.6
General Web Addresses
This setting, as shown in Figure 10, specifies the URL for the Web Console, and also allows an
optional online product knowledge repository to be specified.
Figure 10: Web Address Settings
Page 89
The Web console value will be automatically populated during the installation of the Operations
Manager 2007 Web Console component.
The Online product knowledge value will be left blank.
7.2.7
Server Heartbeat
status of the Health Service on an agent. This setting specifies the Management Servers tolerance
for missed heartbeats. Heartbeat is covered in more detail in section 8.2.2.
As shown in Figure 11, the Number of missed heartbeats allowed setting should be set to the
default of 3.
Figure 11: Specifying the Management Servers Tolerance for Missed Heartbeats
Page 90
7.2.8
Server Security
This setting controls whether or not manual agent installations will be allowed, and if allowed
whether they need explicit approval.
As shown in Figure 12, the Review manual agent installations in pending management view
radio button should be checked. The Auto-approve new manually installed agents checkbox
should not be selected.
Figure 12: Specifying the Acceptance or Rejection of Manual Agent Installations
7.3
SQL Configuration
It is important that the SQL Server installation is configured correctly to ensure that it provides a
stable platform for the Operations Manager 2007 installation.
7.3.1
SQL Service Principal Name Registration
Operations Manager 2007 requires that the Service Principal Name (SPN) for the SQL Server
instance it uses is registered correctly.
Page 91
To verify the SQL Server SPN:

1. Logon to a domain-joined computer using an account that has administrator rights in the
domain that Operations Manager 2007 is installed to.
2. Launch a command prompt using the Runs as administrator option.
3. If the SQL Server service account is a domain account, at the command prompt type:
setspn L <svcaccountname>
If the SQL Server service account is Local System or Network Service, at the command
prompt type:
setspn L <sqlservercomputername>
4. If the SQL Server SPN is correctly registered, the following output should be displayed:
MSSQLSvc/<svcaccountname>:<sqlserverportnumber>
or
MSSQLSvc/<sqlservercomputername>:<sqlserverportnumber>
5. If no SPN is returned, type the following at the command prompt to add a new SPN:
setspn A MSSQLSvc/<svcaccountname>:<sqlserverportnumber>
or
setspn A MSSQLSvc/<sqlservercomputername>:<sqlserverportnumber>
6. If an incorrect SPN is returned, type the following at the command prompt to update the
SPN:
setspn R <svcaccountname>
or
setspn R <sqlservercomputername>
7.3.2
SQL Server Broker Service
The SQL Server Broker Service is a dependency of the Operations Manager 2007 discovery
process, as well as other workflows. Ensure that this service remains enabled.
7.4
Importing Management Packs
The process for importing a new Management Pack into the Operations Console is quite straight
forward.
To import a Management Pack:
1. Launch the Operations Console.
2. Select the Administration pane, then right-click Management Packs and select Import
Management PacksQ
3. Select the .MP (sealed) or .XML (unsealed) file/s from the file system for the Management
Pack to be imported.
4. When the Import Management Packs page displays, check to see that no issues/errors
are raised regarding the importing of the selected files. If there are any issues/errors, these
will need to be resolved, before the Management Pack can be imported.
5. Click Import.
Page 92
OPERATE
During the Operate phase, solution components are proactively managed as an end-to-end IT
Service to ensure the service provides the required levels of solution functionality, reliability,
availability, supportability and manageability. Successfully bringing a well-designed service into a
production environment takes efficient planning to balance speed, cost and safety, while ensuring
minimum disruption to operations and supporting the 'business as usual' delivery of the
organisation's IT requirements.
Figure 13 acts as a high-level checklist, illustrating the critical components for which an IT
Professional is responsible for maintaining in a managed and operational Operations Manager
2007 deployment:
Figure 13: Sequence for Operating System Center Operations Manager 2007
8.1
Managing Management Packs
Management Packs contain all of the knowledge that is used for monitoring in Operations Manager
2007. In many cases, the rules and monitors defined within vendor-supplied Management Packs
can be left to run with their default settings. There are, however, cases where some configuration is
required, and this is usually achieved by creating an override for an existing rule or monitor. Most
vendor-supplied Management Packs are sealed, which means they cannot be altered. In order to
save an override, an unsealed management pack needs to exist prior to setting up the override.
By default, overrides and other customisations are saved to the Default Management Pack (an
unsealed Management Pack created during installation). However, as a best practice, separate
unsealed Management Packs should be created for each sealed Management Pack that requires
changes to be made.
Any customisations that are made to an unsealed Management Pack introduce a dependency
relationship with the sealed Management Pack. As a result, if the sealed Management Pack ever
needs to be deleted, the unsealed Management Pack with customisations must also be deleted.
Page 93
If customisations for all the sealed Management Packs have been stored together, then all of those
customisations will be lost, or the specific customisations for the Management Pack being removed
will need to be found and manually removed first.
To create a new unsealed Management Pack for overrides:
1. Launch the Operations Console and click the Administration button.
2. In the navigation pane, right-click Management Packs, and select Create New
Management Pack. The Create a Management Pack page displays.
3.
Enter the Name and a Description (this is optional) for the new Management Pack.
4. Click Next.
5. Click Create.
To create an override for a monitor:
1. Launch the Operations Console and click the Authoring button.
2. In the Navigation pane, expand Management Pack Objects and select Monitors.
3. In the Results pane, find the desired monitor that requires an override, right-click it, select
Overrides, and select Override the Monitor. The override target options available include:
For all objects of a specific type
For a group
For a specific object of class:<ClassTypeofObjectMonitor>
4. Select a target for the override. The Override Properties page displays.
5. Select the Override check box for the settings to override.
6. Update the value of the Override Setting to the desired value.
7. Choose an unsealed Management Pack from the Select destination management pack
drop down list, or click the New button to create one.
8. Click OK.
8.2
Managing Agents
Once the Operations Manager 2007 server infrastructure is in place and agents have been
deployed to the monitored servers, a large part of the ongoing administration and management of
the solution will be the management of the deployed agents.
8.2.1
State
Agent state provides a high-level view of the status of an agent, calculated from the roll-up of all of
the monitors and alerts relevant to the selected agent. An agent can have one of the following
states:
Healthy (Green Tick) In this state, everything on the agent is running as expected
Critical (Red Cross) In this state, a problem has been reported on this agent and should
be investigated
Unknown (Solid Gray) In this state, the RMS is not receiving an data from the agent,
indicating the agent could be offline or there may be connectivity issues
Unknown (Solid Green) In this state, no status has yet been reported for this object
Page 94
To determine what is responsible for an agents overall state, Health Explorer can be used to
display all of the monitors and alerts for a particular agent. The monitors are displayed in a
hierarchical layout that displays the relationships and dependencies between monitored objects on
the agent.
To launch Health Explorer:
1. Launch the Operations Console and click the Monitoring button.
2. In the navigation pane, select Windows Computers to return a list of agents in the Results
pane.
3. Right click on an agent in the results pane and select Health Explorer. The Health
Explorer page displays, and any monitors in a failed state are automatically expanded for
easy visibility.
8.2.2
Heartbeat
status of the Health Service on an agent. The Heartbeat process involves the agent sending a data
packet to its Management Server on a periodic basis, which by default is once every 60 seconds.
The Management Server is configured with a tolerance level for missed Heartbeats, which by
default is 3. When a fourth Heartbeat data packet fails to be received, the Management Server will
generate an alert to indicate that communication with the agent has been lost. The Management
Server will then attempt to ping the agent. If there is no response to the ping, a second alert will be
generated.
The Heartbeat system allows some basic diagnosis of the potential issue, namely:
The first and second alerts being generated suggest the server hosting the agent is offline,
or there may be a connectivity issue
Just the first alert being generated suggests that the issue may be with the agents Health
Service, as the server hosting it is online and responding on the network
The settings for Heartbeat are configured globally for all agents (see Section 7.2.1) and
Management Servers (see Section 7.2.7), but it is also possible to override these on specific
agents and Management Servers where a smaller or larger threshold is required. Heartbeat
monitoring can also be disabled completely if required.
To override the heartbeat interval setting on an individual agent:
2. In the navigation pane, expand Administration, expand Device Management and then
select Agent Managed.
3. In the results pane, right-click the targeted agent and select Properties.
4. In the Agent Properties dialog box, select Override global server settings.
5. Type the desired value in seconds (the range is from 5 to 86,400 seconds) for the
Heartbeat interval.
6. Click OK.
Page 95
To override the missed heartbeats setting on an individual Management Server:

2. In the navigation pane, expand Administration, expand Device Management and then
select Management Servers.
3. In the results pane, right click the targeted Management Server and select Properties.
4. In the Management Server Properties dialog box, select the Heartbeat tab.
5. Select Override global server settings.
6. Type the required value for the Number of missing heartbeats.
7. Click OK.
To disable heartbeat monitoring on an individual agent:
1. Launch the Operations Console and click the Authoring button.
2. Expand Management Pack Objects and select Monitors.
3. Find the Health Service Heartbeat Failure monitor for the object Health Service Watcher
(Agent).
4. Right-click the target object and select Overrides, select Disable the Monitor and select
For a specific object of class: Health Service Watcher (Agent).
5. In the Select Object dialog box, select the desired agent.
6. Click OK.
8.3
Managing Alerts
Rules and monitors in Operations Manager 2007 are designed to generate alerts to indicate a
potential issue. These alerts are visible in the Operations Console (and Web Console).
To view an alert:
2. In the navigation pane, expand Monitoring and select Active Alerts.
3. In the results pane, select an alert to view further information about (this will be displayed in
the details pane).
Alerts that are generated by a monitor will resolve automatically when the conditions that trigger the
alert return to their expected behaviour. However, while the alert is active, it may be useful to alter
the alert resolution state to reflect that is has been acknowledged and action is being taken.
Additionally, alerts triggered by rules do not resolve automatically and need to be managed and
resolved manually.
To update the resolution state of an alert:
2. In the navigation pane, expand Monitoring and select Active Alerts.
3. Right- click an alert in the result pane, select Set Alert Resolution State and select a
resolution state from the list.
By default, the only resolution states available are New and Closed until additional resolution
states are defined (see Section 7.2.2).
Page 96
8.4
Backup
8.4.1
What to Backup
To ensure that an Operations Manager 2007 solution can be optimally recovered in the event of
failure, the following items should be backed up and stored securely:
Operations Database (OperationsManager) Full backup weekly and
Incremental/Differential backup daily
Reporting Data Warehouse (OperationsManagerDW) Full backup weekly and
Incremental/Differential backup daily
Master Database (master) Full backup after initial installation, and after any
security/logon changes
MSDB Database (msdb) Full backup after initial installation
RMS Encryption Key Backup when prompted after installation
IIS 6.0 Metabase or IIS 7.0 configuration Backup after installation
Custom Management Packs Backup after creation, or after making any changes
Custom reports Backup after creation, or after making any changes
8.4.2
Full Recovery Mode
By default, when the Operations Database is installed, it is configured to use Simple Recovery
mode. Simple Recovery mode results in smaller transaction logs and saves disk space, but does
not provide the optimal recovery options. For optimal recovery options, the Operations Database
should be configured to use Full Recovery mode. In Full Recovery mode, transaction logs will grow
much larger and will need to be backed up regularly in order to truncate them and preserve disk
space. However, in the event of failure, Full Recovery mode provides the capability to recover to
the moment of failure, whereas a database set to Simple Recovery mode would only be capable of
recovering to the last good backup.
Page 97
APPENDIX A
SKILLS AND TRAINING RESOURCES
The table in PART I of this appendix list the suggested training and skill assessment resources
available. This list is not exhaustive; there are many third-party providers of such skills. The
resources listed are those provided by Microsoft. PART II lists additional training resources that
might be useful.
PART I TRAINING RESOURCES

For further information on System Center Operations Manager 2007, see
http://www.microsoft.com/systemcenter/operationsmanager/en/us/default.aspx.
Skill or Technology
Resource Location
Area
Description
Certificates
http://technet.microsoft.com/en-gb/library/dd362553.aspx
How to obtain a Certificate Using Windows

Server 2008 Enterprise CA in Operations
Manager 2007
Passwords
http://technet.microsoft.com/en-gb/library/bb735422.aspx
How to Change IIS ReportServer

Application Pool Account Password for
Passwords
How to Change the Reporting Server

Execution Account Password in
Service Accounts
http://technet.microsoft.com/en-gb/library/cc540429.aspx
How to Change the SDK and Config

Service Accounts in Operations Manager
2007
Passwords
How to Change the Windows Service

Account Password for the SQL Server
Reporting Service in Operations Manager
2007
Service Accounts
http://technet.microsoft.com/en-gb/library/cc540432.aspx
How to Set the Action Account on Multiple

Computers in Operations Manager 2007
Table 19:System Center Operations Manager 2007 Training and Skill Assessment Resources
Page 98
PART II SUPPLEMENTAL TRAINING RESOURCES

Title
Link
Installing and Configuring System Center

http://www.microsoft.com/learning/en/us/Course.aspx?ID=50028B&Locale=en-us
Monitoring Enterprise Systems with Microsoft

System Center Operations Manager 2007
https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=78454
&tab=overview
Deploying Microsoft System Center Operations

Manager 2007
&tab=overview
Monitoring SQL Server and Distributed

Applications with Microsoft System Center
&tab=overview
Monitoring Clients with Microsoft System Center

&tab=overview
Monitoring Exchange Server with Microsoft

System Center Operations Manager 2007
&tab=overview
Implementing Microsoft System Center

https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=1383
07
System Center Operations Manager 2007:

Advanced Configuration and Administration
http://www.microsoft.com/learning/en/us/Course.aspx?ID=50216A&Locale=en-us
System Center Operations Manager 2007:

Advanced Management Pack Authoring
http://www.microsoft.com/learning/en/us/Course.aspx?ID=50231A&Locale=en-us
Table 20: Supplemental Training Resources
Page 99
APPENDIX B
DOCUMENT INFORMATION
PART I TERMS AND ABBREVIATIONS

Abbreviation
Definition
ACS
Audit collection Service
CUI
Common User Interface
DB
Operations Database
DNS
Domain Name System
DS
Domain Services
DW
Reporting Data Warehouse
EULA
End-User License Agreement
FQDN
Fully Qualified Domain Name
IIS
Internet Information Services
IM&T
Information Management & Technology
MDAC
Microsoft Data Access Components
ML
Management License
MS
Management Server
MSXML
Microsoft XML Core Services
NAT
Network Address Translation
OVO
OpenView Operations
RMS
RS
Reporting Server
SIP
Session Initiation Protocol
SMB
Server Message Block
SMS
Short Message Service
SMTP
Simple Mail Transfer Protocol
SP
Service Pack
SPN
Service Principal Name
WS
Web Services
XML
Extensible Markup Language
Table 21: Terms and Abbreviations
Page 100
PART II REFERENCES
Reference
Document
Version
R1.
Microsoft Blogs TechNet: System Center Operations Manager: Understanding how Active
Directory Integration Feature Works in Operations Manager 2007:
http://blogs.technet.com/momteam/archive/2008/01/02/understanding-how-active-directoryintegration-feature-works-in-opsmgr-2007.aspx
Jan, 2008
R2.
Microsoft: System Center Operations Manager 2007 R2: Operations Manager 2007 R2 Design July 2009
Guide:
http://download.microsoft.com/download/B/F/D/BFDD0F66-1637-4EA3-8E6E8D03001E5E66/OM2007R2_DesignGuide.docx
R3.
Microsoft: System Center Operations Manager 2007 R2: Operations Manager 2007
Deployment Guide:
http://download.microsoft.com/download/B/F/D/BFDD0F66-1637-4EA3-8E6E8D03001E5E66/OM2007R2_DeploymentGuide.docx
July 2009
R4.
Microsoft: System Center Operations Manager 2007 R2: Operations Manager 2007 R2
Operations Users Guide:
http://download.microsoft.com/download/B/F/D/BFDD0F66-1637-4EA3-8E6E8D03001E5E66/OM2007R2_OperationsUsersGuide.docx
Sept 2009
R5.
Microsoft Download Center: Microsoft Information Worker Management Pack for Operations
Manager 2007:
http://www.microsoft.com/downloads/details.aspx?FamilyId=D898D5FE-1FF2-4C91-ABBE63ADC3BFA1C4&displaylang=en&displaylang=en
May 2008
R6.
Microsoft Download Center: Windows Client 2000/XP/Vista/Windows 7 Operating System

Management Pack for Operations Manager 2007:
http://www.microsoft.com/downloads/details.aspx?FamilyId=F55F1803-EAE6-4ED5-B2D29E1ADF98E325&displaylang=en&displaylang=en
Oct 2009
R7.
Operations Administrators Guide:
http://download.microsoft.com/download/B/F/D/BFDD0F66-1637-4EA3-8E6E8D03001E5E66/OM2007R2_OperationsAdministratorsGuide.docx
Sept 2009
R8.
Microsoft TechNet: System Center Operations Manager 2007 R2 Connectors:

http://technet.microsoft.com/en-gb/library/dd795265.aspx
R9.
Microsoft TechNet: Operations Manager 2007 R2 Supported Configurations:

http://technet.microsoft.com/library/bb309428.aspx
May 2009
R10.
Security Guide:
http://download.microsoft.com/download/B/F/D/BFDD0F66-1637-4EA3-8E6E8D03001E5E66/OM2007R2_SecurityGuide.docx
May 2009
R11.
Microsoft Blogs TechnNet: System Center Operations Manager: OPSMGR 2007 Database and Oct 2007
Data Warehouse Size Calculator:
http://blogs.technet.com/momteam/archive/2007/10/15/opsmgr-2007-database-and-datawarehouse-size-calculator.aspx
Table 22: References
Page 101

System Center Operations Manager 2007 R2 Guide For Healthcare Organizations PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

System Center Operations Manager 2007 R2 Guide For Healthcare Organizations PDF

Încărcat de

Drepturi de autor:

Formate disponibile

System Center Operations Manager 2007 R2

Design, Deployment and Operations Guide

Friday, 26 February 2010

The following diagram illustrates the different sections of this document:

Figure 1: MSF Process Model Phases and Document Structure

In the Welcome to the Microsoft

From System Configuration Check

In the Ready to Install screen, verify

Table 4: Installing SQL Server 2005

Select the Collation tab.

In the Database Engine

Select the Data Directories

In the Prerequisites Check

In the Management Group

In the SQL Server Database

In the Welcome to the System

In the End-User License

In the Product Registration

In the End-User License

In the Product Registration

In the Custom Setup screen,

In the Prerequisites Check

In the Customer Experience

In the Ready to Install the

Table 10: Installing the Operations Console

In the Welcome to Operations

In the End-User License

In the Product Registration

In the Prerequisites Check

In the Connect to Root

In the Connect to the

In the Destination Folder

In the Management Group

In the Management Group

On the Error Reporting tab,

On the Error Transmission

Managing Management Packs

PART I TERMS AND ABBREVIATIONS

Audit collection Service

Common User Interface

Domain Name System

Reporting Data Warehouse

End-User License Agreement

Fully Qualified Domain Name

Internet Information Services

Information Management & Technology

Microsoft Data Access Components

Microsoft XML Core Services

Network Address Translation

Root Management Server

Session Initiation Protocol

Server Message Block

Short Message Service

Simple Mail Transfer Protocol

Service Principal Name

Extensible Markup Language

Table 21: Terms and Abbreviations

Figure 2: Sequence for Planning System Center Operations Manager 2007

Planning Management Groups

This guidance focuses on two different deployment scenarios:

Deploying a Single Management Group on a Single Server

RMS, DB, RS, DW