Operations Manager 2007 Deployment Guide

Microsoft Corporation
Published: December, 2008

Author
Christopher Fox
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the companies, organizations, products, domain
names, e-mail addresses, logos, people, places, and events depicted in examples herein are
fictitious. No association with any real company, organization, product, domain name, e-mail
address, logo, person, place, or event is intended or should be inferred. Complying with all
applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of Microsoft
Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, and ActiveSync are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
All other trademarks are property of their respective owners.

Revision History

Release Date Changes

March 2007  Original release of this guide

July 2007  Updated procedures for clustering RMS

and bug fixes

August 2007  Security procedures fixes and minor

updates.

February 2008  Updated supported cluster configuration for

SP1
 Updated RMS clustering procedures for
SP1
 Updated certificate import and gateway
server deployment procedures for SP1
 Updated account planning for reporting and
RMS for SP1.
 Bug fixes
Release Date Changes

 Added documentation roadmap

October 2008  Updated maximum number of

recommended client agents for SP1

December 2008  Added description of and link to the

management pack authoring console
Contents
Roadmap for the Operations Manager 2007 Guides.....................................................................11

About the Operations Manager 2007 Deployment Guide.............................................................12

Operations Manager 2007 Deployment Scenarios.......................................................................12

In This Section........................................................................................................................... 12

About Operations Manager 2007 Deployment Scenarios.............................................................13

In This Section........................................................................................................................... 13
Server Role Compatibility....................................................................................................... 14
See Also.................................................................................................................................... 16

Single Server, Single Management Group Scenario.....................................................................17

Operations Manager 2007 Services..........................................................................................19
Operations Manager 2007 Server Roles...................................................................................19
Restrictions................................................................................................................................ 19
Gateway Server..................................................................................................................... 19
High Availability and Redundancy.......................................................................................... 20
Common Uses........................................................................................................................... 20
Ports Used................................................................................................................................. 20

Multiple Server, Single Management Group Scenario..................................................................20

Operations Manager 2007 Features..........................................................................................22
Operations Manager 2007 Server Roles...................................................................................22
Restrictions................................................................................................................................ 22
Installed Languages............................................................................................................... 23
Consolidated Views................................................................................................................ 23
Function................................................................................................................................. 23
Administrative or Other Business Needs................................................................................23
Common Uses........................................................................................................................... 23
Ports Used................................................................................................................................. 23

Connected Management Groups Scenario...................................................................................24

Operations Manager 2007 Services..........................................................................................25
Operations Manager 2007 Server Roles...................................................................................26
Restrictions................................................................................................................................ 26
Common Uses........................................................................................................................... 26
Ports Used................................................................................................................................. 26

Operations Manager 2007 Environmental Prerequisites...............................................................27

In This Section........................................................................................................................... 27
About Operations Manager 2007 Environmental Prerequisites....................................................27
See Also.................................................................................................................................... 28

Infrastructure................................................................................................................................. 28
Active Directory Domain Services............................................................................................. 28
Domain Functional Level........................................................................................................ 28
Forest Functional Level.......................................................................................................... 29
DNS........................................................................................................................................... 29

Security Considerations................................................................................................................ 29
Trust Boundaries....................................................................................................................... 30
Kerberos................................................................................................................................ 30
Certificates............................................................................................................................. 30
Certification Authority................................................................................................................. 30
Microsoft Certificate Services................................................................................................. 31
Accounts and Groups................................................................................................................ 31
Role-Based Security Accounts and Groups...........................................................................31
Notification Accounts and Groups.......................................................................................... 33
Service Accounts.................................................................................................................... 34
Run As Accounts.................................................................................................................... 34

Agent and Agentless Monitoring................................................................................................... 35

Clients with Agents Installed...................................................................................................... 35
Agents Inside a Trust Boundary............................................................................................. 35
Discovery............................................................................................................................ 35
Installation........................................................................................................................... 35
Ongoing Management........................................................................................................ 36
Agents Outside a Trust Boundary..........................................................................................36
Manually Installed Agents...................................................................................................... 37
Agentless Monitoring................................................................................................................. 37

Deploying Operations Manager 2007 Scenarios..........................................................................37

In This Section........................................................................................................................... 37
Before Deployment.................................................................................................................... 38

SQL Server 2005 for Operations Manager 2007...........................................................................38

Selecting a SQL Server 2005 Version.......................................................................................38
SQL Server 2005 Disk Subsystem Configuration......................................................................39
Best Practices........................................................................................................................ 39
SQL Server Version and Service Packs....................................................................................39
SQL Server 2005 Configuration................................................................................................. 40
Best Practices for SQL Server Configuration for OperationsManager Database...................40
SQL Server Broker Service.................................................................................................... 40

Deploying the Single Server, Single Management Group Scenario..............................................40

 Before You Start........................................................................................................................ 41
Installing SQL Server 2005........................................................................................................ 41
Installing Operations Manager 2007 Single Server Configuration.............................................44
Confirming the Health of the Management Group.....................................................................48

Deploying Reporting in the Single Server, Single Management Group Scenario..........................49

Installing Operations Manager 2007 Reporting Single Server Configuration.............................50
Confirming the Health of Reporting Services.............................................................................51

About Audit Collection Services (ACS) in Operations Manager 2007...........................................52

ACS Forwarders........................................................................................................................ 52
ACS Collector............................................................................................................................ 53
ACS Database........................................................................................................................... 53
See Also.................................................................................................................................... 54

ACS Security in Operations Manager 2007..................................................................................54

Limited Access to Audit Events.................................................................................................. 55
Limited Communication for ACS Forwarders.............................................................................55
ACS Forwarders Separated from the ACS Collector by a Firewall............................................55
See Also.................................................................................................................................... 55

Capacity Planning for ACS............................................................................................................ 55

ACS Collector Queue................................................................................................................ 56
ACS Collector Memory.............................................................................................................. 57
ACS Database Recommendations............................................................................................ 58
See Also.................................................................................................................................... 58

How to Deploy Audit Collection Services (ACS)...........................................................................59

Procedures................................................................................................................................ 59
See Also.................................................................................................................................... 60

How to Install an ACS Collector and Database.............................................................................60

Procedures................................................................................................................................ 60
See Also.................................................................................................................................... 62

How To Enable ACS Forwarders In Operations Manager 2007....................................................62

Procedures................................................................................................................................ 62
See Also.................................................................................................................................... 63

Deploying Client Monitoring in the Single Server, Single Management Group Scenario..............63
Customer Experience Improvement Program...........................................................................64
Agentless Exception Monitoring................................................................................................ 64
Client Configuration................................................................................................................... 65

Deploying the Operations Manager 2007 Management Pack Authoring Console.......................65

Deploying the Multiple Server, Single Management Group Scenario...........................................66
Before You Start........................................................................................................................ 66
High-Level SQL Cluster Install Guidance..................................................................................69
Installing Operations Manager 2007 Database Components in a SQL Server 2005 Cluster.....70
Installing the Operations Manager 2007 Operational Database and Data Warehouse
Components in a SQL Server 2005 Cluster........................................................................71
Using Log Shipping for the OperationsManager Database....................................................72
Deploying a Root Management Server on a Windows Cluster in Operations Manager 2007....72
Installing RMS........................................................................................................................ 77
Installing the Secondary Management Servers......................................................................79
Preparing RMS Cluster Resources........................................................................................79
Creating the RMS Cluster...................................................................................................... 81
Creating the Virtual RMS........................................................................................................ 81
Preparing an Inaccessible Management Server.....................................................................84
Testing the Cluster Installation................................................................................................... 85
Uninstalling Operations Manager 2007.....................................................................................85

Deploying Stand-Alone Management Servers in the Multiple Server, Single Management Group
Scenario.................................................................................................................................... 86
Before You Start........................................................................................................................ 87
Installing a Stand-Alone Management Server...........................................................................88
Troubleshooting Tips.............................................................................................................. 89

Deploying Reporting in the Multiple Server, Single Management Group Scenario.......................91

High-Level Installation Overview............................................................................................... 91
Installing Operations Manager Data Warehouse.......................................................................93
Installing Operations Manager Reporting on a Stand-Alone Server.......................................94
Uninstalling Operations Manager Reporting Services............................................................97

Deploying ACS in the Multiple Server, Single Management Group Scenario................................97

Before You Start........................................................................................................................ 98
Installing ACS on a Secondary Management Server.............................................................98

How to Deploy Operations Manager 2007 ACS Reporting...........................................................99

Before You Start...................................................................................................................... 100
Deploying ACS Reporting........................................................................................................ 100

Deploying Gateway Server in the Multiple Server, Single Management Group Scenario...........101
High-Level Procedure Overview.............................................................................................. 102
Before You Start...................................................................................................................... 102
Obtaining Computer Certificates from Microsoft Certificate Services...................................103
Distributing the [Link]............................103
Installing Operations Manager 2007 Gateway Server..........................................................103
Importing Certificates with the [Link] Tool.....................................................104
Registering the Gateway with the Management Group........................................................105
 Configuring Gateway Servers for Failover Between Management Servers.........................105
Description........................................................................................................................... 106
Code.................................................................................................................................... 106
Comments............................................................................................................................ 106

Deploying the Connected Management Groups Scenario..........................................................106

Before You Start...................................................................................................................... 107
Creating Connected Management Groups...........................................................................107
Providing Access to Connected Management Groups.........................................................108

Operations Manager 2007 Post-Deployment Tasks....................................................................109

Roadmap for the Operations Manager 2007
Guides
If you are new to Operations Manager 2007, you can use the following diagram to see the order
in which you should read the Operations Manager 2007 Guides. This diagram will be updated as
new guides become available.

11
About the Operations Manager 2007
Deployment Guide
This guide steps you through the deployment process for System Center Operations
Manager 2007. The guide includes the following:
 Descriptions of three possible deployment scenarios
 Environmental prerequisites for each scenario
 Deployment steps for each scenario
 Post-deployment tasks
Even though these scenarios are presented as discrete units, your implementation of Operations
Manager 2007 may consist of two or even all three types of deployments.
Before using this guide, you should complete the design process. For more information, see the
Operations Manager 2007 Design Guide

Operations Manager 2007 Deployment

Scenarios

In This Section
About Operations Manager 2007 Deployment Scenarios
Describes the three general deployment scenarios.

Single Server, Single Management Group Scenario

Describes the single server, single management group scenario where all components
are installed on one server.

Multiple Server, Single Management Group Scenario

Describes the multiple server, single management group scenario that can offer
distribution of server roles, redundancy, and high availability.

Connected Management Groups Scenario

Describes the connected multiple management groups scenario.

12
About Operations Manager 2007 Deployment
Scenarios
All Operations Manager 2007 individual management group deployments will either be an "all-in-
one" installation, where all components are loaded on a single server, or a distributed installation,
where Operations Manager server roles are distributed across servers. Any number of these can
then be combined together to form an overall Operations Manager 2007 infrastructure that
consists of multiple management groups. These management groups can then relate to each
other in a hierarchical fashion as your business needs dictate. This guide classifies these
deployment configurations into three scenarios:
 Single server, single management group: the all-in-one installation
 Multiple server, single management group: roles distributed across servers
 Connected management groups: multiple management groups working together to provide
monitoring, alerting, and troubleshooting services
This section of the Operations Manager 2007 Deployment guide describes these scenarios, how
they are most commonly used, and any restrictions that may exist with any individual scenario.

In This Section
Single Server, Single Management Group Scenario
Provides an overview of the Operations Manager 2007 services offered, configuration
steps, and an example of this "all-in-one" deployment configuration.

Multiple Server, Single Management Group Scenario

Provides an overview of the Operations Manager 2007 services offered, server roles
used, and an example of this deployment configuration.

Connected Management Groups Scenario

Provides an overview of the Operations Manager 2007 services offered, server roles
used, and an example of this deployment configuration.

This guide helps you in the deployment of Operations Manager 2007. It does not assist in the
design process. Before you start deploying Operations Manager 2007, you should have
completed a design plan that includes a mapping of the following:
 Business and IT needs to Operations Manager 2007 features and functions.
 Operations Manager 2007 features to a server design that supports those features and
functions (a topology).

13
 Infrastructure services, such as security, directory, network, and storage, to support the
server design.
 Your company's monitoring, alerting, and troubleshooting processes to the set of Operations
Manager 2007 services that you plan to implement.
For complete guidance in developing an Operations Manager design plan, see the Operations
Manager 2007 Design Guide at [Link]

Server Role Compatibility

An Operations Manager 2007 management group can provide a multitude of services. These
services can be distributed to specific servers, thereby classifying a server into a specific role. Not
all server roles and services are typically deployed onto the same server. The following table lists
the compatibilities and dependencies and if the role can be installed on a failover cluster.

Server role Requirements and Can be placed in a failover

Compatibilities cluster

Operational database SQL Server 2005 SP1 or SP2. Yes, n+1 cluster
This role can be co-deployed
with all server roles in the Single
Server, Single Management
Group scenario (Gateway and
management server roles are
excluded); otherwise, it is most
commonly deployed as a stand-
alone or co-deployed with other
databases.

Audit Collection Services SQL Server 2005 SP1 or SP2. Yes, n+1 cluster
(ACS) database This role can be co-deployed
with all server roles in the Single
Server, Single Management
Group scenario (Gateway and
management server roles are
excluded); otherwise, it is most
commonly deployed in a stand-
alone configuration for
performance purposes.

Reporting Data Warehouse SQL Server 2005 SP1 or SP2. Yes, n+1 cluster
database This role can be co-deployed
with all server roles in the Single
Server, Single Management
Group scenario (Gateway and

14
Server role Requirements and Can be placed in a failover
Compatibilities cluster

management server roles are

excluded); otherwise, it is most
commonly deployed with the
Reporting database or in a
stand-alone configuration for
performance purposes.

Reporting database Dedicated SQL Server SQL Reporting Services

Reporting Services instance; not database only. n+1 cluster
on a domain controller. This role
can be co-deployed with all
server roles in the Single Server,
Single Management Group
scenario (Gateway and
management server roles are
excluded); otherwise, it is most
commonly deployed with the
Reporting Data Warehouse
database or in a stand-alone
configuration for performance
purposes.

Root Management Server Not compatible with Yes, n+1 cluster, no other
(RMS) management server or gateway roles on the cluster
server role. This role is co-
deployed with all server roles in
the Single Server, Single
Management Group scenario
(Gateway and management
server roles are excluded);
otherwise, it is most commonly
deployed into a n+1 active-
passive-passive cluster with no
other roles on the cluster.

management server (MS) Not compatible with Root No

management server. This role is
not deployed in the Single
Server, Single management
server scenario. It is most
commonly deployed in a stand-
alone configuration,

15
Server role Requirements and Can be placed in a failover
Compatibilities cluster

Administrator console Windows Server 2003 or N/A

Windows XP or Windows Vista.

ACS collector This role is co-deployed with all No

other server roles in the Single
Server, Single Management
Group scenario (Gateway and
management server roles are
excluded); otherwise, it must be
co-deployed with the
management server role. It can
be combined with gateway
server and audit database.

gateway server Can be co-deployed with ACS No

collector only, cannot be
combined with management
server; must be a domain
member.

Web console server Windows Server 2003. N/A

Agent Automatically deployed to Root N/A

Management Server and
management server in a
management group. Deployable
to all other roles in
managemement group.

Note
For more information about SQL Reporting Services database installed on a cluster, see
[Link]

See Also
[Link]

16
Single Server, Single Management Group
Scenario
The single server, single management group scenario combines all the management group roles
that can coexist onto a single instance of the Microsoft® Windows Server® 2003 or Microsoft ®
Windows Server ® 2008 operating system running as a member server in an Active Directory®
domain. This instance can be on dedicated hardware or on a virtual computer. The Operations
console can be deployed to computers other than the single server, and the Web console is
accessed via a browser. Agents are then typically deployed to a limited number of devices
depending on the capacity of the server that Operations Manager is deployed on.

17
18
Operations Manager 2007 Services
Due to the coexistence limitations defined in the About Operations Manager 2007 Deployment
Scenarios, not all Operations Manager 2007 services and server roles are available. The single
server, single management group configuration supports the following services:
 Monitoring and alerting
 Reporting (available in the Operations console but not in the Web console)
 Audit collection
 Agentless exception management
 Data (accessed by using the Web console and the Operations console)

Operations Manager 2007 Server Roles

The single server, single management group configuration combines these server roles:
 Audit Collection Services (ACS) collector
 ACS database
 ACS forwarder
 Operational database
 Operations console
 Reporting Data Warehouse database
 Reporting database
 Reporting server
 Root management server
 Web console server
 CommandShell

Restrictions
The single server, single management group configuration is the easiest to deploy, but there are
limitations to its capabilities and therefore limitations to what it is commonly used for.

Gateway Server
This configuration does not include the gateway server role. Because of this, all monitored
devices must be in the same Active Directory domain as the management server or you must use
certificates on both the managed computer and the management server to provide for mutual
authentication.

19
High Availability and Redundancy
The single server, single Management group resides on a single set of hardware. This
configuration precludes use of Windows Clustering technologies. Similarly, this configuration
supports only one instance of each server role and therefore cannot support agent failover
between Management servers.

Common Uses
This configuration is most commonly used for evaluation, testing, and Management Pack
development purposes, usually in nonproduction or preproduction environments. Single server,
single management group configurations generally lack the robustness and performance to
support anything but the smallest production loads.

Ports Used
In this configuration, you need to make sure that network ports are opened for communication
between the agents and the management server, between the Operations console and the
management server, and between the Web console and the management server. All other inter-
service communication occurs on the management server itself. The ports are as follows:
 Operations console to Root management server: TCP 5724
 Operations console to Reporting Server: TCP 80
 Web console to Web console server: TCP 51908, 443
 Agent to Root Management Server: TCP 5723
 ACS forwarder to ACS collector: TCP 51909
 Agentless management: occurs over remote procedure call
For a complete listing of ports used, the direction of the communication, and if the ports can be
configured, see Operations Manager 2007 Supported Configurations at
[Link]

Multiple Server, Single Management Group

Scenario
This type of management group installation will form the foundation of 99 percent of Operations
Manager deployments. It allows for the distribution of server roles and services across multiple
servers to allow for scalability and for the use of Windows failover clustering and Operations
Manager-specific failover configurations. It can include all Operations Manager server roles and
supports the monitoring of devices across trust boundaries through the use of the gateway server.
The following diagram presents one possible option for the multiple server, single management
group topology.

20
Important
This example shows the ACS, Data Warehouse and OperationsManager databases all
on the same SQL Server 2005 cluster. This supported configuration is recommended for
light usage scenarios or for very high end hardware that can scale to the desired load. If
you don't use very high end hardware and a normal to heavy load is anticipated, then

21
 distribute the databases across several SQL Server 2005 installations for better
performance.

Operations Manager 2007 Features

This configuration supports all Operations Manager features:
 Monitoring and alerting, targeted for between 500 and 6,000 agents
 Monitoring across trust boundaries
 Reporting
 Audit collection
 Agentless exception management
 Agent failover between management servers
 Gateway failover between management servers
 Windows Clustering high availability for database and root management server roles

Operations Manager 2007 Server Roles

This configuration supports all Operations Manager server roles:
 Audit Collection Services (ACS) collector
 ACS database
 ACS forwarder (on agent-managed devices)
 gateway server
 management server
 Operational database
 Operations console
 SQL Server 2005 Reporting database
 Reporting Data Warehouse database
 root management server
 Web console server

Restrictions
Single management group configurations do not support partitioning. Partitioning is the
separation of management group services across multiple management groups. In Operations
Manager 2007, you may want to create multiple management groups for the following reasons.

22
Installed Languages
Operations Manager 2007 management groups support only one installed language. If the overall
IT environment that you need to monitor has more than one installed language, a separate
management group will be needed per language.

Consolidated Views
Even the largest multiple server, single management group implementation will not be appropriate
in every instance. This will lead you to implement multiple management groups, which will split
your monitoring and alerting data between management groups. To provide a single, consolidated
view of your environment, data from multiple management groups can be consolidated and
viewed in another management group. For more information, see the Operations Manager 2007
Design Guide at [Link] .

Function
You may need to have separate groups as needed according to function, such as preproduction
for testing management packs and new servers, and production for monitoring daily business
processes.

Administrative or Other Business Needs

Your company may have other administrative, security, or business needs that require complete
separation of monitoring data and administrative teams, which will mandate additional
management groups.

Common Uses
Multiple server, single management groups are most commonly used to monitor very large
preproduction environments and large production environments that
 Span trust boundaries between domains and workgroups.
 Have multiple network environments segmented by firewalls.
 Have a need for high availability.
 Must have a scalable monitoring solution.

Ports Used
This configuration supports full distribution of server roles among servers in the management
group as well as monitoring of devices across network boundaries, resulting in a longer list of
ports that need to be available for communications. For more information, see Operations
Manager 2007 Supported Configurations ([Link]

23
Connected Management Groups Scenario
This deployment scenario is comprised of multiple management groups, each of which can be of
the single or multiple server configurations type. This deployment scenario is exceptionally
flexible and is mostly used to provide monitoring, alerting, and reporting services in complex
environments.

24
Operations Manager 2007 Services
In addition to the services offered by the multiple server, single management group, this
configuration offers the ability to view and interact with data from multiple management groups in

25
a single Operators console. The management group in which the consolidated view is available is
called the local management group, and those that contribute their data to the consolidated view
are called the connected management groups. They relate to each other in a hierarchical fashion,
with connected groups in the bottom tier and the local group in the top tier. The connected groups
are in a peer-to-peer relationship with each other. Each connected group has no visibility or
interaction with the other connected groups; the visibility is strictly from the local group into the
connected group.
Connecting management groups offers these additional services:
 Consolidated monitoring and alerting for greater than 6,000 agents
 Consolidated monitoring across trust boundaries

Operations Manager 2007 Server Roles

This configuration supports all Operations Manager server roles and makes use of the Operations
Manager Connector Framework to enable bidirectional communication between the connected
groups and local groups.

Restrictions
 Operations Manager 2007 does not support communication of data between peer
management groups.
 Only the local to connected hierarchy configuration is supported. Multiple tiers, where a
management group would be both a local group and a connected group, are not supported.

Common Uses
This deployment scenario is used when business or IT needs mandate management group
partitioning along with the need to have a consolidated view of all monitored activity and
consolidated management of that data.

Ports Used
In addition to all of the communications channels used in the multiple server, single management
group configuration, this deployment requires communication between the root management
server of the local group and the root management server of the connected group over TCP
5724. For a complete list of ports used by Operations Manager 2007 and their configurability, see
Operations Manager 2007 Supported Configurations ([Link]
LinkId=86539).

26
Operations Manager 2007 Environmental
Prerequisites
This section covers the infrastructure that you need to have in place and other factors to consider
before you run the Operations Manager 2007 Prerequisite Viewer tool when setting up your
infrastructure.

In This Section
About Operations Manager 2007 Environmental Prerequisites
Describes the environmental prerequisites that must be satisfied prior to installing
Operations Manager 2007 components.

Infrastructure
Describes prerequisites and issues that you need to be aware of before initiating your
Operations Manager 2007 installation.

Security Considerations
Describes high-level security factors that need to be addressed.

Agent and Agentless Monitoring

Describes the environmental prerequisites for deploying agents to monitor devices and
for deploying agentless monitoring.

About Operations Manager 2007

Environmental Prerequisites
There are two sets of prerequisites that must be satisfied prior to installing any of the Operations
Manager 2007 components. One set consists of those items that the Prerequisite Viewer checks
for during setup. The Prerequisite Viewer is targeted at the server that setup is running on and
determines if the server has the necessary components and configuration to host whatever role
you have chosen.
The other set consists of those items that are outside the scope of the Prerequisite Viewer, such
as the Active Directory domain or forest functional level, or the availability of a certification
authority (CA) to issue the certificates that are necessary for deploying agents and gateway
27
servers across trust boundaries. This section addresses this second set of prerequisites, which
are much broader in scope, as they apply to the whole environment that Operations Manager will
be functioning in, rather than those that are verified by the Prerequisite Viewer during setup.
To ensure that Operations Manager deploys smoothly and functions as expected, the
environment that it will run in must be properly prepared. Because environmental changes impact
more than Operations Manager, ensure that you exercise due caution before making sweeping
changes. The prerequisites are presented in a unified format with scenario-specific items called
out.
For more information about design and environmental decisions, see the Operations
Manager 2007 Design Guide at [Link]

See Also
Security Considerations
Operations Manager 2007 Supported Configurations

Infrastructure
This section addresses prerequisites and issues involving Active Directory Domain Services
(AD DS) and Domain Name System (DNS) that you need to be aware of before initiating your
Operations Manager 2007 installation.

Active Directory Domain Services

Operations Manager 2007 relies on AD DS for a number of services, including definition of
security principles, rights assignment, authentication, and authorization. Operations Manager
queries AD DS when performing computer and service discovery and can use AD DS for storing
and distributing agent configuration information. For Operations Manager to function properly,
AD DS and its supporting service, DNS, need to be healthy and at certain minimum configuration
levels.

Domain Functional Level

Windows Server 2003 Active Directory domains can operate in one of four different levels of
functionality. These levels are distinguished by the version of the Windows Server operating
system that is permitted on the domain controllers present in the domain. Each of the following
levels provides increasingly powerful features:
 Windows 2000 mixed: Windows NT® Server 4.0, Windows® 2000 Server, and Windows
Server 2003 domain controllers are allowed. This is the default domain functional level for
Windows Server 2003 domains.

28
 Windows 2000 native: Windows 2000 Server and Windows Server 2003 domain controllers
are allowed.
 Windows Server 2003 interim: Windows Server 2003 and Windows NT Server 4.0 domain
controllers are allowed. This is only seen when upgrading a Windows NT Server 4.0 domain
to be the first Windows Server 2003 domain in an Active Directory forest.
 Windows Server 2003: Only Windows Server 2003 domain controllers are allowed.
Operations Manager 2007 requires that the domain functional level be Windows 2000 native,
Windows Server 2003 interim, or Windows Server 2003. The domain functional level of Windows
Server 2008 is also supported. For Operations Manager to function properly, you must check the
domain functional level and raise it to at least Windows 2000 native. To do this, see Raise the
Domain Functional Level ([Link]

Note
Ensure that you exercise due caution prior to raising a domain's functional level because
it cannot be reversed, and if there are any down-level domain controllers, their function
will be impacted.

Forest Functional Level

The forest functional level is similar to the domain functional level in that it sets a minimum
domain controller operating system level across the whole forest. After it is set, domain controllers
with down-level operating systems from lower functional levels cannot be introduced into the
forest. Operations Manager does not have a forest functional level requirement; however, if the
forest functional level is left at the default Windows 2000 level, there may be domains in your
forest that won't meet the minimum domain functional level requirement.

DNS
DNS must be installed and in a healthy state to support AD DS. Beyond the reliance of
Operations Manager on AD DS, there are no specific DNS requirements.

Security Considerations
Most of the work in preparing the environment for Operations Manager 2007 goes into security-
related tasks. This section covers those tasks at a cursory level; for detailed coverage, see the
Operations Manager 2007 Security Guide at. [Link]
Preparing the security-related tasks involves the following:
 Understanding, planning, and preparing for monitoring across trust boundaries.
 Planning and preparing the service accounts, user accounts, and security groups that you will
need.
 Understanding and preparing the network ports as required by your design.

29
Trust Boundaries
Active Directory domains form the basic unit of a Kerberos trust boundary as seen by Operations
Manager. This boundary is automatically expanded to other domains in the same name space
(the same Active Directory tree), and between domains that are in different Active Directory trees
but still in the same Active Directory forest via transitive trusts. The trust boundary can be further
expanded between domains in different Active Directory forests through the use of across forest
trusts.

Kerberos
The Kerberos authentication protocol, which is supported by Windows 2000 domain controllers
and above, can only occur within a trust boundary. Kerberos authentication is the mechanism
used to perform the Operations Manager 2007 agent/server mutual authentication. Agent/server
mutual authentication is mandated in Operations Manager 2007 for all agent/server
communication.
An Operations Manager management group does have the ability to perform discovery and
monitoring outside of the Kerberos trust boundary that it is in. However, because the default
authentication protocol for Windows-based computers that are not joined to an Active Directory
domain is NTLM, another mechanism must be used to support mutual authentication. This is
done through the exchange of certificates between agents and servers.

Certificates
When Operations Manager 2007 communication needs to occur across trust boundaries, such as
when a server that you want to monitor lies in a different, untrusted, Active Directory domain than
the management group that is performing the monitoring, certificates can be used to satisfy the
mutual authentication requirement. Through manual configuration, certificates can be obtained
and associated with the computers and the Operations Manager services running on them. When
a service that needs to communicate with a service on a different computer starts and attempts to
authenticate, the certificates will be exchanged and mutual authentication completed.

Important
The certificates used for this purpose must ultimately trust the same root certification
authority (CA).
For more information about how to obtain and make use of certificates for mutual authentication,
see Deploying Gateway Server in the Multiple Server, Single Management Group Scenario.

Certification Authority
To get the necessary certificates, you will need access to a certification authority (CA). This can
be either Microsoft Certificate Services or a third-party certification service such as VeriSign.

30
Microsoft Certificate Services
There are four types of Microsoft CAs:
 Enterprise root
 Enterprise subordinate
 Stand-alone root
 Stand-alone subordinate
 Both enterprise types of CAs require Active Directory Domain Services; stand-alone CAs do
not. Either type of CA can issue the necessary certificates for agent/server mutual
authentication across trust boundaries.
Customarily, a CA infrastructure consists of a root CA that signs its own certificates and certifies
itself and one or more subordinate CAs, which are certified by the root. The subordinate CA
servers are the ones that a service certificate requests, while the root is taken offline and held for
safekeeping. For more information about designing certificates, see Enterprise Design for
Certificate Services ([Link] and the topic "Certificates" in
the Operations Manager 2007 Help.

Accounts and Groups

Over the lifetime of your Operations Manager deployment, you will potentially need many
accounts and security groups. During Operations Manager setup, you are only prompted for four.
You need to consider additional accounts when planning out role-based security assignments,
notifications, and alternate credentials to run processes. For guidance on planning role-based
security assignments, see the Operations Manager 2007 Design Guide at
[Link]

Role-Based Security Accounts and Groups

Operations Manager controls access to monitored groups, tasks, views, and administrative
functions through the assignment of user accounts to roles. A role in Operations Manager is the
combination of a profile type (operator, advanced operator, administrator) and a scope (what data
the role has access to). Typically, Active Directory security groups are assigned to roles, and then
individual accounts are assigned to those groups. Prior to deploying, plan out Active Directory
security groups that can be added to these and any custom-created roles so that you can then
add individual user accounts to the security groups.
Operations Manager provides the following role definitions out-of-the-box.

Role name Profile type Profile description Role scope

Operations Manager Administrator Has full privileges to Full access to all

Administrators: Operations Manager; Operations Manager
Created at setup; no scoping of the data, services,
cannot be deleted; Administrator profile is administrative, and

31
Role name Profile type Profile description Role scope

must contain one or supported authoring tools

more global groups

Operations Manager Advanced Operator Has limited change Access to all groups,
Advanced Operators: access to Operations views, and tasks
Created at setup; Manager currently present and
globally scoped; cannot configuration; ability to those imported in the
be deleted create overrides to future
rules; monitors for
targets or groups of
targets within the
configured scope

Operations Manager Author Has ability to create, Access to all groups,

Authors: Created at edit, and delete tasks, views, and tasks
setup; globally scoped; rules, monitors, and currently present and
cannot be deleted views within those imported in the
configured scope future

Operations Manager Operator Has ability to interact Access to all groups,

Operators: Created at with alerts, run tasks, views, and tasks
setup; globally scoped; and access views currently present and
cannot be deleted according to those imported in the
configured scope future

Operations Manager Read-Only Operator Has ability to view Access to all groups
Read-Only Operators: alerts and access and views currently
Created at setup; views according to present and those
globally scoped; cannot configured scope imported in the future
be deleted

Operations Manager Report Operator Has ability to view Globally scoped

Report Operators: reports according to
Created at setup; configured scope
globally scoped

Operations Manager Report Security Enables integration of No scope

Report Security Administrator SQL Reporting
Administrators: Services security with
Integrates SQL Operations Manager
Reporting Services roles
security with
Operations Manager
user roles; gives

32
Role name Profile type Profile description Role scope

Operations Manager
administrators the
ability to control access
to reports; cannot be
scoped

You can add Active Directory security groups or individual accounts to any of these predefined
roles. If you do, those individuals will be able to exercise the given role privileges across the
scoped objects.

Note
The predefined roles are globally scoped, giving them access to all groups, views, and
tasks (except for Report Security Administrator).
Operations Manager also allows you to create custom roles based on the Operator, Read-Only
Operator, Author, and Advanced Operator profiles. When you create the role, you can further
narrow the scope of groups, tasks, and views that the role can access. For example, you can
create a role entitled "Exchange Operator" and narrow the scope to only Exchange-related
groups, views, and tasks. User accounts assigned to this role will only be able to run Operator-
level actions on Exchange-related objects.

Important
Make sure that you create a domain security group for the Operations Manager
Administrators role; this is required to be in place during the first setup run for a
management group.

Notification Accounts and Groups

Individuals in your company that will interact with Operations Manager frequently, such as an
Exchange administrator who has been assigned to the Exchange Operator role, need a way to
discover new alerts. This can be done by either watching the Operations console for new alerts or
by Operations Manager informing them about the alert via supported communications channels.
Operations Manager supports notifications through e-mail, instant messaging, Short Message
Service, or pager messages. Notifications on what the role needs to know go out to recipients
that you specify in Operations Manager. An Operations Manager recipient is merely an object that
has a valid address to receive the notification, such as an SMTP address for e-mail notifications.
Therefore, it is logical to combine role assignment with notification group membership via an e-
mail-enabled security group. For example, create an Exchange Administrators security group and
populate it with individuals that have the knowledge and permissions to fix things in Exchange.
Assign this security group to a custom-created Exchange Administrator role so they have access
to the data and are e-mail-enabled. Then, create a recipient by using the SMTP address of the e-
mail-enabled security group.

33
Service Accounts
At the time of deployment, you need to have the following service accounts ready. If you use
domain accounts and your domain Group Policy object (GPO) has the default password
expiration policy set as required, you will either have to change the passwords on the service
accounts according to the schedule, or use low maintenance system accounts, or configure the
accounts so that the passwords never expire.

Account name Requested when Used for Low maintenance High security

management management Collecting data Local system Low privilege

server Action server setup from providers, domain account
Account running
responses

SDK and management Writing to Local system Low privilege

Configuration server setup operational domain account
Service Account database,
running services

Local Discovery and Installing agents Domain or local Domain or local

Administrator push agent install administrator administrator
Account for target account account
devices

Agent Action Discovery and Gathering Local system Low privilege

Account push agent install information and domain account
running
responses on
managed
computers

Data Warehouse Reporting Server Writing to the Low privilege Low privilege
Write Action setup Reporting Data domain account domain account
Account Warehouse
database

Data Reader Reporting Server Querying SQL Low privilege Low privilege
Account setup Reporting domain account domain account
Services
database

Run As Accounts
Agents on monitored computers can run tasks, modules, and monitors on demand as well as in
response to predefined conditions. By default, all tasks run by using the Agent Action account

34
credentials. In some cases, the Agent Action account may have insufficient rights and privileges
to run a given action on the computer. Operations Manager supports the running of tasks by
agents in the context of an alternate set of credentials called a Run As Account. A Run As
Account is an object that is created in Operations Manager, just like a recipient is, and maps to an
Active Directory user account. A Run As Profile is then used that maps the Run As Account to a
specific computer. When a rule, task, or monitor that has been associated with a Run As Profile at
the development time of a management pack needs to run on the targeted computer, it does so
by using the specified Run As Account.
Out-of-the-box, Operations Manager provides a number of Run As Accounts and Run As Profiles,
and you can create additional ones as necessary. You may also choose to modify the Active
Directory credentials that a Run As Account is associated with. This will require planning,
creating, and maintaining additional Active Directory credentials for this purpose. You should treat
these accounts as service accounts with respect to password expiration, Active Directory Domain
Services, location, and security.
You will need to work with management pack authors as they develop requests for Run As
Accounts.
For more information, see the Operations Manager 2007 Security Guide.

Agent and Agentless Monitoring

This section covers the environmental prerequisites for devices that will have agents installed and
devices that will be monitored in an agentless fashion.

Clients with Agents Installed

The three main activities involved with agent administration are discovery of target devices,
deployment or installation of agents to those devices, and ongoing management of the agents.
Agents that lie outside a trust boundary require a few more prerequisites than agents that lie
inside a trust boundary.

Agents Inside a Trust Boundary

Discovery
Discovery requires that the TCP 135 (RPC), RPC range, and TCP 445 (SMB) ports remain open
and that the SMB service is enabled.

Installation
After a target device has been discovered, an agent can be deployed to it. Agent installation
requires the following:

35
 Opening Remote procedure call (RPC) ports beginning with endpoint mapper TCP 135 and
the Server Message Block (SMB) port TCP/UDP 445.
 Enabling the File and Printer Sharing for Microsoft Networks and the Client for Microsoft
Networks services (this ensures that the SMB port is active).
 If enabled, Windows Firewall Group Policy settings for Allow remote administration
exception and Allow file and printer sharing exception must be set to Allow unsolicited
incoming messages from: to the IP address and subnets for the primary and secondary
management servers for the agent. For more information, see How to Configure the Windows
Firewall to Enable Management of Windows-Based Computers from the Operations Manager
2007 Operations Console.
 An account that has local administrator rights on the target computer.
 Windows Installer 3.1. To install, see article 893803 in the Microsoft Knowledge Base
([Link]
 Microsoft Core XML services (MSXML) 6 on the Operations Manager product installation
media in the \msxml subdirectory.

Note
Push agent installation will install MSXML 6 on the targeted device if it is not there.

Ongoing Management
Ongoing management of an agent requires that the TCP 135 (RPC), RPC range, and TCP 445
(SMB) ports remain open and that the SMB service remains enabled.

Agents Outside a Trust Boundary

For agents that lie outside the trust boundary of the management servers, the environmental
prerequisites are the same as for those that lie inside a trust boundary, with some additions.
Because the device is going to have an installed agent, the software, service, and port
requirements remain the same. However, because there is no underlying infrastructure to support
Kerberos authentication, certificates must be used on both sides of the connection.
To simplify the cross trust boundaryr configuration, you can install an Operations Manager
gateway server in the same trust boundary as the devices that you will monitor. The gateway
server acts as a proxy so that all communication between the management server and agents is
routed through the gateway server. This communication is done over a single port, TCP 5723,
and requires certificates on the management server and the gateway server. In addition, the
gateway server performs discovery and installation, and relays ongoing administration traffic on
behalf of the management server to the agents. The use of gateway servers also reduces the
volume of network traffic and is therefore useful in low bandwidth conditions
For more information about gateway server configuration, see Deploying Gateway Server in the
Multiple Server, Single Management Group Scenario.

36
Manually Installed Agents
Discovery is not performed for manually installed agents, so there are fewer requirements.

Agentless Monitoring
Agentless monitoring of devices is performed by either a management server or by another
device that does have an agent, called a proxy agent. An agentless managed device must not be
separated from its management server or proxy agent by a firewall because monitoring is
performed over RPC. The action account of the agent that is performing the monitoring must
have local administrative rights on the device that is being monitored.

Deploying Operations Manager 2007

Scenarios
This section provides detailed procedures for installing each of the deployment scenarios.

In This Section
SQL Server 2005 for Operations Manager 2007
Describes the SQL Server 2005 items to be aware of prior to deploying Operations
Manager 2007.

Deploying the Single Server, Single Management Group Scenario

Provides step-by-step instructions for installing this scenario.

Deploying the Multiple Server, Single Management Group Scenario

Provides step-by-step instructions for installing this scenario.

Deploying the Connected Management Groups Scenario

Provides step-by-step instructions for installing this scenario.

The goal of this section is to teach you how to deploy Operations Manager in the three described
scenarios. The deployment scenarios are intended as common examples of Operations
Manager 2007 infrastructures which can be modified and molded as your business and IT needs
dictate. Each deployment scenario builds on the previous one and is broad enough so that with
very little modification, you will be able to install Operations Manager to a wide variety of
environments with varying business needs.

37
Before Deployment
 Have a design plan in hand. For more information about developing a design plan, see the
Operations Manager 2007 Design Guide at, [Link]
 If this is to be anything but a temporary lab testing installation, ensure that you have installed
and tested the deployment in a lab setting.
 Read all background material or attend training on Operations Manager 2007. For more
information, see the Operations Manager 2007 Design Guide at,
[Link]

SQL Server 2005 for Operations Manager

2007
This section provides information about Microsoft SQL Server 2005 as it is used to support
Operations Manager 2007. It is not intended as a complete guide to planning, installing,
configuring, and tuning SQL Server 2005; for that information, see the Microsoft SQL Server 2005
Online Books. For minimum hardware configuration, see Operations Manager 2007 Supported
Configurations ([Link]

Selecting a SQL Server 2005 Version

Microsoft SQL Server 2005 comes in five editions: Express, Workgroup, Standard, Enterprise,
and Developer. Of these five, you should consider the Standard and Enterprise Editions to
support Operations Manager 2007.
 Express Edition: This edition has a maximum database size of 4 GB and is intended for
desktop development with very small datasets. Express Edition makes a suitable
replacement for Microsoft Access databases.

Note
Using a database for Operations Manager 2007 that has been upgraded from SQL
Server 2005 Express Edition is not supported and fails the Prerequisite Viewer
checks.
 Workgroup Edition: This edition is only available for 32-bit operating systems and supports
only 3 GB of memory. It is intended for departmental and branch office applications.
 Developer Edition: This edition is not licensed for production use.
 Standard Edition: This edition supports 32-bit and 64-bit hardware, up to four multicore
processors, memory limited by operating system, unlimited database size and support of
failover clustering, log shipping, and database mirroring. It is intended for large datasets and
production loads.
 Enterprise Edition: This edition supports 32-bit and 64-bit hardware, unlimited number of
multicore processors, memory limited by operating system, unlimited database size, failover
38
 clustering for two or more nodes, log shipping, and database mirroring. It is intended for the
largest and most demanding online transaction processing (OLTP) environments, data
analysis, and data warehousing systems. When planning for ACS, SQL Server 2005
Enterprise Edition is the preferred version.

SQL Server 2005 Disk Subsystem Configuration

The Operations Manager 2007 operational database, named OperationsManager by default, is
the single chokepoint when it comes to performance. The faster the SQL Server 2005 disk
subsystem can perform, the better Operations Manager performs. For production systems,
consider RAID 10.
 RAID 0: This disk configuration creates stripes across the disks that are dedicated to it, and it
delivers high performance but no fault tolerance.
 RAID 1: This disk configuration creates a redundant copy of the selected disk, also known as
disk mirroring. It provides fault tolerance, but the write performance is degraded.
 RAID 5: This disk configuration uses data striping, but it includes parity information for fault
tolerance. Multiple heads provide better performance for read and write operations.
 RAID 10: This disk configuration is also known as RAID 1+0 and provides data striping
without parity for performance and mirroring for fault tolerance. It is the most expensive of the
common disk configurations. This configuration provides better write performance than RAID
5.

Best Practices
 Do not place database data files in the same drive as the operating system.
 Place transaction logs and database data files on separate drives.
 Place the TempDB database on its own drive.
For more information about designing SQL Server 2005 installations, see the SQL Server 2005
Online Books and Physical Database Storage Design ([Link]
LinkId=86441).

SQL Server Version and Service Packs

Ensure that the database server offering of the SQL Database Services, Reporting Services, and
Workstation components all have SQL Server 2005 SP1 or higher installed.
If you are working with SQL Server 2005 SP1, you must also ensure that hotfixes are installed for
each of the SQL Server components to be supported by the server. To install the hotfixes, see the
Cumulative Hotfix Package (build 2153) for SQL Server 2005 ([Link]
LinkId=78950).
These hotfixes are already included in SQL Server 2005 SP2.

39
SQL Server 2005 Configuration
The SQL Server 2005 instance that is used to support Operations Manager 2007 must use
Windows Authentication mode.
The databases that you will be most concerned with in Operations Manager 2007 are:
 OperationsManager: This database holds the operational data and the configuration settings
for its management group.
 OperationsManagerAC: This database is created when the Audit Collection Service is
installed. It is optimized for Windows Security Event Log events.
 OperationsManagerDW: This database is created when Operations Manager 2007 Reporting
service is installed and the Data Warehouse option is selected. It holds the same operational
data as the OperationsManager database, but reformats it for long-term storage and
optimizes it for report generation.
 ReportServer: This database is installed when SQL Server 2005 Reporting Services is
installed and is used to house report definitions.
 ReportServerTempDB: This temporary database is used during report generation.
To provide the best recovery experience, configure the OperationsManager database to run in the
Full Recovery model. You can set this in SQL Server Management Studio, in the properties of a
database. Select the Options object on the Database Properties page, and on the right side,
select Full in the Recovery model list.

Best Practices for SQL Server Configuration for

OperationsManager Database
Because each environment is different, Microsoft recommends that you thoroughly evaluate all
configuration settings as they relate to your environment.
 Database Growth Configuration: The OperationsManager database is the single bottleneck
for all operational data, and its performance has a dramatic impact on the performance of
Operations Manager as a whole. Keeping this database relatively small ensures faster
operations.

SQL Server Broker Service

Operations Manager Discovery, in addition to other workflows, is dependent on SQL Server 2005
Service Broker, which must remain enabled for Operations Manager 2007 to be fully functional.

Deploying the Single Server, Single

Management Group Scenario
This topic provides the procedures to deploy the single server, single management group
scenario. This procedure assumes that Windows PowerShell has been installed but that SQL
40
Server 2005 has not been installed yet. For a complete list of required software and supported
configurations, see Operations Manager 2007 Supported Configurations at
[Link]

Before You Start

To prepare accounts and groups in Active Directory
1. In Active Directory Users and Computers, create five accounts: the Management Server
Action account, the SDK and Configuration Service account, the Data Reader account,
the Data Warehouse Write Action account, and an Operations Manager Administrator
account (for example, OpsMgrAdmin). These can all be domain user accounts. No
special privileges are required at the domain level.

Note
If you have a domain password expiration Group Policy in place and you do not
want to change these service account passwords on the same schedule, select
Password never expires for the individual accounts.
2. In Active Directory Domain Services, create a Global Security group for the Operations
Manager Administrators. If you plan to use of any of the other Operations Manager 2007
roles, create e-mail-enabled Global Security groups for those also.
3. Add the Operations Manager Administrator Account to the Operations Manager
Administrators Global Security group.

To prepare accounts and groups on the Operations Manager server

1. On the server that you are going to install Operations Manager on, log on with an account
that has local administrator rights.
2. In the Computer Management tool, under Local Users and Groups, open the
Administrators group and add the Operations Manager Administrators Global Security
group that you created in step 2 of "To prepare accounts and groups in Active Directory."
Also add the accounts that you created to use as the Management Server Action
account, the SDK and Config account, the Data Reader account, and the Data
Warehouse Write Action account.
3. Log off and then log back on with the Operations Manager Administrator account (for
example, OpsMgrAdmin).

Installing SQL Server 2005

This procedure assumes that SQL Server 2005 Enterprise Edition SP1 with hotfixes or SP2 is
used.

41
To install SQL Server 2005 to support the single server, single management group
scenario
1. On the installation media, start [Link] to start the SQL Server 2005 installation.
2. On the End User License Agreement page, click I accept the licensing terms and
conditions, and then click Next.
3. Allow the Installing Prerequisites operation to finish, and then click Next.
4. The Welcome to the Microsoft SQL Server Installation Wizard page appears. Click
Next to continue.
5. The Microsoft SQL Server Installation runs a System Configuration Check. Fix any
issues that are found, and click Next.
6. On the Registration Information page, enter the appropriate Name and Company
values, and then click Next.
7. On the Components to Install page, select the SQL Server Database Services, the
Reporting Services, and the Workstation components, Books Online and
development tools options. If you want to change the installation directory, click
Advanced and enter the appropriate installation directory; otherwise, click Next.

Note
SQL Server Reporting Services as it is used to support Operations
Manager 2007 cannot have any additional Reporting Services applications
installed on the same instance of SQL Server. Also, SQL Server 2005 Reporting
Services must be configured to run in Native mode, not Sharepoint Integrated
mode.
8. On the Instance Name page, accept the Default instance selection, and then click
Next.
9. On the Service Account page, select the Use the built-in System account, and then
accept the default Local system account in the drop-down box. Accept the default
selections for SQL Server and Reporting Services in the Start services at the end of
setup box, and then click Next.
10. On the Authentication Mode page, accept the default of Windows Authentication
Mode, and then click Next.
11. On the Collation Settings page, accept the default SQL collations (used for
compatibility with previous version of SQL Server) selection and the default
Dictionary order, case -insensitive, for use with 1252 Character Set values, and then
click Next.
12. On the Report Server Installation Options page accept the default Install the default
configuration selection, and then click Next.

Note
If these radio buttons are unavailable, check to ensure that Reporting Services
has not been installed before and that no IIS Virtual Directories, named Reports

42
 and ReportServer, exist. If they do, delete them and go back to the Report
Server Installation Options page. If the Install but do not configure the
server option is selected, you must use the Reporting Services Configuration
tool to complete the configuration.
13. On the Ready to Install page, review the installation options and either click Back to
change them or Install to start the installation.
14. After the installation is complete, the Completing Microsoft SQL Server 2005 Setup
page appears. Save the Summary Log of the installation if you want to retain a record of
the installation activities, and then click Finish. You can examine the logs later in the \
Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log\[Link] file
15. Complete the SQL Server 2005 installation by applying SQL Server 2005 SP1 and the
KB918222 hotfixes or SP2 for SQL Server, Reporting Services and Workstation and
tools.
16. Confirm the existence of the ReportServer and ReportServerTempDB databases in
SQL Server Management Studio. Click Start, point to Programs, point to Microsoft SQL
Server 2005, point SQL Server Management Studio, and connect to the default
database instance. Open the Databases node and look for the two Reporting Services
databases.
17. Confirm the correct configuration of SQL Server 2005 Reporting Services. Click Start,
point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools,
and click Reporting Services Configuration to launch the Configure Report Server
tool. Connect to the instance that you installed Reporting Services on.
18. In the left hand pane, ensure that Server Status, Report Server Virtual Directory,
Report Manager Virtual Directory, Windows Service Identity, Database Setup, and
Initialization are all not in a Not configured state, any other state is acceptable. If they
are not, select the item and follow the configuration instructions in the right hand pane.
19. Confirm that the SQL Server reporting Services service is running. Click Start, point to
Settings, and select Control Panel. In the Control Panel, select Administrative Tools,
and open Services.
20. In the Name column, find the SQL Server Reporting Services instance service and
confirm that its status reads Started and that its Startup Type is reads Automatic.
21. Confirm that the Report Server Web site is up by browsing to
[Link] You should see a page with
the <servername>/ReportServer<$INSTANCE> and the text Microsoft SQL Server
Reporting Services Version #.##.####.## where the # is the version number of your
SQL Server installation.
22. Confirm the correct configuration of Report Manager Web site by opening Internet
Explorer and browsing to [Link]
23. Once you are in the Report Manager Web site, click New Folder to create a new folder.
Enter a name and description and click OK. Ensure that the new created folder is visible
on the Report Manager Web site.

43
For more information on how to verify a SQL Server Reporting Services installation see:
[Link]

Installing Operations Manager 2007 Single Server

Configuration
To use the Prerequisite Viewer for single server configuration
1. On the server that you are going to install Operations Manager on, log on with the
Operations Manager Administrator account.
2. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup on the Start page.
3. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.
4. In the Components box, select all options, which are Operational Database, Server,
Console, Power Shell, Web Console, Reporting, and Data Warehouse, and then click
Check.

Note
When all components are selected, the Prerequisite Viewer checks for the
presence of Windows Server 2003 SP1, SQL Server 2005 SP1 or SP2, SQL
Server Reporting Services SP1, MDAC version 2.80.1022.0 or later, .NET
Framework version 2.0, .NET Framework 3.0 components, and Windows
PowerShell. It then checks to ensure that the WWW service is running and set to
automatic startup mode.

Note
The results are displayed at the bottom of the Prerequisite Viewer. If there are
any deficiencies, they are marked either as a Warning or as Failed. Warnings
can be ignored at the risk of degraded performance; Failed prerequisites must
be fixed before the installation can proceed. You can close the Prerequisite
Viewer, fix the items, and rerun the Prerequisite Viewer checks as many times
as necessary until a Pass evaluation is achieved on all items. You can click any
row for more details as well as remediation steps.

Note
Multiple Operations consoles can be installed in a Management Group. Each one
accesses the RMS. If one of the servers that the Operations console component
has been installed on fails, you can install additional consoles on other servers or
workstations and use them to connect to the RMS and then perform
management functions. In this scenario, you can install Operations consoles on
client machines if you wish.
5. When you are finished with the Prerequisite Viewer, click Close.

44
To install the server components
1. Log on to the server that you are going to install Operations Manager on with an account
that has Operations Manager administrator rights and local administrator rights.

Note
It is necessary to use an account with local administrator rights because the
setup process creates services, folders structures, SQL databases, SQL logins
and SQL roles.
2. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup Wizard to the Start page.
3. Under the Install heading, click Install Operations Manager 2007 to start the
Operations Manager 2007 Setup Wizard.
4. On the Setup Wizard Welcome page, click Next.
5. On the End User License Agreement page, select the I accept the terms in the
license agreement option, and then click Next.
6. On the Product Registration page enter the appropriate values in the User Name and
Organization fields. Enter your 25-digit CD Key, and then click Next.
7. On the Custom Setup page, ensure that all the components are set to This component,
and all dependent components, will be installed on the local disk drive. If you want
to change the installation directory, click Browse and enter the appropriate path and
folder name, and then click Next.
8. On the Management Group Configuration page, in the Management Group name:
box, enter the appropriate management group name.

Note
After the management group name is set, it cannot be changed. The
Management Group name cannot contain the following characters:, ( ) ^ ~ : ; . ! ?
" , ' ` @ # % \ / * + = $ | & [ ] <>{}, and it cannot have a leading or trailing space. It
is recommended that the Management Group name be unique within your
organization if you plan to connect Operations Manager 2007 Management
Groups.
9. In the Configure MOM Administrators box, click Browse to select the Global Security
group for Operations Manager Administrators; then click Next.
10. On the SQL Server Database Instance page, select the instance of the SQL Server
database from the drop-down list if necessary. This drop-down list is populated with the
SQL Server database instance name that was created in SQL Server 2005 step 8. This
name should be the name of the server you are installing on. Click Next.

Note
The SQL Server Port must be the same as the SQL installation, by default 1433.
Entering the wrong port will cause the installation to fail and roll back. If you
encounter this failure, simply repeat the installation using the correct port.

45
11. On the Database and Log File Options page, you can accept the default value of
OperationsManager for the SQL Database Name, or you can change it. It is
recommended that you accept the default. Enter the appropriate value in the Database
size field or accept the default 1000-MB.

Note
For information about initial database sizing, see the System Center Capacity
Planner (SCCP) Guide on TechNet ([Link]
LinkId=118307).
12. The Data file location and Log file location boxes indicate where the
OperationsManager database and log files will be installed. The default location is the
installation directory of SQL Server on the computer. If you have created additional
partitions or drives to separate the database files and the log files, click Advanced to
enter the appropriate drive, path, and folder names, and then click Next.
13. On the Management Server Action Account page, accept the default Domain or Local
Computer Account option, enter the credentials of the Management Server Action
account, and then click Next.

Note
For more information about what accounts to use for the Management Server
Action Account and the SDK and Config account, see the Operations Manager
Security Guide at ([Link] By using a
domain-based account, it will be much easier to perform discovery and push
agent installation later on than it will be if you chose the Local System account.
For more information about agent installation, see Agent and Agentless
Monitoring.
14. On the SDK and Config Service Account page, select the Domain or Local Account
option and enter the credentials for the SDK and Config service account, and then click
Next.

Note
Because all components are being installed on one server, you can select the
Local System account option if you want to. But by using a domain-based
account, you are preparing for the addition of other management servers to the
management group at a later date.

Note
If you receive an Account Verification Error when you click Next, it is most likely
that you mistyped the credentials or that the SDK and Config service account
was not added to the local Administrators group.
15. On the Web Console Authentication Configuration page, accept the default selection
of Use Windows Authentication (Recommended) if the Web Console will be primarily
consumed from Intranet-based clients. Select Use Forms Authentication if you plan to

46
 offer the Web Console to Internet usage, and then click Next.

Note
Selecting Forms Authentication alone does not make the Web console available
to Internet-based users. Additional steps and infrastructure are required.
16. On the Operations Manager Error Reports page, select the Do you want to send
error reports to Microsoft? option if you want to, and then click Next.

Note
Your selection here has no effect on the deployment or functionality of the
Agentless Exception Management feature in Operations Manager 2007.
17. On the Customer Experience Improvement Program page, indicate whether you want
to join this program, and then click Next.
18. On the Ready to Install the Program page, click Install when you are ready for the
installation to proceed.
19. On the Completing the System Center Operations Manager 2007 Setup Wizard
page, accept the default option to Back up Encryption Key and to Start the Console, and
then click Finish. The Operations Console will launch as will the Encryption Key
Backup or Restore Wizard.

Note
If Setup fails, it will provide you with a value to search on and a link to open the
setup log.

Note
If you uninstall the server components, the Operations Manager event log
remains following uninstall, by design. This also causes the Operations Manager
installation folder to remain (default: %ProgramFiles%\Microsoft System Center
Operations Manager 2007).

This starts the Operations console for the first time. If the console does not start successfully and
you are prompted for credentials, it is most likely that you are not logged on with an account that
is a member of the Operations Manager Administrators security group.

To use the Encryption Key Backup or Restore Wizard to backup the RMS encryption key
1. On the Introduction page, click Next>.
2. On the Backup or Restore? page, select the Backup the Encryption Key button and
click Next>.
3. On the Provide a Location page, specify a valid path to back up the encryption key file
to and then click Next>.
4. On the Provide a Password page, enter an eight-character or longer password to
secure the encryption key file, and then click Next> to start the backup process.
5. You should now see the Secure Storage Backup Complete page. Click Finish.

47
Confirming the Health of the Management Group
The core Management Server roles of Root Management Server, Operational Database,
Operations console, PowerShell, and Web console have now been installed. Reporting and Audit
Collection Services are installed separately. For more information about Reporting and Audit
Collection Services, see Deploying Reporting in the Single Server, Single Management Group
Scenario and How to Deploy Audit Collection Services (ACS). Prior to deploying agents and
importing management packs, it is necessary to confirm the health state of the management
group.

To confirm the health of the Management Group

1. In the opened Operations console, in the Monitoring view, expand the Operations
Manager folder, and then expand the Management Server folder.
2. In the Management Server folder, select the Management Server State view. Confirm
that the Root Management Server health state is listed as Healthy. This particular view
tracks the health state of all the roles that are installed on the management server. This is
shown by entries for the Collection Management Server state (ACS) and the Gateway
Management Server state.
3. Open SQL Server Management Studio, expand the Databases folder, and confirm the
existence of the OperationsManager database and that it is online.
4. Expand the OperationsManager database, expand the Security folder, and select the
Users folder. You should see that the Management Server Action account and the SDK
and Config domain accounts are present.
5. Right-click the Management Server Action account and display its properties. In the
Database role membership box, confirm that the Management Server Action account is
a member of the db_datareader, db_datawriter and dbmodule_users SQL roles.
6. Right-click the SDK and Config service account and display its properties. In the
Database role membership box, confirm that the SDK and Config service account is a
member of the configsvc_users, db_datareader, db_datawriter, db_ddladmin and
sdk_users SQL roles.

To confirm the health of the Web console

 Click Start, point to All Programs, point to System Center Operations Manager 2007,
and select Web Console. Confirm that the Web Console starts successfully.

Note
The default URL for the Web console is [Link] This can be
in the Operations console, Administration view, Settings object, Web Address
properties. For more information, see the Operations Manager 2007 Online Help.

48
Deploying Reporting in the Single Server,
Single Management Group Scenario
In this scenario, the SQL Reporting Services database and the Operations Manager Data
Warehouse database are installed in the same instance of SQL Server as the
OperationsManager database, and eventually the Audit Collection Services (ACS) database.
During this installation, you are prompted for two accounts: the Data Warehouse Write account
and the Data Reader account. These accounts are created as domain user accounts and added
to the local Administrators group on the target server.
 Data Warehouse Write account: This account is assigned write permissions on the Data
Warehouse database and read permissions on the OperationsManager database.

Note
Before you perform this procedure, be sure that the account you plan to use for the
Data Warehouse Write Account has SQL Login rights and is an Administrator on the
computers hosting both the Operations Manager database and Reporting data
warehouse. Otherwise, setup fails and all changes are rolled back, which might leave
SQL Reporting Services in an inoperable state.
 Data Reader account: This account is used to define what user SQL Reporting Services uses
to run queries against the Operations Manager Reporting Data Warehouse. This account is
also used for the SQL Reporting Services IIS application pool account to connect to the RMS.
The account that you use to run the Operations Manager 2007 Reporting installation must be a
member of the following groups and roles.
 Local Administrator – this is required by the Operations Manager 2007 Reporting installation
and for configuring SQL Server Reporting Services.
 Operations Manager Administrator role – this is required for configuring reporting roles and
creating reporting instances.
 SQL SysAdmin for the OperationsManager database – this is required for configuring
dwsynch_users role.
 SQL SysAdmin for the Data Warehouse database – this is required for configuring
OpsMgrWriter and OpsMgrReader roles.

Installing Operations Manager 2007 Reporting

Single Server Configuration
To install Operations Manager 2007 Reporting
1. Ensure that SQL Server Reporting services has been correctly installed and configured.
Refer to the ”Installing SQL Server 2005” procedure in the previous section.
2. On the server that you are going to install Operations Manager on, log on with the

49
 Operations Manager Administrator account.
3. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup Wizard on the Start page.
4. Under the Install heading, click the Install Operations Manager 2007 Reporting link.
5. On the Welcome page, click Next.
6. On the End-User License Agreement page, select the I accept the terms in the
license agreement option, and then click Next.
7. On the Product Registration page, enter the appropriate value in the User Name and
Organization fields, and then click Next.
8. On the Custom Setup page, ensure that the Data Warehouse and Reporting Server
components are set to This component, and all dependent components, will be
installed on the local disk drive, and then click Next.

Note
If you specify a custom name for the Data Warehouse database, be sure not to
include a '-' character. The database installation will fail if a '-' character is
included in the name.
9. On the Connect to the Root Management Server page, enter the name of the first
server in the management group. In this case, it is the server that you are installing
Operations Manager on. Click Next.
10. On the SQL Server Database Instance page, select the SQL Server database instance
from the drop-down list if necessary. This drop-down list is populated with the SQL Server
database instance name that was created when you installed SQL 2005 and should be
the name of the server that you are installing on. Accept the SQL Server Port default
(1433) or modify it if you have configured SQL to use a different port. Click Next.
11. On the Database and Log File Options page, you can accept the default value of
OperationsManagerDW for the SQL Database Name, or you can change it. It is
recommended that you accept the default value. Enter the appropriate value in the
Database size field or accept the default 1000-MB.

Note
If you choose to use custom directories for the OperationsManagerDW data and
log files, you must create these custom directories prior to starting the setup
process for the OperationsManagerDW

Note
For information about initial database sizing, see the System Center Capacity
Planner (SCCP) Guide on TechNet ([Link]
LinkId=118307).
12. The Data file location and Log file location boxes indicate where the
OperationsManager database and log files will be installed. The default is the installation
directory of SQL Server on the computer. If you have created additional partitions or

50
 drives to allow the separation of the database files and the log files, click Advanced to
enter the appropriate drive, path and folder names. Click Next.
13. On the SQL Server Reporting Services Instance page, select the Reporting Services
server instance name from the drop-down list. In this case, the server name should
already be selected. Click Next.

Note
Installing Operations Manager 2007 Reporting Services integrates the security of
the SQL Reporting Services instance with the Operations Manager role-based
security. Do not install any other Reporting Services applications in this same
instance of SQL Server.
14. On the Data Warehouse Write Account page, enter the Data Write account credentials,
and then click Next.
15. On the Data Reader Account page, enter the Data Reader account credentials, and
then click Next.
16. On the Operational Data Reports page, indicate whether you want to send data reports
to Microsoft or not, and then click Next.
17. On the Ready to Install the Program page, click Install when you are ready for the
installation to proceed.
18. After setup completes, you should see the Completing the Operations Manager
Reporting Components Setup Wizard page. Click Finish.

Confirming the Health of Reporting Services

Operations Manager Reports are accessed in the Operations console, in the Reporting view. After
initial deployment, it takes up to 30 minutes for reports to appear.

To confirm the health of Operations Manager Reports

1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role for the Operations Manager 2007 management group.
2. In the Operations console, click the Reporting button..
3. Click Microsoft ODR Report Library, and then double-click any of the reports listed; by
default, you should see the management group, management packs and Most
Common Alerts reports. The selected report will then generate and display in a new
window.

Note
Selecting the management packs report is particularly useful at this point
because it provides you with a full inventory of the management packs that have
been installed on your server.
4. Close the report window.

51
About Audit Collection Services (ACS) in
Operations Manager 2007
In Operations Manager 2007, Audit Collection Services (ACS) provides a means to collect
records generated by an audit policy and store them in a centralized database. By default, when
an audit policy is implemented on a Microsoft Windows computer, that computer automatically
saves all events generated by the audit policy to its local Security log. This is true for Windows
workstations as well as servers. In organizations that have strict security requirements, audit
policies can quickly generate large volumes of events.
Using ACS, organizations can consolidate individual Security logs into a centrally managed
database and can filter and analyze events using the data analysis and reporting tools provided
by Microsoft SQL Server. With ACS, only a user who has specifically been given the right to
access the ACS database can run queries and create reports on the collected data.
In Operations Manager 2007, the deployment of ACS involves the following components:
 ACS forwarders
 ACS collector
 ACS database

ACS Forwarders
The service that runs on ACS forwarders is included in the Operations Manager agent. By default,
this service is installed but not enabled when the Operations Manager agent is installed. You can
enable this service for multiple agent computers at once using the Enable Audit Collection task.
After you enable this service, all security events are sent to the ACS collector in addition to the
local Security log.

ACS Collector
The ACS collector receives and processes events from ACS forwarders and then sends this data
to the ACS database. This processing includes disassembling the data so that it can be spread
across several tables within the ACS database, minimizing data redundancy, and also applying
filters so that unnecessary events are not added to the ACS database.
The number of ACS forwarders that can be supported by a single ACS collector and ACS
database can vary, depending on the number of events that your audit policy generates, the role
of the computers that the ACS forwarders monitor (such as domain controller versus member
server), the level of activities on the computer, and the hardware on which the ACS collector and
ACS database run. If your environment contains too many ACS forwarders for a single ACS

52
collector, you can install more than one ACS collector. Each ACS collector must have its own ACS
database.
An ACS Collector must be installed on computers running Windows Server 2003 and later. An
ACS collector must have a minimum of 1 gigabyte (GB) of RAM, with 2 GB recommended. Also, it
must have at least a 1.8 gigahertz (GHz) processor, with a 2.8 GHz processor recommended and
10 GB of hard disk space available, at a minimum, with 50 GB recommended. The computer you
select as an ACS collector must be an Operations Manager 2007 Management Server and for
security reasons, it must also be a member of an Active Directory domain.
On each computer on which you plan to install the ACS collector, you must download and install
the latest version of the Microsoft Data Access Components (MDAC) from the Microsoft Web site.
To learn more about MDAC, see "Learning Microsoft Data Access Components (MDAC)" at
[Link]

ACS Database
The ACS database is the central repository for events that are generated by an audit policy within
an ACS deployment. The ACS database can be located on the same computer as the ACS
collector, but for best performance, each should be installed on a dedicated server.
The server that hosts the ACS database must have Microsoft SQL Server 2005. You can choose
an existing or new installation of SQL Server 2005. The Enterprise edition of SQL Server 2005 is
recommended because of the stress of daily ACS database maintenance.
If you use SQL Server standard edition, the database must pause during daily maintenance
operations. This may cause the ACS collector queue to fill with requests from ACS forwarders. A
full ACS collector queue then causes ACS forwarders to be disconnected from the ACS collector.
Disconnected ACS forwarders reconnect after the database maintenance is complete and the
queue backlog is then processed. To ensure no audit events are lost allocate a sufficient amount
of hard disk space for the local security log on all ACS forwarder.
SQL Server 2005 enterprise edition can continue to service ACS forwarder requests, although at
a lower performance level, during daily maintenance operations. For more information on the
ACS collector queue and ACS forwarder disconnection see ACS Capacity Planning and
Monitoring ACS Performance.
The ACS database should run on a computer that has a minimum of 1 GB of RAM, with 2 GB
recommended. Also, it must have at least a 1.8 GHz processor, with a 2.8 GHz processor
recommended and 20 GB of hard disk space available, at a minimum, with 100 GB
recommended. If your SQL Server has more than 2 GB of memory some additional configuration
steps are needed. For more information and the steps needed, see "How to configure SQL
Server to use more than 2 GB of physical memory" at [Link]
LinkId=74153.

See Also
ACS [Link]

53
ACS Capacity Planning
ACS Security in Operations Manager 2007
How to Deploy Audit Collection Services (ACS)
How to Install an ACS Collector and Database
How To Enable ACS Forwarders In Operations Manager 2007
How to Remove ACS
Monitoring ACS Performance

ACS Security in Operations Manager 2007

In Operations Manager 2007, Audit Collection Services (ACS) requires mutual authentication
between the ACS collector and each ACS forwarder. By default, Windows authentication, which
uses the Kerberos protocol, is used for this authentication. After authentication is complete, all
transmissions between ACS forwarders and the ACS collector are encrypted. You do not need to
enable additional encryption between ACS forwarders and the ACS collector unless they belong
to different Active Directory forests that have no established trusts.
By default, data is not encrypted between the ACS collector and the ACS database. If your
organization requires a higher level of security, you can use Secure Sockets Layer (SSL) or
Transport Layer Security (TLS) to encrypt all communication between these components. To
enable SSL encryption between the ACS database and the ACS collector, you need to install a
certificate on both the database server and the computer hosting the ACS Collector service. After
these certificates are installed, configure the SQL client on the ACS collector to force encryption.
For more information about installing certificates and enabling SSL or TLS, see SSL and TLS in
"Windows Server 2003" at [Link] and "Obtaining and
installing server certificates" at [Link] For a list of the
steps to force encryption on a SQL client, see [Link]

Limited Access to Audit Events

Audit events that are written to a local Security log can be accessed by the local administrator,
but audit events that are handled by ACS, by default, do not allow users (even users with
administrative rights) to access audit events in the ACS database. If you need to separate the role
of an administrator from the role of a user who views and queries the ACS database, you can
create a group for database auditors and then assign that group the necessary permissions to
access the audit database. For step-by-step instructions, see How to Deploy Audit Collection
Services (ACS).

54
Limited Communication for ACS Forwarders
Configuration changes to the ACS forwarder are not allowed locally, even from user accounts that
have the rights of an administrator. All configuration changes to an ACS forwarder must come
from the ACS collector. For additional security, after the ACS forwarder authenticates with the
ACS collector, it closes the inbound TCP port used by ACS so that only outgoing communication
is allowed. The ACS collector must terminate and then reestablish a communication channel to
make any configuration changes to an ACS forwarder.

ACS Forwarders Separated from the ACS

Collector by a Firewall
Because of the limited communication between an ACS forwarder and an ACS collector you only
need to open the inbound TCP port 51909 on a firewall to enable an ACS forwarder, separated
from your network by a firewall, to reach the ACS collector.

See Also
About Audit Collection Services (ACS) in Operations Manager 2007
Audit Collection Services (ACS)
How to Deploy Audit Collection Services (ACS)

Capacity Planning for ACS

Audit policies can generate a large amount of data. In Operations Manager 2007, for better
performance, you can change settings on the Audit Collection Services (ACS) collector to adjust
for the actual auditing load. The queue that the ACS collector uses to store events that are ready
to be written to the ACS database has a considerable impact on the ability of ACS to handle a
surge in the amount of generated security events. Balancing the capacity of this queue along with
maintaining the correct amount of RAM on the ACS collector can improve the performance of
ACS.

ACS Collector Queue

The ACS collector queue is used to store events after they are received from ACS forwarders but
before they are sent to the ACS database. The number of events in the queue increases during
periods of high audit traffic or when the ACS database is not available to accept new events, such
as during database purging. Three registry values control how the ACS collector reacts when this
queue is approaching maximum capacity.

55
The following table lists each registry entry and its default value. All registry entries in the table
are located in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AdtServer\
Parameters key of the registry.

Entry Name Default Value Description

MaximumQueueLength 0x40000 The maximum number of events

that can queue in memory while
waiting for the database. On
average, each queue entry
consumes 512 bytes of memory.

BackOffThreshold 75 How full the ACS collector queue

can become before the ACS
collector denies new connections
from ACS forwarders. This value
is expressed as a percentage of
MaximumQueueLength.

DisconnectThreshold 90 How full the ACS collector queue

can become before the ACS
collector begins disconnecting
ACS forwarders. This value is
expressed as a percentage of
MaximumQueueLength. ACS
forwarders with the lowest priority
value are disconnected first.

You might want to adjust the value of one or more of the preceding registry entries, depending on
your environment. For best results, you should consider how a value change of one entry will
affect the rest of the entries. For example, the value of BackOffThreshold should always be less
than DisconnectThreshold, allowing the ACS collector to gracefully degrade performance when
the ACS database cannot keep up with demand.

ACS Collector Memory

Memory on the ACS collector is used for caching ACS events that need to be written to the ACS
database. The amount of memory needed by an ACS collector can vary depending on the
number of ACS forwarders connected and the number of events generated by your audit policy.
You can use the following formula, based on expected traffic, to calculate whether more memory
is needed for better ACS performance:
Recommended Memory = (M x .5)+(50 x N)+(S x .5)+(P x .1)
The formula variables are defined in the following table.

56
Variable Definition Registry Key Entry Name

M Maximum number HKEY_LOCAL_MACHINE\ MaxQueueLength

of events queued SYSTEM\CurrentControlSet\
in memory on the
Services\AdtServer\Parameters
ACS collector

N Number of No registry setting NA

forwarders
connected to the
ACS collector

S ACS uses the HKEY_LOCAL_MACHINE\ StringCacheSize

string cache for SYSTEM\CurrentControlSet\
previously
Services\AdtServer\
inserted strings,
Parameters
such as event
parameters, to
avoid
unnecessary
queries to the
dtString tables in
the ACS
database.
Size of the string
cache on the ACS
collector,
expressed by the
maximum number
of entries the
cache can hold.
On average, each
queue entry
consumes 512
bytes of memory.
This cache is
used for event
record data.

P Size of the HKEY_LOCAL_MACHINE\ PrincipalCacheSize

principal cache on SYSTEM\CurrentControlSet\
the ACS collector,
Services\AdtServer\Parameters
expressed as the
maximum number
of entries the

57
Variable Definition Registry Key Entry Name

cache can hold.

This cache is
used for data that
pertains to the
user and
computer
accounts that
have access to
ACS components.

ACS Database Recommendations

When ACS is operating normally, the queue length should seldom reach the BackOffThreshold
value. If the queue length frequently reaches this threshold, either you have more events than
your database can handle or your database hardware should be upgraded.
To reduce the number of events written to the ACS database, you can change your audit policy to
reduce the number of generated events or use filters, applied at the ACS collector, to discard
unnecessary events and keep them out of the ACS database. You can also reduce the number of
ACS forwarders that send events to the ACS database by deploying an additional ACS collector
and database so that fewer ACS forwarders are serviced by each ACS collector.
For more information about filters, see the \SetQuery section of ACS Administration. For more
information on the number of ACS forwarders that an ACS collector can support, see About Audit
Collection Services (ACS) in Operations Manager 2007.

See Also
About Audit Collection Services (ACS) in Operations Manager 2007
ACS Administration
Audit Collection Services (ACS)

How to Deploy Audit Collection Services

(ACS)
The following procedure provides the general steps needed for a successful deployment of the
Operations Manager 2007 Audit Collection Services (ACS) components within your organization.

58
 Note
To uninstall Operations Manager 2007 from the Management Server that functions as
your ACS Collector, you must first uninstall ACS.
See About Audit Collection Services (ACS) in Operations Manager 2007 for more information on
minimum and recommended system requirements for ACS.

Procedures
To deploy Audit Collection Services
1. Plan an audit policy for your organization. For more information on setting up an audit
policy, see Windows Server 2003 Auditing at [Link]
LinkId=74154.
2. Plan your ACS server deployment. This includes deciding which server will act as the
ACS database and which Operations Manager 2007 Management Server will act as the
ACS collector. Ensure that the computers selected for these roles meet the minimum
system requirements. See About Audit Collection Services (ACS) in Operations Manager
2007 for more information about the components of ACS and the system requirements
for each.
3. Plan which Operations Manager agents will be ACS forwarders. All computers that you
want to collect security events from must be ACS forwarders.
4. Install and configure prerequisites for ACS components.
5. (Optional) Separate administrator and auditor roles by doing the following:
a. Create a local group just for users who access and run reports on the data in the
ACS database. For step-by-step instructions for creating a local group, see the To
create a group account in Active Directory section of the "Creating user and group
accounts" topic at [Link]
b. Grant the newly created local group access to the SQL database by creating a new
SQL Login for the group and assigning that login the db_datareader permission. For
step-by-step instructions for creating a SQL Login, go to
[Link]
c. Add the user accounts of users who will act as auditors to the local group.
6. Deploy the ACS Database and ACS Collector(s). See How to Install an ACS Collector
and Database.
7. Run the Enable Audit Collection task to start the ACS Forwarder service on the ACS
forwarders. For more information, see How To Enable ACS Forwarders In Operations
Manager 2007.
8. Implement your audit policy within your organization.

59
See Also
About Audit Collection Services (ACS) in Operations Manager 2007
How To Enable ACS Forwarders In Operations Manager 2007
How to Install an ACS Collector and Database

How to Install an ACS Collector and

Database
Use the following procedures in Operations Manager 2007 to install an Audit Collection Services
(ACS) collector and database and to start the service for the ACS collector computer. Both
procedures are performed on the computer that is designated as your ACS collector.
The ACS database runs on Microsoft SQL Server 2005. The Audit Collection Services Collector
Setup wizard creates the ACS database on an existing installation of Microsoft SQL Server 2005.
To complete the installation procedure, you must be a member of the local Administrators group
on both the ACS collector and the ACS database computers as well as a database administrator
on the ACS database. As a best practice for security, consider using Run As to perform this
procedure.
For information about system requirements and best practices for performance, see About Audit
Collection Services (ACS) in Operations Manager 2007 and ACS Capacity Planning.

Procedures
To install an ACS collector and an ACS database
1. Insert the Operations Manager 2007 CD in the Management Server that you selected to
be the ACS collector.
2. On the root of the CD, double-click [Link]. In the Install section, click Install
Audit Collection Server. The Audit Collection Services Collector Setup wizard starts.
3. On the Welcome page, click Next.
4. On the License Agreement page, read the licensing terms and then click I accept the
agreement. Click Next.
5. On the Database Installation Options page, click Create a new database and then
click Next.
6. On the Data Source page, type a name that you want to use as the Open Database
Connectivity (ODBC) data source name for your ACS database in the Data Source
Name box. By default, this name is OpsMgrAC. Click Next.
7. On the Database page, if the database is on a separate server than the ACS collector,
click Remote Database Server and then type the computer name of the database server
that will host the database for this installation of ACS. Otherwise, click Database server
60
 running locally.
8. In the Database server instance name field, type the name of the database that will be
created for ACS. If you leave this field blank, the default name is used. In the Database
name field, the default database name of OperationsManagerAC is automatically
entered. You can select the text and type in a different name or leave the default name.
Click Next.

Note
To display a list of SQL Server Instances, click Start, point to Programs and
Microsoft SQL Server 2005, and then click SQL Server Management Studio
on the database computer. Under Server name, click Browse for more and
then expand Database Engine. All databases are listed as server name\
database name.
9. On the Database Authentication page, click to select one authentication method. If the
ACS collector and the ACS database are members of the same domain, you can select
Windows authentication; otherwise, select SQL authentication and then click Next.

Note
If you select SQL authentication and click Next, the Database Credentials
page displays. Enter the name of the user account that has access to the SQL
Server in the SQL login name box and the password for that account in the SQL
password box, and then click Next.
10. On the Database Creation Options page, click Use SQL Server's default data and log
file directories to use SQL Server's default folders. Otherwise, click Specify directories
and enter the full path, including drive letter, to the location you want for the ACS
database and log file, for example C:\Program Files\Microsoft SQL Server\MSSQL.1\
MSSQL\Data. Click Next.
11. On the Event Retention Schedule page, click Local hour of day to perform daily
database maintenance. Choose a time when there is the amount of expected security
events are low. During the database maintenance window, database performance will be
impacted. Type the number of days ACS should keep events in the ACS database before
the events are removed during database grooming in Number of days to retain events.
The default value is 14 days. Click Next.
12. On the ACS Stored Timestamp Format page, click to choose Local or Universal
Coordinated Time, formerly known to as Greenwich Mean Time, and then click Next
13. The Summary page displays a list of actions that the installation program will perform to
install ACS. Review the list, and then click Next to begin the installation.

Note
If a SQL server login dialog box displays and the database authentication is set
to Windows authentication, click the correct database and verify that the Use
Trusted Connection check box is checked. Otherwise click to remove the check

61
 and enter the SQL login name and password. Click OK.
14. When the installation is complete, click Finish.

See Also
About Audit Collection Services (ACS) in Operations Manager 2007
ACS Capacity Planning

How To Enable ACS Forwarders In

Operations Manager 2007
Depending on your auditing needs, you might have several hundred to thousands of computers
from which you want to collect audit events. By default, the service needed for an agent to be an
Audit Collection Services (ACS) forwarder is installed but not enabled when the Operations
Manager agent is installed. After you install the ACS collector and database you can then
remotely enable this service on multiple agents through the Operations Manager console by
running the Enable Audit Collection task.
This procedure should be run after the ACS collector and database are installed and can only be
run against computers that already have the Operations Manager agent installed. In addition, the
user account that runs this task must belong to the local Administrators group on each agent
computer.

Procedures
To enable audit collection on Operations Manager 2007 agents
1. Log on to the computer with an account that is a member of the Operations Manager
Administrators role for your Operations Manager 2007 Management Group. This account
must also have the rights of a local administrator on each agent computer that you want
to enable as an ACS forwarder.
2. In the Operations Console, click the Monitoring button.

Note
When you run the Operations Console on a computer that is not a Management
Server, the Connect To Server dialog box displays. In the Server name text
box, type the name of the Operations Manager 2007 Management Server that
you want the Operations Console to connect to.
3. In the Monitoring pane, expand Operations Manager, expand Agent, and then click
Agent Health State. This view has two panes, and the actions in this procedure are
performed in the right pane.

62
 4. In the details pane, click all agents that you want to enable as ACS forwarders. You can
make multiple selections by pressing CTRL or SHIFT.
5. In the Actions pane, under Health Service Tasks, click Enable Audit Collection. The
Run Task - Enable Audit Collection dialog box displays.
6. In the Task Parameters section, click Override. The Override Task Parameters dialog
box displays.
7. In the Override the task parameters with the new values section, click the
CollectorServer parameter; in the New Value column, type the FQDN of the ACS
collector; and then click Override.

Note
If you are enabling ACS on a gateway or management server and you do not
specify the CollectorServer parameter, the task will fail with a “Type Mismatch
Error.” To avoid this, provide a value for the override.
8. In the Task credentials section, click Other. In the User Name box, type the name of a
user account that belongs to the local Administrators group on the agent computers. In
the Password box, type the password for this user account. Click to expand the Domain
drop-down list to view the available domains, and then click the domain of the user
account.
9. Click Run Task. The Task Status dialog box displays tracking the progress of the task.
10. When the task completes successfully, click Close.

See Also
About Audit Collection Services (ACS) in Operations Manager 2007
How to Deploy Audit Collection Services (ACS)
How to Install an ACS Collector and Database

Deploying Client Monitoring in the Single

Server, Single Management Group Scenario
Client Monitoring in Operations Manager 2007 consists of two features and a group of client-
specific management packs. The features are the Customer Experience Improvement Program
(CEIP) and Agentless Exception Monitoring (AEM). Operations Manager 2007 also hosts
management packs specifically for monitoring Windows Vista™, Windows XP, Windows 2000,
and Microsoft Information Worker applications.
All Client Monitoring features are configured from the Operations Console. This section gives a
brief description of each of these features and any prerequisites to their deployment. For more
information about the implementation and configuration of these services, see the Operations

63
Manager 2007 Operations Guide and the topic "Client Monitoring" in the Operations
Manager 2007 Help.

Customer Experience Improvement Program

When the Customer Experience Improvement Program (CEIP) is active on a client or server, it
gathers information about how Microsoft products are used on that particular computer,
processes it, and sends it to Microsoft, where it is combined with other CEIP data for further
analysis. Examples of data collected are as follows:
 Configuration, such as the number of processors, the version of Windows used, or the
number of network connections.
 Performance and reliability, such as program responsiveness and the speed of data
transmission.
 Program use, such as most frequently used features and Help and Support center usage.
This data is used to help Microsoft solve problems and to improve the products and features that
customers use most often. This data does not contain any personally identifying information, and
although the data does include the IP address that is used to access the Internet, Microsoft does
not use this address. For more information about CEIP, see the Microsoft Customer Experience
Improvement Program ([Link]
Rather than having a large number of clients each reporting this data individually, you can have
your clients send the CEIP data to the Operations Manager management server as a central
collection point. The management server that hosts the CEIP service can then forward the data to
Microsoft. The communication of CEIP data from the clients to the management server can be
SSL secured, can use Windows Authentication, and can be directed over a configurable port; the
default is TCP 51907. CEIP is configured on the management server by using the Client
Monitoring Configuration Wizard.

Agentless Exception Monitoring

When an application error occurs or when an operating system stops responding, an error log is
generated. This can be in the form of a dump file (.dmp) or other encoded or plain text log file.
These logs contain valuable information that is used to determine the root cause of the problem.
Microsoft Online Crash Analysis ([Link] makes use of
these reports.
When Agentless Exception Monitoring (AEM) is enabled on a management server, clients can be
configured to send their error reports to the management server to be stored on a file share.

Note
If you choose to collect the error reports on the management server, be sure to allow for
the additional disk and performance overhead when you size your server. For more
information about Operations Manager capacity planning and sizing, see the System

64
 Center Capacity Planner (SCCP) Guide on TechNet ([Link]
LinkId=118307).
Operations Manager can then aggregate the data and provide views and reports for your use.
The management server also forwards the data to Microsoft rather than having all the clients
perform this individually. AEM is configured by using the Client Monitoring Configuration Wizard,
and it allows configuration of the following:
 The file share path
 Election to collect error reports from Windows Vista-based clients
 management server port for communication
 SSL encryption
 Windows Authentication
 The name of the organization to include in the reports

Client Configuration
If you elect to deploy either of these features in your organization, you must create a Group Policy
Administrative template to be applied to the appropriate computers. This template is generated by
the Client Monitoring Configuration Wizard and can be applied individually or through Active
Directory Domain Services. The default template name is the fully qualified domain name (FQDN)
of the server with the .adm extension.

Deploying the Operations Manager 2007

Management Pack Authoring Console
The Operations Manager 2007 authoring console is a stand-alone application that provides richer
management pack authoring functionality than what is provided by the Operations console
authoring space. Using the authoring console, you can create new management packs, view and
modify existing management packs, verify the integrity of management packs, and import and
export management packs to and from management groups. Before you install the authoring
console, see the prerequisites in the Operations Manager 2007 Supported Configurations
document at: [Link] The Operations Manager 2007
authoring console can be downloaded here: [Link] The
download is a self-extracting executable file

To install the Operations Manager 2007 Management Pack Authoring Console

1. Using the link in the preceding section, download the appropriate version (x86 or x64) of
the authoring console. You can either run the installation directly from the Web site or
choose to save the file. In this procedure, you save the file locally.
2. When the download has been completed, click Run to start the installation.

65
 3. Click OK on the Welcome page. This starts the WinZip Self-Extractor utility.
4. Click Unzip, and then click OK.
5. On the System Center Operations Manager Authoring Console Setup End User
License Agreement page, select the I accept the terms in the license agreement
option.
6. Click Next.
7. When the setup has been completed, select or clear the Start the Console option, and
click Finish.

Deploying the Multiple Server, Single

Management Group Scenario

Before You Start

To provide high availability for the OperationsManager, Data Warehouse and Audit Collection
Services (ACS) databases, and the root management server (RMS), this installation calls for two
Microsoft Cluster service (MSCS) clusters. Each cluster consists of two nodes: one is actively
running the workload, and the other is passively waiting for the workload to failover to it. The SQL
Server 2005 database workloads are on one cluster and the RMS is on the other. For information
about how to install and configure a cluster, see Windows Server 2003 online help or the Quick
Start Guide for Server Clusters ([Link]

Note
Although this example uses two-node clusters, all of the Operations Manager 2007
databases can be placed on n+1-node clusters. Operations Manager places no limits on
the number of nodes that can be in a cluster for the databases and is limited only by
SQL Server 2005 clustering capabilities. For the RMS, the only supported configuration is
a two-node cluster running in an active-passive configuration. No other Operations
Manager roles may be placed on the RMS cluster.
This deployment scenario uses the following:
 One MSCS cluster for SQL Server 2005 to host the components of the Operations Manager,
Data Warehouse, and ACS databases.
 One MSCS cluster for the Operations Manager RMS component.
 One or more stand-alone servers for secondary management server components.
 One stand-alone server with SQL Server 2005 Database and Reporting Services for the
Operations Manager Reporting component.
 One or more stand-alone servers for the Operations Manager ACS component.

66
 Note
Each ACS installation requires a dedicated instance of SQL Server 2005.
 One or more stand-alone servers for the Operations Manager gateway server component.
 Certificates issued from a Microsoft Certificate Services certification authority or from another
certificate issuer.
For information about complete planning assistance, see the Operations Manager 2007 Design
Guide, [Link] For information about sizing and capacity
planning, see the System Center Capacity Planner (SCCP) Guide on TechNet
([Link]

Before you start

1. Create domain accounts for the following:
 MSAC, SDK and Config, Data Reader, Data Warehouse Write Action, and Operations
Manager Administrators accounts

Important
For this scenario, the MSAC must be a domain-based account, do not use
Local System for the MSAC. In addition, the MSAC must have permissions
on the SQL Server 2005-based server that hosts the OperationsManager
database. For more information, please see the Operations Manager 2007
Security Guide.

Important
When clustering the Root Management Server, the SDK and Config account
must be a domain account and that one account should be used on all
cluster nodes and all secondary management servers. If you need to use
different domain-based accounts for the SDK and Config service on the
cluster node and secondary management servers, see
[Link] for more information before
proceeding.
 Operations Manager Administrators Group
 Cluster service account
 SQL Service account
 Domain groups for SQL Clustered Services, SQL Server, SQL Server Agent, Full-Text
Search
2. Add the Operations Administrator domain account and the Cluster service account to the
Operations Manager Administrators group.

Note
Adding these accounts to the Operations Manager Administrators group helps
with setting up the RMS service in a clustered configuration and is not necessary

67
 for the SQL Database cluster configuration.
3. Add the Operations Manager Administrators group to the Local Administrators Group on
each node.
4. Add the MSAC, SDK and Config, and the SQL Service and Cluster service accounts to
the Local Administrators group on each node.
5. Plan network names for the following:
 Each node in each cluster.
 A network name by which the cluster can be accessed publicly (cluster name).
 A network name for the SQL Server cluster (SQL network name).
 An RMS network name.
6. Plan IP addresses for the following:
 The public-facing network adapter in each cluster node.
 The private or heartbeat network adapter in each cluster node.
 The cluster IP address.
 A SQL IP address.
 An RMS IP address.
7. Plan shared disk (clusterable disk) for the following:
 The Quorum drive.
 Dedicated disk for SQL data files.
 Dedicated disk for SQL log files.
 Dedicated disk for RMS files.
8. Consider the following points for SQL Server clustering:
 Prior to installing SQL Server 2005 Enterprise Edition in the cluster, you must create
a Microsoft Distributed Transaction Coordinator (MSDTC) Resource in the Cluster
Administrator. For more information about preparing and installing SQL Server 2005
in a failover cluster, see the "Before Installing Failover Clustering" topic in the SQL
Server 2005 Books Online and "How to: Create a New SQL Server 2005 Failover
Cluster (Setup)" topic in the SQL Server 2005 Books Online.
 SQL Server Configuration checker can return a warning on the COM+ catalog. If this
happens, see "How to: Work around COM+ check failure in SQL Server Setup" in the
SQL Server 2005 Books Online.

High-level order of installations

1. Install SQL Server 2005 Enterprise Edition in a two-node MSCS cluster.
2. Install the Operations Manager 2007 Database component in the SQL Cluster.
3. Install the Operations Manager 2007 management server and Console components in
the other two-node MSCS cluster.

68
 4. Install one or more secondary management servers on stand-alone servers.
5. Install SQL Server 2005 and SQL Server 2005 Reporting Services on a stand-alone
server.
6. Install ACS on a stand-alone server.
7. Install Operations Manager gateway server on a stand-alone server.

High-Level SQL Cluster Install Guidance

The following procedure provides high-level guidance for installing SQL Server in a cluster and is
not a replacement for the SQL Server 2005 Online Books. It assumes that you already have
access to a healthy two-node MSCS cluster that is dedicated to hosting the Operations
Manager 2007 databases.

To install SQL Server in a cluster

1. Log on to the active cluster node with an account that has local administrator rights.
2. On the SQL Server 2005 Enterprise Edition (or SQL Server 2005 Standard Edition)
installation media, double-click [Link].
3. Click Install SQL Server.
4. Proceed through the Welcome and End User License Agreement screens, selecting
the appropriate responses.
5. Address any issues that are found by the System Configuration Check, and complete
the product registration page.
6. On the Components to Install page, select the SQL Server and Workstation
components, Books Online and development tools options. When you select the SQL
Server option, the Create a SQL Server failover cluster check box is enabled, and you
must select this.
7. On the Virtual SQL Server name page, type a unique instance name for your
installation. This name will be used to identify the failover cluster on your network. This
name must be different than the host cluster name.
8. On the Virtual SQL Server Configuration page, enter one IP address for each network
that is configured for client access.
9. On the Cluster Group Selection page, select the group that contains the drive that you
want to use for SQL Server from the Available Cluster Groups. This is where the SQL
Server virtual SQL Server cluster resources are placed.
10. On the Cluster Node Configuration page, select all nodes that are to be included in the
failover cluster.
11. On the Remote Account Information page, specify an account that has administrative
rights on all cluster nodes.

Note

69
 SQL Server will be installed on all cluster nodes and therefore only has to be run
once.
12. On the Service Accounts (Clusters) page, specify the user name and password for the
SQL Service account.
13. On the Domain Groups for Clustered Services page, provide a DomainName\
GroupName for each clustered service that is being installed. In this case, for SQL
Server, SQL Server Agent, and Full-Text Search.
14. Select Windows Authentication.
15. Accept the default values for the Collation Settings.
16. Proceed through the Error and Usage Reporting Settings page, making the
appropriate selections.
17. On the Ready to Install page, click Install.

For more information about preparing and installing SQL Server 2005 in a failover cluster, see the
"Before Installing Failover Clustering" topic and "How to: Create a New SQL Server 2005 Failover
Cluster (Setup)" topic in the SQL Server 2005 Books Online.

Installing Operations Manager 2007 Database

Components in a SQL Server 2005 Cluster
This procedure assumes that you have access to a dedicated, healthy SQL Server 2005 cluster.
The Database services and the Workstation components, Books Online and development tools
components have been installed. The SQL Server installation must be at the level of SQL
Server 2005 SP1 or SP2 with the kb918222 hotfixes for the database and tools components
applied. To obtain the hotfixes for each platform (x86, x64, I64), see article 918222 in the
Microsoft Knowledge Base ([Link]

To check prerequisites for OperationsManager database installation

1. Log on to Node 1 of the SQL Server 2005 Cluster with the Operations Manager
Administrator account credentials.
2. In the Cluster Administrator tool, ensure that the Cluster Group that hosts all the SQL
Server Cluster resources is owned by Node 1.
3. From your Operations Manager 2007 installation media, double-click [Link] to
start the System Center Operations Manager 2007 Setup on the Start page.
4. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.
5. In the Components box, select the Operational Database and Data Warehouse
options, and then click Check.

Note
When the Operational Database and Data Warehouse components are selected,
the Prerequisite Viewer checks for presence of 2048-MB Physical Memory,

70
 Windows Server 2003 SP1, and SQL Server 2005 SP1 or SP2.

Note
The results are displayed at the bottom of the Prerequisite Viewer. If there are
any deficiencies, they are marked either as a Warning or as Failed. Warnings
can be ignored at the risk of degraded performance; Failed prerequisites must be
fixed before the installation can proceed. You can close the Prerequisite Viewer,
fix the items, and then rerun the Prerequisite Viewer checks as many times as
necessary until a Pass evaluation is achieved on all items.
6. When you are done with the Prerequisite Viewer, click Close.

Installing the Operations Manager 2007 Operational Database

and Data Warehouse Components in a SQL Server 2005 Cluster
To install the OperationsManager database on a cluster, use the Database Configuration Wizard,
as described in [Link]

Note
The OperationsManager database can only be clustered by using the Database
Configuration Wizard found in the Support Tools folder in the installation media.

To set up the database using the Database Configuration Wizard

1. Create a new directory on the database server.
2. Copy these files from the root of the SupportTools directory on the installation media.
 \SupportTools\[Link]
 \SupportTools\DBCreateWizard\i386
 \SupportTools\[Link]
 \SupportTools\[Link]
 \SupportTools\[Link]
3. Double-click [Link] to run the wizard.
4. On the Welcome page, click Next.
5. On the Database Information page, select whether you want to create an Operations
Manager Database or Data Warehouse Database.
6. Select the instance on which to install.
7. Specify a unique name or accept the default.
8. Specify a database size.
9. Click Next.

Note
For a data warehouse, the installation skips to the Summary page.

71
 10. On the management group page, specify a unique management group name.
11. Specify a domain security group which has the Operations Manager Administrators, and
then click Next to continue.
12. On the Error Reporting page, choose to send error reports, and then click Next to
continue.
13. Review the Summary page, and then click Finish.

Use the Database Configuration Wizard again to set up a data warehouse on a cluster.

Using Log Shipping for the OperationsManager Database

Log shipping sends transaction logs from a primary to a secondary database, which keeps the
secondary nearly synchronized with the primary database. For more information about log
shipping, see Log Shipping in the SQL Server 2005 documentation.
To use log shipping, you need to set the OperationsManager database to use Full Recovery
mode. For more information, see [Link]
To set up transaction log shipping to a secondary server, see [Link]
LinkId=91992.

Deploying a Root Management Server on a

Windows Cluster in Operations Manager 2007
The root management server (RMS) is the only management server in a management group that
runs the SDK and Config services, and the management group cannot operate without these
services. This makes these services a single point of failure. Just as the risk of the single
OperationsManager database is mitigated by clustering it, so too can the risk of single instance of
the SDK and Config services be mitigated through clustering.

Note
Do not install agents on the cluster nodes that support the root management server. If
you want to monitor the health of a root management server on a cluster as part of
another management group, use agentless management.
In this procedure, the management server and user interface components are installed on the
cluster, and it makes use of the OperationsManager database that is hosted on the SQL
Server 2005 cluster that was created in the ‘To setup the database using the Database
Configuration wizard’ procedure.
The following procedures show how to install Operations Manager 2007 root management
servers on a Windows cluster. Installing Operations Manager 2007 root management servers on
a Windows cluster involves the following tasks:
 Preparing the Windows cluster and create a cluster group for the RMS.
 Creating Physical Disk, IP Address, and Network Name resources in the RMS cluster group.

72
 Installing the RMS and secondary management servers on the cluster nodes and back up the
RMS encryption key.
 Creating Generic Service cluster resources in the RMS cluster group for the RMS Health
Service (HealthService), the RMS SDK (OMSDK), and the RMS Config (OMCFG) services.
 Backing up the OperationsManager database.
 Running SecureStorageBackup with the Backup option on the RMS to back up the RMS
encryption key.

Note
If the RMS encryption keys were successfully backed up at the end of the RMS
setup, it is not necessary to back them up again at this point.
 Running SecureStorageBackup with the Restore option on all secondary management
servers to place the RMS key on them.
 Running the ManagementServerConfigTool with the InstallCluster option to cluster the RMS
cluster group resources.
 Bringing all RMS cluster groups online.
 Moving the RMS cluster group to each node to complete the configuration.
 Testing to verify successful cluster installation.
 Optionally running the ManagementServerConfigTool with the AddRMSNode option to add
cluster nodes to the RMS cluster that were inaccessible during the InstallCluster action
above.
 Optionally running [Link] if it did not succeed while running the InstallCluster action
above.
If you have previously installed or attempted to install Operations Manager on a cluster and that
attempt has failed, see the additional procedure "To uninstall an Operations Manager 2007 in a
cluster" prior to reinstalling.

To prepare the cluster nodes, the RMS cluster group, and the RMS cluster group
resources
1. On each RMS cluster node, ensure that the domain Operations Manager Administrators
security group has been added to the local Administrators group and that the Cluster
service account is a member of the domain Operations Manager Administrators security
group.

Note
Having the Cluster service account in the Operations Manager Administrators
group is necessary for creating the clustered configuration of RMS.
2. Ensure that each cluster node meets the prerequisites for the management server and
User Interface components:
 Windows Server 2003 SP1 or subsequent service pack
 MDAC version 2.80.1022.0 or later

73
  .NET Framework version 2.0
 .NET Framework version 3.0 components
3. Add the SDK and Config service accounts to the Local Administrators group on each
node of the RMS cluster.
4. Log on to the cluster node that will be the primary owning node for the RMS with
administrative rights.
5. Start the Cluster Administrator tool from Administrative tools or by selecting Start - Run
and running CluAdmin.
6. If this is the first time that the Cluster Administrator tool has been run, you will be
prompted to connect to a cluster. Select the Open connection to cluster option from the
Action: drop-down box and either enter or browse for the cluster name for the Cluster or
server name: box.
7. In the Cluster Administrator tool, right-click the Groups folder to open the context menu
and select New -> Group.
8. On the New Group page, enter a name for the cluster group in the Name: field, enter a
description, and then click Next.

Note
For this procedure, the cluster group created will be called RMSClusterGroup,
although you can rename it as you wish.
9. On the Preferred Owners page, select all computers listed in the Available nodes: list
and Add -> them to the Preferred owners: list. Then click Finish. You should see a pop-
up box stating Cluster group '<clustergroupname>' created successfully message. Click
OK.
10. In the Cluster Administrator tool, right-click the RMSClusterGroup object to bring up
the context menu and select New -> Resource.
11. On the New Resource page, create an IP Address resource with the following
configuration and click Next>.
 Name: RMS IP Address
 Description: This is the IP Address of the RMS Server.
 Resource type: IP Address
 Group: RMSClusterGroup
12. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible
owners: list, and then click Next>.
13. On the Dependencies page, click Next>.
14. On the TCP/IP Address Parameters page, enter a TCP/IP address for the
RMSClusterGroup that is on the same subnet as the publicly accessible network
adapters that the cluster nodes are using in the Address: field. This is the IP address
that will be registered for the RMS server in DNS.
15. Enter the same value in the Subnet mask: field that the cluster node publicly accessible
74
 network adapters are using. This field may be automatically populated.
16. Select the publicly accessible network from the Network: drop-down list. This may
automatically populate.
17. Ensure that the Enable NetBIOS for this address check box is selected, and click
Finish.
18. In the RMS cluster group, create a new Physical Disk resource (as in step 11 above) with
the following configuration and click Next>.
 Name: RMSPhysicalDisk

Note
RMSPhysicalDisk is being used for this procedure only, although you can
rename this resource anything you wish.
 Description: This is the shared cluster disk resource that the RMS will use.
 Resource type: Physical Disk
 Group: RMSClusterGroup
19. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible
owners: list, and then click Next.
20. On the Dependencies page, click Next.
21. On the Disk Parameters page, select the drive letter of the dedicated RMS disk, and
then click Finish.

Note
The disk partition that is used for this must already exist, be included as an
available cluster resource, and be accessible by all cluster nodes.
22. In the RMSClusterGroup, create a new Network Name resource (as in step 10 above)
with the following configuration and click Next.
 Name: RMSNetworkName

Note
RMSNetworkName is being used for this procedure only, although you can
rename this resource whatever you wish.
 Description: This resource defines the network name that the RMS server will be
known by. It will be registered in DNS.
 Resource type: Network Name
 Group: RMSClusterGroup
23. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible
owners: list, and then click Next.
24. On the Dependencies page, select the IP Address resource from the Available
resources: list, and click Add-> to place it in the Resource dependencies: list. Click
Next.

75
 25. On the Network Name Parameters page, enter a valid NetBIOS name in the Name:
field. Ensure that the DNS Registration Must Succeed and the Enable Kerberos
Authentication check boxes are selected. Click Finish.

Important
The value that is entered in the Name field is the server name that is used for the
RMS server. It will be registered in DNS as an A record along with the value you
entered in the IP Address resource.
26. In Cluster Administrator, right-click the RMSClusterGroup object to open the context
menu and select Bring Online.

To check prerequisites for RMS installation

1. Log on to the cluster node that will be the primary owning node for the RMS with
administrative rights.
2. Ensure that the RMS cluster group is owned by the node that you are logged onto. For
example, in a two-node cluster, log on to node 1, open Cluster Administrator, and
select the Groups folder in the details pane. The value in the Owner column for the RMS
cluster group should be the node that you are logged onto. If it is not, right-click the RMS
cluster group, and select Move Group.
3. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup on the Start page.
4. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.
5. In the Components box, select the Server and Console components, and click Check.

Note
When these components are selected, the Prerequisite Viewer checks for
presence of Windows Server 2003 SP1, MDAC version 2.80.1022.0 or
later, .NET Framework version 2.0, .NET Framework version 3.0 components.

Note
The results are displayed at the bottom of the Prerequisite Viewer. If there are
any deficiencies, they are marked either as a Warning or as Failed. Warnings
can be ignored at the risk of degraded performance; Failed prerequisites must be
fixed before the installation can proceed. You can close the Prerequisite Viewer,
fix the items and rerun the Prerequisite Viewer checks as many times as
necessary until a Pass evaluation is achieved on all items.
6. When you are done with the Prerequisite Viewer, click Close.

Installing RMS
In this procedure, you install the first management server in the management group (the RMS).

76
To prepare the cluster and install Operations Manager server-level components
1. Log on to the cluster node that will be the primary owning node for the RMS with
administrative rights.
2. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 SetupWizard on the Start page.
3. Under the Install heading, click Install Operations Manager 2007. This starts the
Operations Manager 2007 Setup Wizard.
4. On the Setup Wizard Welcome page, click Next.
5. On the End User License Agreement page, select the I accept the terms in the
license agreement option, and then click Next.
6. On the Product Registration page, enter the appropriate values in the User Name and
Organization fields. Enter your 25-digit CD Key, and then click Next.
7. On the Custom Setup page, leave the management server and User Interfaces options
set to This component, and all dependent components, will be installed on the local
disk drive. Set the Database, Command Shell and Web Console components to This
component will not be available, accept the default installation location, and then click
Next.
8. On the Prerequisite Checker page, click Next.
9. On the SQL Server Database Instance page, enter the SQL Server name and database
instance in the SQL Database Name box. This is in the format of SQL Server\SQL
Instance. Because the SQL Server database was installed in the default instance, you
only need to enter the SQL Cluster name that was created when you installed SQL
Server 2005 in the cluster.

Note
To find the value, open Cluster Administrator on the SQL Server cluster, select
the Resources folder, in the details pane, select the SQL Network Name
resource and open its properties. Navigate to the Parameters tab and the value
is in the Name field.
10. Check that the SQL Database Name field reads OperationsManager.
11. Check that the SQL Server Port field has the value of 1433.

Note
If you have chosen a different port for SQL Server communications and have
already configured that in SQL Server, you should enter that value here;
otherwise, accept the default of 1433.
12. Click Next.
13. On the management server Action Account page, accept the default Domain or Local
Computer Account option, enter the credentials of the management server Action
account, and then click Next.

77
 Note
By using a domain-based account, it will be much easier to perform discovery
and push agent installation later on than if you chose the Local System account.
For more information about agent installation, see "Agent Deployment" in the
Operations Manager 2007 Administrators Guide.
14. On the SDK and Config Service Account page, select the Domain or Local Account
option, enter the credentials for the SDK and Config service account, and then click Next.

Note
In this configuration, the account must be a domain account, because reporting is
installed on a separate server. This account must have permissions on the
reporting system.

Note
If you receive an Account Verification Error when you click Next, it is most likely
that you mistyped the credentials or the SDK and Config service account was not
added to the local Administrators group.
15. On the Customer Experience Improvement Program page, indicate whether you want
to join this program, and then click Next.
16. On the Microsoft Update page, indicate whether you want to use the Microsoft Update
services to check for updates, and then click Next.
17. On the Ready toInstall the Program page, click Install when you are ready for the
installation to proceed.
18. On the Completing the System Center Operations Manager 2007 Setup Wizard
page, clear the Start the Console check box, ensure that the Back up Encryption Key
check box is selected, and then click Finish. The Encryption Key Backup or Restore
Wizard will now launch.

Important
Even though the Operations Console has been installed, do not launch the
console at this point. Clear the Launch the Operations Console check box to
prevent the Operations Console from launching.

Note
If setup fails, it provides you with a value to search on and a link to open the
setup log.
19. On the Introduction page of the Encryption Key Backup or Restore Wizard, click
Next.
20. On the Backup or Restore page, select Backup the Encryption Key radio button and
click Next.
21. On the Provide a Location page, specify a valid path and filename for the encryption
key and click Next.

78
 Important
It is critical that the location provided for backing up the encryption key be
accessible by all nodes in the cluster.
22. On the Provide a Password page, enter a password to secure the encryption key
backup file and click Next to start the backup process. You will be prompted for this
password when you restore the RMS encryption key later in this procedure.
23. You should now see the Secure Storage Backup Complete page. Click Finish.

Note
Be sure to copy the encryption key to a location that is accessible by all computers that
will be management servers. Also be sure to make multiple copies and store them in
separate, secure locations.

Installing the Secondary Management Servers

In this procedure, you will install secondary management servers on all other nodes in the cluster.
These servers are secondary management servers until this process is complete, at which time
they will be able to host the Root Management Server.

To install secondary management servers in the RMS cluster

1. Log on to each remaining cluster node with the Operations Manager Administrator
account.
2. Follow the Install RMS procedures to install the management server and User Interface
components on each of the other nodes in the management group.

Note
If you choose to install any management server without the User Interfaces
component and you want to run [Link], you must copy
[Link],
[Link], and [Link] from the installation
media to the installation directory on the management server. Typically this is C:\
Program Files\System Center Operations Manager 2007.

Preparing RMS Cluster Resources

In this procedure, you create cluster resources out of the Operations Manager Health Service
(HealthService), the Operations Manager Config service (OMCFG), and the Operations Manager
SDK service (OMSDK). These are the RMS resources that can fail over between cluster nodes
along with the network name, IP address, and physical disk.

To prepare RMS cluster resources

1. Log on to the node that is the owner of the RMS cluster group with an account that has

79
 administrative rights.
2. In Cluster Administrator, right-click the RMSClusterGroup to open the context menu,
select New, and then select Resource. This starts the New Resource Wizard.
3. Create a Generic Service Cluster resource for the Operations Manager Health Service
with the following settings:
 Name:RMS Health Service

Note
You can choose to name this resource anything you want, but for ease of use
make it simple and descriptive.
 Resource type:Generic Service
 Group: RMSClusterGroup
4. Click Next.
5. On the Possible Owners page, ensure that all cluster nodes are listed in the Possible
owners box. If they are not, then select the appropriate node in the Available nodes box
and click Add to add them to the Possible owners box. Click Next.
6. On the Dependencies page, select the RMSPhysicalDisk and RMSNetworkName
resources from the Available resources box, click Add to move to the Resource
dependencies box, and then click Next.
7. On the Generic Service Parameters page, in the Service name field, enter
HealthService.

Important
HealthService is the exact name of the service; this cannot be modified.
8. Leave the Start parameters field empty.
9. Select the Use Network Name for computer name check box, and then click Next.
10. On the Registry Replication page, leave the Root Registry Key field blank, and then
click Next to end the wizard.
11. Repeat the same process for the Operations Manager Config service and the Operations
Manager SDK service using these values:
 For the Config service: Name: RMS Config Service, Resource type:Generic
Service, Group: RMSClusterGroup, Possible owners: all nodes, Resource
dependencies: RMSPhysicalDisk and RMSNetworkName, Service Name:OMCFG,
select the Use Network Name for computer name, Root Registry Key blank.
 For the SDK Service: Name: RMS SDK Service, Resource type:Generic Service,
Group: RMSClusterGroup, Possible owners: all nodes, Resource dependencies:
RMSPhysicalDisk, RMSNetworkName, Service name:OMSDK, select the Use
Network Name for computer name check box, Root Registry Key blank.

Important
Do not bring the HealthService, the Config, or the SDK resources online at

80
 this time.

Creating the RMS Cluster

In this procedure, you distribute the RMS Key to the secondary management servers and create
the RMS cluster. At the end of this procedure, all nodes in a cluster can host the RMS.

Before you start

1. Ensure that the file share with the encryption key is accessible by all cluster nodes. This
is used for distributing the RMS Key.
2. Make sure that the Cluster service account has been added to the Operations Manager
Administrators Global Security group.

Creating the Virtual RMS

To create the virtual Root Management Server
1. Log on to the computer that owns the RMSClusterGroup with an account that is a
member of the Administrators group.
2. On the Operations Manager 2007 installation media, locate the
[Link] and the [Link] files in the \
SupportTools folder.
3. Copy these files to the installation folder for Operations Manager (typically Program Files\
System Center Operations Manager 2007) on the RMS owning node.

Note
If SecureStorageBackup is already present in the Operations Manager
installation folder on the RMS, it is not necessary to copy it.

Note
If you successfully backed up the encryption key at the end of RMS setup, you
can skip to step 7.
4. On the RMS owning node, open a command prompt and change current directory to the
Operations Manager installation folder; for example, cd \Program Files\System Center
Operations Manager 2007.
5. To back up the RMS Key, type the following, where <fileshare> is a share accessible by
all cluster nodes:
[Link] Backup \\<fileshare>\<filename>.bin.

Note
This will launch the Encryption Key Backup or Restore Wizard. A password will
be requested. It must be at least eight characters long and must include at least

81
 one symbol. You must confirm the password to create the encryption key file.
6. Log on to each secondary management server computer with an account that is a
member of the Administrators group.
7. At a command prompt on each secondary management server, type cd <path to
Operations Manager installation directory> and then press ENTER.
8. To restore the key to each secondary management server, type the following, where
<fileshare> is a share accessible by all cluster nodes:
[Link] Restore \\<fileshare>\<filename>.bin

Note
This will launch the Encryption Key Backup or Restore Wizard. Select the
Restore option, and enter the path to the encryption key file. You must provide
the same password that you entered to encrypt the file on the RMS node.
9. Log on to the RMS computer with an account that is a member of the Administrators
group.
10. In Cluster Administrator, expand the cluster, and then click Groups. In the results pane,
make sure that the computer that is hosting the Root Management Server appears in the
Owner column. If the computer hosting the Root Management Server does not appear as
the owner, in the navigation pane, right-click the Operations Manager group and select
Move Group to move the RMSClusterGroup to the node that is the RMS.
11. On the SQL Server-based computer that hosts the OperationsManager database, open
the SQL Server Management Studio tool, open the Databases folder, and select the
OperationsManager database. Right-click to open the context sensitive menu and select
Tasks, Back Up to initiate a backup. On the Back Up Database - OperationsManager
page, ensure that the Backup type value is set to Full, give the Backup set an
appropriate name, and set the Backup set will expire value to a date in the distant
future. In the Destination box, for the Back up to value, select Disk and add an
appropriate disk location to hold the backup, if one is not already present, and then click
OK.

Important
When you run the ManagementServerConfigTool to create the RMS cluster, you
are advised to back up the OperationsManager database because irrecoverable
damage can be done by creating the RMS cluster if something is done
incorrectly.

Note
The OperationsManager database should already be running in the Full
Recovery model. For more information, see SQL Server 2005 Books Online.
12. On the RMS server, open a command prompt, type cd <path to Operations Manager
installation directory>, and then press ENTER.
13. To instantiate the RMS cluster group as a cluster, type the following, where G is the disk

82
 resource that is allocated to the cluster group that is being used to create this virtual Root
Management Server and where <VirtualServerNetbiosName> is the network name
resource allocated to the same cluster group:
[Link] InstallCluster
/vs:<VirtualServerNetbiosName> /Disk:G
The value you enter for <VirtualServerNetbiosName> must be the value that appears in
the Name text box located on the Parameters tab of the Properties dialog box for the
network name resource.

Note
[Link] InstallCluster will install the RMS as a
clustered service on every available node in the cluster.

Note
When you run the ManagementServerConfigTool, the output might display
instructions for running the SetSPN command.
14. In the Cluster Administrator, right-click the RMSClusterGroup to open the context menu
and select Bring Online to bring all the RMSClusterGroup services online.

Note
If you did not run ManagmentServerConfigTool InstallCluster as an administrator
account, go to step 15; otherwise, skip to step 16.
15. If you are not running the ManagementServerConfigTool under the account which is
running the Cluster service or is an administrator account, you must manually run the
SetSPN utility. Disregard the SetSPN commands that appear in the
ManagementServerConfigTool output, and instead use the following command—where
<domain>\<user name> is the account that the Cluster service is running under, where
the value for <VirtualManagementServerFQDN> is the same name you use for
<VirtualManagementServerNetbios> with the domain extension appended, and where
the value for <VirtualManagementServerNetbios> must be the value that appears in the
Name text box located on the Parameters tab of the Properties dialog box for the
network name resource:
runas /user:<domain>\<user name> "[Link] -A
MSomHSvc/<VirtualManagementServerFQDN>
<VirtualManagementServerNetbios>"

Note
The SetSPN utility is available in the Windows 2000 Resource Kit
([Link]

Note
Later, when you are installing stand-alone management servers, if they are not
able to establish a secure Kerberos channel with the RMS, you should run the

83
 SetSPN command to ensure that the SPN has been set correctly. It is critical that
the parameter MSomHSVC be used exactly as it is spelled because the
HealthService on the stand-alone management servers establish a connection
only with this object.
16. Open the Cluster Administrator tool and right-click the RMSClusterGroup to open the
context menu and select Move group. Repeat this so that the RMSClusterGroup is
moved to each node.

Important
The RMSClusterGroup must be moved and successfully come online on each
cluster node in order to set the state of the Health, SDK, and Config services
correctly on each node at this time. Do not skip this step.
Clustered RMS setup is complete.

Preparing an Inaccessible Management Server

The following procedure is required only if, in bringing the cluster group online, the output stated
that you are required to run the [Link] tool using the
AddRMSNode action on any of the non-Root Management Server cluster nodes. This is most
likely caused by a cluster node not being accessible when the InstallCluster action was executed
or you are adding a new node to the cluster.

To prepare inaccessible management servers

1. Log on to the computer that hosts the management server as a member of the
Administrators group.
2. Open the services snap-in and if the startup type for the OpsMgr SDK Service is set to
Disabled, change it to Manual.
3. At a command prompt, change directories to the installation folder and type the following:
[Link] AddRMSNode
/vs:<VirtualServerNetbiosName> /Disk:<VirtualServer Disk Resource>
VirtualServerNetbiosName is the Network Name resource allocated to the same cluster
group. The value you enter for VirtualServerNetbiosName must be the value that
appears in the Name text box located on the Parameters tab of the Properties dialog
box for the Network Name Cluster resource.
VirtualServerDiskResource is the disk resource allocated to the cluster group being
used to create this Virtual Root Management Server. The Disk location can be found by
on the Parameters tab of the Properties dialog box for the Disk Resource.

Testing the Cluster Installation

Use the following procedure to test the cluster installation.

84
 To test an Operations Manager 2007 cluster
1. In the Operations Console, click Administration.

Note
When you run the Operations Console on a computer that is not a management
server, the ConnectToServer dialog box appears. In the Servername text box,
type the name of the RMS Server (the cluster virtual server name) that you want
the Operations Console to connect to.
2. In the Administration pane, point to Administration, point to Device Management, and
then click management server.
3. In the management servers pane, the RMS Server Network Name should appear with a
health state of Healthy.
4. In the Administration pane, click AgentlessManaged.
5. In the Agentless Managed pane, the entry for each node in the cluster should appear with
a health state of Healthy.

Uninstalling Operations Manager 2007

Use the following procedure to uninstall Operations Manager 2007.

To uninstall Operations Manager 2007 from a cluster

1. In Cluster Administrator, point to Groups, and then click the Operations Manager group.
2. In the right page, right-click each of the three Operations Manager Services, and then
click Take Offline.
3. In the right page, right-click each of the three Operations Manager Services, and then
click Delete.
4. Perform the following steps on every node in the cluster that a management server was
installed on:
a. On the computer, click Start, point to Settings, and then click ControlPanel.
b. In Control Panel, double-click Add or Remove Programs, click System Center
Operations Manager 2007, and then click Remove.
c. Close Control Panel.
d. Delete the \Program Files\System Center Operations Manager 2007 folder and all
subfolders and files.
e. Delete the following registry keys:
 HKLM/SOFTWARE/Microsoft/Microsoft Operations Manager
 HKLM/SYSTEM/CurrentControlSet/Services/HealthService
 HKLM/SYSTEM/CurrentControlSet/Services/MOM Connector
5. On the computer that is the active node of the cluster, open Windows Explorer, and on

85
 the shared cluster disk resource, delete the three service state folders which are, Config
Service State, Health Service State, and SDK Service State.
6. Use Add or Remove Programs to uninstall any Operations Manager database and
Operations Console that you have installed.
7. On the Windows desktop, click Start, point to Programs, point to Microsoft SQL
Server 2005, and then click SQL Server Management Studio.
8. In the Connect to Server dialog box, do the following: in the ServerType list, select
DatabaseEngine; in the ServerName list, select the server and instance for your
Operations Manager database (for example, computer\INSTANCE1); in Authentication
list, select WindowsAuthentication; click Connect.
9. In the Object Explorer pane, expand Databases, right-click Operations Manager, and
then click Delete.
10. In the Delete Object dialog box, select CloseExistingConnections and then click OK.
You are now ready to reinstall starting with Installing Operations Manager 2007 Database
Components in a SQL Server 2005 Cluster procedures.

Note
If you uninstall Server Components of Operations Manager 2007, the Operations
Manager event log remains following the uninstall, by design. This causes the
Operations Manager installation folder to remain also (default: %ProgramFiles%\
Microsoft System Center Operations Manager 2007).

Deploying Stand-Alone Management Servers

in the Multiple Server, Single Management
Group Scenario
To allow agents to have fail-over targets and to further distribute the Operations Manager 2007
Server components, you must install additional management servers in the management group.
After they are installed, you can use the Agent Assignment and Failover Wizard to indicate which
management servers are available for failover, and you can install the ACS server and Web
console components.
In this scenario, two additional secondary stand-alone management servers are installed.

Before You Start

To prepare servers for management server components
1. Make sure that all servers that will be used as management servers are in Forests that

86
 share a Kerberos trust with the Forest that the root management server (RMS) is in.
2. Use the Manage Your Server tool to add the Application Server role to the server or
manually install IIS. Install the .NET Framework version 2.0, .NET Framework version 3.0
components, and MSXML 6.0. Install Windows PowerShell if you want to install the
Operations Manager Command Shell component.
3. Add the Operations Manager Administrators Domain group to the Local Administrators
group, add the domain-based management server Action account to the Local
Administrators group, and add the SDK and Config Service account to the Local
Administrators group.
4. Complete the RMS cluster setup and verify the health of the RMS before you start
installing any stand-alone secondary management servers.

To check for management server prerequisites by using Prerequisite Viewer

1. Log on to the target server with the Operations Administrator account credentials.
2. From your Operations Manager 2007 installation media, double-click [Link] to
start the System Center Operations Manager 2007 Setup on the Start page.
3. Under the Prepare heading, click Check Prerequisites to start the Prerequisite Viewer.
4. In the Components box, select the Server, Console, and PowerShell components.

Note
When the Server, Console, and PowerShell components are selected, the
Prerequisite Viewer checks for presence of 2048-MB physical memory,
Windows Server 2003 SP1, MDAC Version 2.80.1022 or later, .NET
Framework 2.0, .NET Framework 3.0 components, and Windows PowerShell.

Note
The results are displayed at the bottom of the Prerequisite Viewer. If there are
any deficiencies, they are marked either as a Warning or as Failed. Warnings
can be ignored at the risk of degraded performance; Failed prerequisites must
be fixed before the installation can proceed. You can close the Prerequisite
Viewer, fix the items and then rerun the Prerequisite Viewer checks as many
times as it is necessary, until a Pass evaluation is achieved on all items.
5. When you are done with the Prerequisite Viewer, click Close.

Installing a Stand-Alone Management Server

In this procedure, you install a secondary management server in the management group on a
stand-alone server.

To install a stand-alone management server

1. On the server that you are going to install Operations Manager on, log on with the

87
 Operations Manager Administrator account.
2. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup Wizard on the Start page.
3. Under the Install heading, click Install Operations Manager 2007 to start the
Operations Manager 2007 Setup Wizard.
4. On the Setup Wizard Welcome page, click Next.
5. On the End User License Agreement page, select the I accept the terms in the
license agreement option, and then click Next.
6. On the Product Registration page, enter the appropriate values in the User Name and
Organization fields. Enter your 25-digit CD Key, and then click Next.
7. On the Custom Setup page, ensure that the ManagementSserver, User Interfaces and
Command Shell components are set to This component, and all dependent
components, will be installed on the local disk drive. Set the Database and Web
Console options to This component will not be available. To change the installation
directory, click Browse, enter the appropriate path and folder name, and then click Next.
8. On the SQL Server Database Instance page, enter the name of the clustered SQL
Server instance in the SC database Server field. This is the value that is in the Network
Name field of the SQL Server Name Cluster Resource. In the SQL Database Name field,
ensure that OperationsManager is present, or change it if you changed the name of the
database when you installed the Operations Manager database component. In the SQL
Server Port field, accept the default of 1433 unless you have configured SQL Server to
use a different port for communications. If you have done so, enter the appropriate port
number.
9. On the Management Server Action Account page, accept the default Domain or Local
Computer Account option, enter the credentials of the management server Action
account, and then click Next.

Note
By using a domain-based account, it will be much easier to perform discovery
and push agent installation later on than if you chose the Local System account.
For more information about agent installation, see Agent and Agentless
Monitoring.
10. On the SDK and Config Service Account page, select the Domain or Local Account
option, enter the credentials for the SDK and Config Service account, and then click
Next.

Note
It is necessary to use a domain-based account because you are distributing the
Operations Manager server components across multiple servers.

Note
If you receive an Account Verification Error when you click Next, it is most likely

88
 that you mistyped the credentials or the SDK and Config Service account was
not added to the Local Administrators group.
11. On the Customer Experience Improvement Program page, indicate whether you want
to join this program, and then click Next.
12. On the Microsoft Update page, indicate whether you want to use the Microsoft Update
services to check for updates, and then click Next.
13. On the Ready to Install the Program page, click Install when you are ready for the
installation to proceed.
14. On the Completing the System Center Operations Manager 2007 Setup Wizard
page, accept the default option to Start the Console, and then click Finish.

Note
If Setup fails, it provides you with a value to search on and a link to open the
setup log.
15. In the Operations Console, in the Monitoring view, expand the Operations Manager
folder, expand the management server folder and select the management server State
object, and then confirm that the newly added management server is present and in a
Health state.

Note
It may take up to five minutes for the HealthService on the new management
server to establish secure communications with the clustered RMS, and during
that time it appears as not monitored. When communications are established, its
Health state changes to Healthy.

Note
If you uninstall Server Components of Operations Manager 2007, the Operations
Manager event log remains following the uninstall, by design. This also causes
the Operations Manager installation folder to remain (default: %ProgramFiles%\
Microsoft System Center Operations Manager 2007).

Troubleshooting Tips
If the secondary management server cannot establish a secure communications channel with the
RMS, it is because Kerberos authentication is failing. You will see these three events in the
Operations Manager Event Viewer event log. If this occurs, rerun the SetSPN tool, paying special
attention to the syntax, on the cluster node that owns the RMS cluster resources. Take the RMS
cluster group offline, open Computer Management on the owning node, and then expand the
Services and Applications, Services node. Restart the OpsMgr Health Service, and then bring
the RMS cluster group back online. It might also be necessary to restart the HealthService on
the stand-alone management server. After five to ten minutes, the secure channel is established
and communication starts.
Event Type: Error

89
Event Source: OpsMgr Connector
Event Category: None
Event ID: 20057
Date: 3/2/2007
Time: [Link] PM
User: N/A
Computer: <ManagmentServerName>
Description:
Failed to initialize security context for target MSOMHSvc/<[Link]>.
The error returned is 0x80090303 (the specified target is unknown or unreachable). This error
can apply to either the Kerberos or the SChannel package.
Event Type: Error
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21001
Date: 3/2/2007
Time: [Link] PM
User: N/A
Computer: <ManagmentServerName>
Description:
The OpsMgr Connector could not connect to MSOMHSvc/<[Link]>
because mutual authentication failed. Verify that the SPN is properly registered on the server and
that, if the server is in a separate domain, there is a full-trust relationship between the two
domains.
Event Type: Error
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21016
Date: 3/2/2007
Time: [Link] PM
User: N/A
Computer: <ManagmentServerName>
Description:
OpsMgr was unable to set up a communications channel to <[Link]>
and there are no failover hosts. Communication will resume when
<[Link]> is available and allows communication from this computer.

90
Deploying Reporting in the Multiple Server,
Single Management Group Scenario
In this scenario, the Data Warehouse and the Operations Manager Reporting components are
installed on separate servers. The Data Warehouse database is installed in the SQL Server
Cluster and the Reporting services are installed on a stand-alone server that is hosting SQL
Server Database and SQL Reporting Services.

Note
Although SQL Reporting Services is installed on the stand-alone server, Operations
Manager Reports are not accessed on this server; instead, they are accessed in the
Reports view in the Operations console. If you want to access published reports via the
Web console, then you must install the Operations Manager 2007 Web console
component on the same computer as Operations Manager 2007 Reporting services.

High-Level Installation Overview

Installation overview
1. Run the DBCreateWizard on the SQL Server cluster to create the Data Warehouse
database.

Note
If you need to install the Data Warehouse database on a stand-alone SQL
Server 2005 instance, you would use the Operations Manager 2007 Reporting
Setup and select the Data Warehouse component only.
2. Run Install Operations Manager 2007 Reporting on the stand-alone Reporting server,
and choose to install the Reporting Server component only.
3. Verify the health of Operations Manager 2007 Reports.

Before you start

1. On the stand-alone server that is to be used for Reporting Services, add the following
accounts and group to the Local Administrators group:
 Domain management server Action account
 Domain SQL Service account
 Domain SDK and Config Service account
 Domain Operations Manager Administrators security group
 Domain Data Reader and Data Writer accounts

91
 Note
Before you continue with this procedure, be sure that the account you plan to use
for the Data Warehouse Write Account has SQL Login rights and is an
Administrator on the computers hosting both the Operations Manager database
and Reporting data warehouse. Otherwise, setup fails and all changes are rolled
back, which might leave SQL Reporting Services in an inoperable state.

Note
Both the Data Warehouse Write Account and the Data Reader account must
have logon locally rights on this server.
The account that you use to run the Operations Manager 2007 Reporting installation
must be a member of the following groups and roles.
 Local Administrator – this is required by the Operations Manager 2007 Reporting
installation and for configuring SQL Server Reporting Services.
 Operations Manager Administrator role – this is required for configuring reporting
roles and creating reporting instances.
 SQL SysAdmin for the OperationsManager database – this is required for configuring
dwsynch_users role.
 SQL SysAdmin for the Data Warehouse database – this is required for configuring
OpsMgrWriter and OpsMgrReader roles.
2. Add the Application Server role to the stand-alone reporting server by using the Manage
Your Server tool or manually install IIS by using the Add and Remove Programs tool.
3. Install SQL Server 2005 on the stand-alone server with the SQL Server Database
Services, Reporting Services in Native mode, not Sharepoint Integrated mode and
Workstation components, Books Online and development tools options.
4. Apply SQL Server 2005 SP1 to the stand-alone reporting server and the KB918222
hotfixes for server, reporting, and tools. To obtain the hotfixes, see article 918222 in the
Microsoft Knowledge Base ([Link] Or install SQL
Server 2005 SP2.
5. Confirm the existence of the ReportServer and ReportServerTempDB databases in
SQL Server Management Studio on the stand alone server. Click Start, point to
Programs, point to Microsoft SQL Server 2005, point SQL Server Management
Studio, and connect to the default database instance. Open the Databases node and
look for the two Reporting Services databases.
6. Confirm the correct configuration of SQL Server 2005 Reporting Services. Click Start,
point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools,
and click Reporting Services Configuration to launch the Configure Report Server
tool. Connect to the instance that you installed Reporting Services on.
7. In the left hand pane, ensure that Server Status, Report Server Virtual Directory,
Report Manager Virtual Directory, Windows Service Identity, Database Setup, and
Initialization are all not in a Not configured state, any other state is acceptable. If they
92
 are not, select the item and follow the configuration instructions in the right hand pane.
8. Confirm that the SQL Server reporting Services service is running. Click Start, point to
Settings, and select Control Panel. In the Control Panel, select Administrative Tools,
and open Services.
9. In the Name column, find the SQL Server Reporting Services instance service and
confirm that its status reads Started and that its Startup Type is reads Automatic.
10. Confirm that the Report Server Web site is up by browsing to Error! Hyperlink reference
not valid.>. You should see a page with the
<servername>/ReportServer<$INSTANCE> and the text Microsoft SQL Server
Reporting Services Version #.##.####.## where the # is the version number of your
SQL Server installation.
11. Confirm the correct configuration of Report Manager Web site by opening Internet
Explorer and browsing to [Link]
12. Once you are in the Report Manager Web site, click New Folder to create a new folder.
Enter a name and description and click OK. Ensure that the new created folder is visible
on the Report Manager Web site.

For more information on how to verify a SQL Server Reporting Services installation see:
[Link]

Installing Operations Manager Data Warehouse

In this procedure, you install the Operations Manager Data Warehouse in the SQL Server cluster.
This installs only the database; no binary files are installed.

Note
It is only necessary to do this procedure if you did not install the Data Warehouse
database in the Installing the Operations Manager 2007 Operational Database and Data
Warehouse Components in a SQL Server 2005 Cluster procedure.

To set up the Data Warehouse database using the Database Configuration Wizard
1. Create a new directory on the database server.
2. Copy the file [Link] from one of the following directories on the installation
media:
 \SupportTools\DBCreateWizard\amd64
 \SupportTools\DBCreateWizard\i386
3. From a computer with the Operations Manager 2007 Operations console installed, copy
the following files to the directory you created on the database server:
 C:\Program Files\System Center Operations Manager 2007\
[Link]

93
  C:\Program Files\System Center Operations Manager 2007\
[Link]
 C:\Program Files\System Center Operations Manager 2007\
[Link]
4. Double-click [Link] to run the wizard.
5. On the Welcome page, click Next.
6. On the Database Information page, select to create a Data Warehouse Database.
7. Select the instance on which to install.
8. Specify a unique name or accept the default. It is recommended to accept the default.

Note
If you specify a custom name for the Data Warehouse database, be sure not to
include a '-' character. The database installation will fail if a '-' character is
included in the name.
9. Specify a database size.
10. Click Next.

Note
For a Data Warehouse, the installation skips to the Summary page.
11. Specify a domain security group which has the Operations Manager Administrators, and
then click Next to continue.
12. On the Error Reporting page, choose to send error reports, and then click Next to
continue.
13. Review the Summary page, and then click Finish.

Installing Operations Manager Reporting on a Stand-Alone

Server
In this procedure, you install the Operations Manager Reporting component on the stand-alone
Reporting server. Due to changes that the Operations Manager 2007 Reporting component
makes to SQL Server Reporting Services security, no other applications that make use of SQL
Server Reporting Services can be installed on this server.

To check for Operations Manager 2007 Reporting component prerequisites

1. Log on to the server with the Operations Administrator account credentials.
2. From your Operations Manager 2007 installation media, double-click [Link] to
start the System Center Operations Manager 2007 Setup on the Start page.
3. Under Prepare, click Check Prerequisites to start the Prerequisite Viewer.
4. In the Components box, select the Reporting component, and then click Check.

Note

94
 When the Reporting component is selected, the Prerequisite Viewer checks for
presence of Windows Server 2003 SP1, and SQL Server 2005 SP1 or SP2, SQL
Server Reporting Services SP1 or SP2, .NET Framework version 2.0, .NET
Framework version 3.0 components, and that the World Wide Web service is
running and set to automatic startup.

Note
The results are displayed at the bottom of the Prerequisite Viewer. If there are
any deficiencies, they are marked either as a Warning or as Failed. Warnings
can be ignored at the risk of degraded performance; Failed prerequisites must
be fixed before the installation can proceed. You can close the Prerequisite
Viewer, fix the items and rerun the Prerequisite Viewer checks as many times
as it is necessary until a Pass evaluation is achieved on all items.
5. When done with the Prerequisite Viewer, click Close.

To install Operations Manager 2007 Reporting component

1. Log on to the server with the Operations Manager Administrator account.
2. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup Wizard on the Start page.
3. Under the Install heading, click the Install Operations Manager 2007 Reporting link.
4. On the Welcome page, click Next>.
5. On the End-User License Agreement page, select the I accept the terms in the
license agreement option.
6. On the Product Registration page, enter the appropriate value in the User Name and
Organization fields. Enter the 25-digit CD Key, and then click Next>.
7. On the Custom Setup page, ensure that the Reporting Server component is set to This
component, and all dependent components, will be installed on the local disk
drive, and that the Data Warehouse component is set to This component will not be
available. To change the installation directory, click Browse, enter the appropriate path
and folder name, and then click Next>.
8. On the Connect to the Root Management Server page, enter a value in the name field
of the RMS Network Name Cluster resource, and then click Next>.
9. On the Connect to the Operations Manager Data Warehouse page, in the SQL Server
Database instance field, enter the value that is in the name field of the SQL Network
Name cluster resource. In the SQL database name field, check that
OperationsManagerDW is there. Check that the SQL Server Port field is set to 1433,
unless you have previously configured a different port for SQL Server communications,
enter that value, and then click Next>.
10. On the SQL Server Reporting Services Instance page, select the Reporting Services
server instance name from the drop-down list, and then click Next>. In this case, the field

95
 should already be populated with the local server name.

Note
Installing Operations Manager 2007 Reporting Services integrates the security of
the instance of SQL Reporting Services with the Operations Manager role-based
security. Do not install any other Reporting Services applications in this same
instance of SQL Server.
11. On the Data Warehouse Write Account page, enter the DataWriter account credentials,
and then click Next>.
12. On the Data Reader Account page, enter the DataReader account credentials, and then
click Next>.
13. On the Operational Data Reports page, select whether to join the program, and then
click Next>.
14. On the Microsoft Update page, select whether to use Microsoft Update.
15. On the Ready to Install the Program page, click Install.
16. When the installation is complete, click Finish.

Note
Operations Manager Reports are accessed in the Operations Console, in the Reporting
view. After initial deployment, it can take up to 30 minutes for reports to appear

To confirm the health of Operations Manager reports

1. Log on to a management server with an Operations Administrator role account and start
the Operations Console.
2. In the Operations Console, select the Reporting View (on the bottom left side of the
console).
3. Under Reporting, select the Microsoft ODR Report Library, and then double-click any
of the reports listed; by default, you should see the management group, management
packs and Most Common Alerts reports. This causes the selected report to be
generated and be displayed in a new window.

Note
Selecting the management packs report is particularly useful at this point
because it provides you with a full inventory of the management packs that have
been installed on your server.
4. Close the report window.

Uninstalling Operations Manager Reporting Services

You can uninstall Operations Manager Reporting services through the Add or Remove
Programs tool. If you do, you must also run the [Link] tool found in the SupportTools
folder of the Operations Manager installation media.
96
 To uninstall Operations Manager 2007 Reporting Services component
1. Log on to the Reporting Server with the Operations Manager Administrator account.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. From the list of currently installed programs, select Systems Center Operations
Manager 2007 Reporting Server, and then click Remove. This uninstalls Operations
Manager Reporting Server, and it does not uninstall SQL Server 2005 Reporting
Services.
4. When the uninstall is complete, copy the [Link] tool to the root of the local hard
drive.
5. Open a command prompt and change directories to the root of the local hard drive or
wherever you copied the [Link] tool, and then enter c:\[Link]
<SQLINSTANCENAME> where SQLINSTANCENAME is the name of the instance of SQL
Server that SQL Reporting Services was installed in. If you installed in the default
instance, use MSSQLSERVER for the <SQLINSTANCENAME> value.
6. Click Start, point to Microsoft SQL Server 2005, point to Configuration Tools, and then
select Reporting Services Configuration.
7. On the left side, select Web Service Identity and on the right side click Apply. This
restores the SQL Server Reporting Services installation to its pre-Operations
Manager 2007 Reporting Server component state.

Deploying ACS in the Multiple Server, Single

Management Group Scenario
In this procedure, the Audit Collection Services Collector and the Audit Collection Services (ACS)
databases are installed on different servers, with the ACS Collector on a stand-alone
management server and the ACS database on the SQL Server cluster. The Operations Manager
ACS Collector service must be installed on an existing management server. You can also choose
to create a database for ACS to use or you can let the setup program create one for you. In this
procedure, an already existing stand-alone secondary management server is used for the ACS
Collector component and a new ACS Database is created by the ACS setup on the SQL Server
cluster.
When you are done with this procedure, you must enable the ACS forwarder function on all
Operations Manager Agents that you want to collect Windows Security Event Log events from.
For more information about enabling ACS forwarders, see the topic "How to Enable ACS
Forwarders" in the Operations Manager 2007 Help.

97
Before You Start
Before you start
 The Operations Manager 2007 Prerequisite Viewer does not have an option to check for
ACS Collector and Database because an existing management server must host the
ACS Collector role and a SQL Server database server already exists to support the
OperationsManager database for the management group. Also, all the proper accounts
have already been added to the Local Administrators group on the management server
and the SQL Server database server.

Installing ACS on a Secondary Management Server

To install ACS
1. Log on to the secondary management server that is to host the ACS Collector with the
domain-based Operations Manager Administrator account. This account should already
have local administrative rights.
2. On your installation media, start [Link]. This starts the System Center
Operations Manager 2007 Setup Wizard on the Start page.
3. Under the Install heading, click the Install Audit Collection Server link.
4. On the Welcome page, click Next>.
5. On the End-User License Agreement page, select the I accept the terms in the
license agreement option.
6. On the Database Installation Options page, select the Create a new database option.
This creates the ACS database on the designated instance of SQL Server with the
necessary tables and stored procedures and the SQL login and database user for the
collector. Click Next>.
7. On the Data Source page, in the Data Source name field, accept the default value of
OpsMgrAC, and then click Next>.

Note
The ACS Collector uses an ODBC (Open Database Connectivity) Data Source
Name (DSN) to communicate with the ACS database.
8. On the Database page, under Choose an ACS database, select the Remote database
server option. In the Remote database server machine name field, enter the value in
the name field of the SQL Server network name cluster resource. Leave the Database
server instance name field blank, unless you have installed the SQL Server cluster in a
named instance of SQL Server, and then enter that value. In the Database name field,
accept the default of OperationsManagerAC, but if you plan to host multiple ACS
databases in the same instance of SQL Server, enter a unique name. Click Next>.
9. On the Database Authentication page, select Windows authentication, and then click

98
 Next>. By selecting Windows authentication, the ACS Collector services will use the local
machine account to write to the ACS database during normal operations.
10. On the Database Creation Options page, select the Use SQL Server default data and
log file directories option, and then click Next>. This ensures that the ACS database
and log files are placed on the SQL Server physical disk cluster resource.
11. On the Event Retention Schedule page, set the Local hour of day to perform daily
maintenance and Number of days an event is retained in database options to the
appropriate values, and then click Next>.
12. On the ACS stored Timestamp Format page, select either the Local or Universal
Coordinated Time (UTC) option, and then click Next>.
13. On the Summary page, review the installation options, and then click Next>.
14. During the installation, you might be prompted for a SQL Server Login. If you are logged
on with with an account that has SQL Administrator rights, then accept the default or
otherwise provide credentials that have the SQL Server Administrator rights.

Note
This account is used by the setup process to create the ACS database.
15. Click Finish to complete the installation.
16. On the SQL Server cluster, open the SQL Server Management Studio tool, open the
Databases folder, and confirm the presence of the OperationsManagerAC database.
17. On the ACS management server, open the Computer Management tool, point to
Services and Applications, select Services, and confirm that the Operations Manager
Audit Collection Service is present, that it is started, and that the Startup Type is set to
Automatic.
18. You can now enable the ACS forwarders. For more information, see How To Enable ACS
Forwarders In Operations Manager 2007.

How to Deploy Operations Manager 2007

ACS Reporting
Audit Collection Services (ACS) reporting can be installed in two configurations.
 A Microsoft SQL Server 2005 Reporting Services (SRS) SP1 or SP2 instance with Operations
Manager Reporting already installed. A benefit of this is the ability to view ACS Reports in the
Operations console.
 A SRS instance without Operations Manager Reporting installed.
The installation procedures for ACS Reporting do not differ, but the application of access control
is different. By deploying ACS Reporting on the same SQL Server 2005 Reporting Services

99
instance as your Operations Manager 2007 Reporting, the same role-based security applies to all
reports. This means that ACS Reporting users need to be assigned to the Operations Manager
Report Operator Role to access the ACS reports.
In addition to membership in the Operations Manager Reporting Role, ACS report users must
also be assigned db_datareader role on the ACS database (OperationsManagerAC) in order to
run ACS reports. This is requirement is independent of the presence of Operations Manager
Reporting
If you choose to install ACS Reporting independently of Operations Manager Reporting, you can
also use SRS security to secure the reports. See the SQL Server 2005 Books Online Reporting
Services Tutorials, Setting Permissions in Reporting Services for more information.

Before You Start

Deploy ACS as described in .About Audit Collection Services (ACS) in Operations Manager 2007
before setting up ACS reporting.

Before you start

1. The root management server for your management group must be installed and ACS
must be configured, on either the RMS or a management server. For more information,
see About Audit Collection Services (ACS) in Operations Manager 2007.
2. An instance of Microsoft SQL Server 2005 Reporting Services must be installed on the
target computer.
3. During this procedure, you need to be logged on as member of Operations Manager
Report Operator user role.
4. IIS must be installed on the hosting system. IIS will have already been installed if you are
co-locating with a Reporting Server.
5. You need to have access to the ACS database.
6. You need the Operations Manager 2007 installation media.

Deploying ACS Reporting

To deploy ACS Reporting
1. Logon to the server that will be used to host ACS reporting as a user that is an
administrator of the SRS instance.
2. Create a temporary folder, such as C:\acs.
3. On your installation media, go to \ReportModels\acs and copy the directory contents to
the temporary installation folder.
There are two folders (Models and Reports) and a file named
[Link].

100
 4. On your installation media, go to \SupportTools and copy the file [Link]
into the temporary acs folder.
5. Launch a Command Prompt window and change directories to the temporary acs folder.
6. Run the following command.
UploadAuditReports “<AuditDBServer\Instance>” “<Reporting Server URL>”
“<path of the copied acs folder>”
For example: UploadAuditReports “myAuditDbServer\Instance1”
“[Link] “C:\acs”
This example creates a new data source called Db Audit, uploads the reporting models
[Link] and [Link], and uploads all reports in the acs\reports directory.

Note
The reporting server URL needs the reporting server virtual directory
(ReportingServer$<InstanceName>) instead of the reporting manager directory
(Reports$<InstanceName>).
7. Open Internet Explorer and enter the following address to view the SQL Reporting
Services Home page. [Link]
8. Click Audit Reports in the body of the page and then click Show Details in the upper
right part of the page.
9. Click the Db Audit data source.
10. In the Connect Using section, select Windows Integrated Security and click Apply.

Deploying Gateway Server in the Multiple

Server, Single Management Group Scenario
Gateway servers are used to enable agent-management of computers that are outside the
Kerberos Trust boundary of management groups, such as in a domain that is not trusted. The
gateway server acts as a concentration point for agent-to-management server communication.
Agents in domains that are not trusted communicate with the gateway server and the gateway
server communicates with one or more management servers. Because communication between
the gateway server and the management servers occurs over only one port (TCP 5723), that port
is the only one that has to be opened on any intervening firewalls to enable management of
multiple agent-managed computers. Multiple gateway servers can be placed in a single domain
so that the agents can failover from one to the other if they lose communication with one of the
gateway servers. Similarly, a single gateway server can be configured to failover between
management servers so that no single point of failure exists in the communication chain.
Because the gateway server resides in a domain that is not trusted by the domain that the
management group is in, certificates must be used to establish each computer's identity, agent,

101
gateway server, and management server. This arrangement satisfies the requirement of
Operations Manager for mutual authentication.

Note
To monitor computers that lie outside the management servers' trust boundary without
the use of a gateway server, you need to install and manually maintain certificates on the
management servers and the computers to be monitored. When this configuration is
used instead of using a gateway server, additional ports must be opened for agent-to-
management server communication. For a listing of all ports that are necessary, see
Agent and Agentless Monitoring and Operations Manager 2007 Supported Configurations
([Link]

High-Level Procedure Overview

High-level gateway server installation overview
1. Request certificates for any computer in the agent, gateway server, management server
chain.
2. Import those certificates into the target computers by using the Operations Manager 2007
[Link] tool.

Note
For information on obtaining and importing a certificate using an enterprise
certification authority, see [Link] For
information about using a stand-alone certification authority, see
[Link]
3. Distribute the [Link] to the gateway
server and the management server.
4. Install the gateway server.
5. Run the [Link] tool to initiate
communication between the management server and the gateway server.

Before You Start

Before you start
1. Deployment of gateway servers requires certificates. You need to have access to a
certification authority (CA). This can be a public CA such as VeriSign, or you can use
Microsoft Certificate Services. This procedure provides the steps to request, obtain, and
import a certificate from Microsoft Certificate Services.
2. Reliable name resolution must exist between the agent-managed computers and the
gateway server and between the gateway server and the management servers. This

102
 name resolution is typically done through DNS. However, if it is not possible to get proper
name resolution through DNS, it might be necessary to manually create entries in each
computer's hosts file.

Note
The hosts file is located in the \Windows\system32\drivers\etc directory, and it
contains directions for configuration.

Obtaining Computer Certificates from Microsoft Certificate

Services
For more information, see the sections How to Obtain a Certificate Using a Stand-Alone CA in
Operations Manager 2007 and How to Obtain a Certificate Using an Enterprise CA in Operations
Manager 2007" in the Security Guide at[Link]

Distributing the
[Link]
The [Link] tool is needed only on the
management server, and it only has to be run once.

To copy [Link] to management

servers
1. From a target management server, open the installation media \SupportTools directory.
2. Copy the [Link] from the
installation media to the Operations Manager 2007 installation directory, which is typically
c:\Program Files\System Center Operations Manager 2007.

Installing Operations Manager 2007 Gateway Server

This procedure installs the gateway server. The server that is to be the gateway server should be
a member of the same domain as the agent-managed computers that will be reporting to it.

Tip
An installation will fail when starting Windows Installer (for example, installing a gateway
server by double-clicking [Link]) on a computer running Windows
Server 2008 if the local security policy User Account Control: Run all administrators in
Admin Approval Mode is enabled (which is the default setting on Windows Server 2008).

To run Windows Installer from a command prompt for Windows Server 2008
1. On the Windows desktop, click Start, point to Programs, point to Accessories, right-click
Command Prompt, and then click Run as administrator.
2. In the Administrator: Command Prompt window, navigate to the local drive that hosts the

103
 Operations Manager 2007 SP1 installation media.
3. Navigate to the directory where the .msi is located, type the name of the .msi file, and
then press ENTER.

To install Operations Manager 2007 gateway server

1. Log on to the gateway server with Administrator rights.
2. From the Operations Manager 2007 installation media, navigate to the \gateway\
<platform> (i386 or amd64) directory.
3. Double-click the [Link] file to start the gateway server installation.
4. On the Welcome screen, click Next>.
5. On the Destination Folder page, accept the default, or click Change to select a different
installation directory, and then click Next>.
6. On the Management Group Configuration page, enter the target management group
name in the Management Group Name field, enter the target management server name
in the Management Server field, check that the Management Server Port field is 5723,
and then click Next>. This port can be changed if you have enabled a different port for
management server communication in the Operations Console.
7. On the Gateway Action Account page, select the Local System account option, unless
you have specifically created a domain-based or local computer-based gateway Action
account. Click Next>.
8. On the Microsoft Update page, indicate if you want to use Microsoft Update, and then
click Next>.
9. On the Ready to Install page, click Install.
10. On the Completing Installation page, click Finish.

Importing Certificates with the [Link] Tool

Perform this operation on each gateway server, management server, and computer that will be
agent-managed and that is in a domain that is not trusted.

To import computer certificates by using [Link]

1. Copy the [Link] tool from the installation media \SupportTools\<platform>
(i386 or ia64) directory to the root of the target server or to the Operations Manager 2007
installation directory if the target server is a management server.
2. Open a command prompt and change the directory to the directory where
[Link] is, and then run [Link] /SubjectName <certificate
subject name>. This makes the certificate usable by Operations Manager.

104
Registering the Gateway with the Management Group
This procedure registers the gateway server with the management group, and when this is
completed, the gateway server appears in the Discovered Inventory view of the management
group.

To run the gateway Approval tool

1. On the management server that was targeted during the gateway server installation, log
on with the Operations Manager Administrator account.
2. Open a command prompt, and navigate to the \Program Files\System Center Operations
Manager 2007 directory or to the directory that you copied the
[Link] to.
3. At the command prompt, run
[Link]
/ManagementServerName=<managementserverFQDN> /GatewayName=<GatewayFQDN>
/Action=Create

4. If the approval is successful, you will see The approval of server <GatewayFQDN>
completed successfully.

5. If you need to remove the gateway server from the management group, run the same
command, but substitute the /Action=Delete flag for the /Action=Create flag.
6. Open the Operations Console to the Monitoring view. Select the Discovered Inventory
view to see that the gateway server is present.

Configuring Gateway Servers for Failover Between Management

Servers
Although gateway servers can communicate with any management server in the management
group, this must be configured. In this scenario, the secondary management servers are
identified as targets for gateway server failover and the Clustered RMS is excluded from failover.
This is a typical best practice that is done to prevent unnecessary load on the RMS.
Use the Set-ManagementServer-gatewayManagementServer command in Command Shell, as
shown in the following example, to configure a gateway server to failover to multiple management
servers. The commands can be run from any Command Shell in the management group.

To configure gateway server failover between management servers

1. Log on to the management server with an account that is a member of the Administrators
role for the management group.
2. On the Windows desktop, click Start, point to Programs, point to
SystemCenterOperationsManager, and then click CommandShell.
3. In Command Shell, follow the example that is described in the next section.

105
Description
The following example can be used to configure gateway server failover to multiple management
servers.

Code
$primaryMS = Get-ManagementServer | where {your filter here}

$failoverMS = Get-ManagementServer | where {your filter here}

$gatewayMS = Get-ManagementServer | where {your filter here}

Set-ManagementServer -gatewayManagementServer: $gatewayMS -ManagementServer: $primaryMS -

FailoverServer: $failoverMS

Comments
In the preceding example, you must create a filter statement for the first three commands. The
following is an example of a filter command written to find the computer [Link] that
will be assigned to the $failoverMS variable:
$failoverMS = Get-ManagementServer | where {$_.Name –eq ’[Link]’ }

For help with the Set-ManagementServer command, type the following in the Command Shell
window:
Get-help Set-ManagementServer -full

Deploying the Connected Management

Groups Scenario
When you connect management groups, you are not actually deploying any new servers; rather
you are allowing a top tier or local management group to have access to the Alerts and Discovery
information that is in a bottom tier or connected management group. In this way, you can view
and interact with all the alerts and other monitoring data from multiple management groups in a
single console. In addition, you can run tasks on the monitored computers of the connected
management groups.
In this procedure, you create a connection between two management groups. These
management groups can be in the same domain, or they can be in trusted domains. You can
connect to management groups that are in domains that are not trusted, but you cannot view data
from those domains until you add an account from the domain of the local management groups to
an Operations Manager role for the connected management group. To do this, a trust must be
established between the domains.

106
Before You Start
Before you start
1. To connect management groups, you must provide the fully qualified domain name
(FQDN) of the root management server (RMS) of the connected management group. The
management server of the local management group must be able to resolve this FQDN.
If the two management groups do not use the same Domain Name System (DNS)
service, you must create a secondary DNS zone in the DNS service that the local
management group uses. This secondary DNS zone transfers the DNS information from
the primary DNS zone of the connected management group. The transferred information
is essentially a copy of the DNS information that is available to the management server of
the local management group. For more information about Zone Transfers, see the
"Understanding zones and zone transfers" topic in the Windows Server DNS help.
2. Add the SDK and Config Service account of the connected management groups to the
Operations Manager Administrator role for the connected management group, or just add
it to the domain-based Operations Manager Administrator security group in the connected
management groups domain, which has already been added to the Operations Manager
Administrator role.
3. Collect the SDK and Config Service account credentials from the connected
management groups. These credentials are needed when you add the connected
management group in the local management group.
4. Identify users in the domain of the local management group that will need access to data
from the connected management groups. They must be added to the appropriate
Operations Manager roles in the connected management group.
5. Both the connected management groups and the local management groups must be
running the same version of Operations Manager 2007. Mixing release versions is not
supported. For more information on how to upgrade connected management groups from
RTM to SP1, see the Operations Manager 2007 SP1 Upgrade Guide

Creating Connected Management Groups

To create a connected management group
1. Open the Operations Console on a management server that is a member of the local
management group using an account that is a member of the Operations Manager
Administrator role.
2. Open the Administration view, and select the Connected Management Groups object.
3. In the Actions pane, on the far right, click the Add Management Group link.

Note
If the Actions pane is not visible, click Actions on the toolbar.

107
 4. On the Add Management Group page, enter the name of the management group that
you want to connect to in the Management Group name field. This group is referred to
as the connected management group.
5. In the Root field, enter the FQDN of the RMS of the connected management group.
6. If the local management group and the connected management group are using the
same SDK and Config Service account, select Use SDK service account.

Important
The SDK account must be a member of the Operations Manager Administrator
role for the connected management group.
7. If the local management group and the connected management group are not using the
same SDK and Config Service account, then select Other user account, and complete
the User name, Password and Domain fields with the SDK account for the connected
management group.
8. The connected management group appears in the connected management groups
Results pane in the Operations Console.
9. Repeat this process for each management group that you want to connect.

Providing Access to Connected Management Groups

In order to view alerts, set overrides, and monitor objects in connected groups, the group scope
has to be set for user groups.

To grant access to Connected Management Groups

1. Identify users in the local management group that need access to the connected
management groups.
2. Add those users as members to the appropriate user role in the connected management
groups.

Note
If local and connected management groups are not in the same domain and
there is no trust relationship between the two domains, you will have to create
accounts in the connected management group domain for the users in the local
management group domain to use.
3. In the Operations Console for the local management group, in the Administration view,
expand Security, and then click User Roles.
4. In the right pane, right-click the user role to which you want to grant connected
management group access, and then click Properties.
5. On the Group Scope tab, select the connected management groups to which you want
to grant access to this user role, and then click OK. A user with both permission and
access to at least one connected management group will now see the Show Connected

108
 Alerts button in the toolbar of any Alert view in the Monitoring space.
6. A Log On dialog box appears and prompts the user for credentials (to log on to the
connected management groups). Enter the credentials, and then click OK. Alerts appear
from all connected management groups for which you have access and permission. You
can run tasks in the managed computers of connected management groups.

Operations Manager 2007 Post-Deployment

Tasks
After your management group infrastructure has been deployed and its health verified, it is ready
to use. To start using Operations Manager, there are two tasks that you must complete:
 Deploying agents to monitor computers
 Importing management packs so that the deployed agents know what to monitor
These tasks are covered in detail in the Operations Manager 2007 Operations Guide.
The purpose of this section is to outline the steps that are necessary to prepare your environment
for deploying agents or initiating agentless management and for importing management packs.

To prepare Active Directory Domain Services for Agents

1. Review the agent and agentless monitoring environmental prerequisites at Agent and
Agentless Monitoring.
2. For agents that are included in computer images, the agent configuration information can
either be entered manually or stored in an Active Directory Service Connection Point
(SCP). Connection points are created by using the [Link] tool located in the
Installation Media\SupportTools Directory. For information about how to use this tool, see
the topic "How to Create an Active Directory Domain Services Container for an
Operations Manager 2007 Management group" in the Operations Manager 2007 Help.

Note
Agents that are installed via a push install cannot make use of configuration
information that is stored in an Active Directory SCP.
3. In addition to this, you can place agent failover configuration information in the SCP by
using the Agent Assignment Failover Wizard. By using this wizard, you can designate
which management servers agents are allowed to use failover if the primary management
server is unavailable. You can use this technique to prevent agents from failing over to
the root manager server (RMS) of a management group. For information about how to
perform this operation, see the topic "How to Use Active Directory Domain Services to
Assign Computers to an Operations Manager 2007 Management group" in the
Operations Manager 2007 Help.

109
To prepare the Management Group for Agents
 By default, management groups do not automatically admit manually installed agents into
the management group to manage them. This is a security feature. The management
group, as a whole, and individual management servers can be configured to place new
manually installed agents into the Pending Management container, where an
administrator can then review them and either admit them into the management group or
reject them. It is also possible to change the default behavior and automatically admit
manually installed agents, although this is not recommended for security reasons. For
information about how to perform these steps, see the topic "How to Approve an
Operations Manager 2007 Agent Installed for a management group Using
[Link]" in the Operations Manager 2007 Help.

110