Installing MOM 2005 on a Single Computer

Authors: Py Bateman (S&T Onsite), John Hallows, James R. Morey

Program Managers: Harry Sinn, Travis Wright, Lorenzo Rizzi, Thomas Theiner

Published: June 2005

Applies To:   Microsoft Operations Manager 2005

Document Version:   Release 1.1

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

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.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.

2005 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Active Directory, ActiveSync, and Windows Mobile are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Acknowledgmen 828m126i ts

Primary Reviewers: Barry Webberley, Starr Parker, Bill Hodghead, Appireddy Kikkuru

Secondary Reviewers: Anandha Ganesan, Kerry Minietta, Stephanie Couch, Venkatesh Sargunesan, Janaina Bueno, Ramana Satyavarapu

Managing Editor: Sandra Faucett

Chapter 2

This chapter provides basic instructions for installing all Microsoft Operations Manager (MOM) 2005 components on a single computer to create a single management group. A management group consists of a MOM Database, at least one MOM Management Server, the MOM Administrator console, the MOM Operator console, and managed computers. Optionally, a management group can include the MOM Reporting Server and the MOM Web console.

If you have less than 200 computers to manage, you can accomplish this by installing all MOM 2005 components on a single computer. If the number of managed computers grows, you can expand your management group by installing additional Management Servers on additional computers.

If you need to manage more than 200 computers, or if you want to provide for agent failover, it is recommended that you install the MOM components on separate computers. With agent failover, agents on managed computers can report to another Management Server in the same management group if their primary Management Server becomes unavailable. For instructions for deploying MOM across multiple computers, see Chapter 3, "Deploying MOM 2005 across Multiple Computers."

For more information about which MOM configuration best suits your needs, see the Performance and Sizing Guide at https://go.microsoft.com/fwlink/?LinkId=46754.

In This Chapter

Before You Begin

Deployment Scenario Description

Deployment Phases

Installing the MOM Components

Discovering Computers and Deploying Agents

Installing MOM 2005 Reporting

Importing MOM 2005 Management Packs

Send feedback to the MOM Documentation Team: [email protected].

Before you begin deploying MOM, review the key concepts of MOM and your deployment design and planning documents. Areas to review include:

The MOM 2005 release notes to identify any changes that could affect planning for a new deployment.

The Performance and Sizing Guide at https://go.microsoft.com/fwlink/?LinkId=46754.

The Microsoft Operations Manager 2005 Security Guide.

The Microsoft Operations Manager 2005 Supported Configurations data sheet on the MOM 2005 CD

Verifying Software and Hardware Requirements

You can run the MOM Prerequisite Checker in MOM Setup to check the hardware and software prerequisites and to create a report that lists what your computer requires to run MOM 2005.

For complete information about hardware and software requirements, see Microsoft Operations Manager 2005 Supported Configurations data sheet located on the MOM 2005 CD.

Software requirements

Check the computer that will host the MOM components or a MOM agent to ensure that all the software requirements are met. If a computer does not have the required software, either remove it from your deployment plan or install the required software.

Hardware requirements

Check the computer that will host the MOM components or a MOM agent to ensure that the minimum hardware requirements have been met. If a computer does not meet the minimum hardware specification, either remove it from your rollout plan or upgrade it to the required hardware. Also verify that the available disk space on the computer falls within the supported guidelines for free disk space.

Verifying the MOM Service Accounts

There are three primary service accounts that MOM 2005 uses.

The Data Access Server (DAS) account provides centralized access to the MOM database.

The Management Server Action Account is used to run computer discovery and can be used to automatically install agents. The Management Server Action Account also enables a Management Server to communicate with, collect data from, and to run actions on, agentless-managed computers. It is also used to collect data from the registry, performance counters, and event logs of the local computer that the Management Server is installed on.

The agent Action Account is used by MOM to collect data from, and to run actions on, agent-managed computers.

For more information about these service accounts, see the Microsoft Operations Manager 2005 Security Guide.

MOM security groups required for the MOM Administrator and Operator consoles

MOM 2005 uses Windows security groups to assign and control access privileges to various MOM functionalities. You can grant a user access to use functions of the MOM consoles by making a user's domain account a member of the appropriate MOM user group on a Management Server. For more information, see the Microsoft Operations Manager 2005 Security Guide.

Calculating the size of the MOM Database

Database sizing depends on a number of factors:

The number of computers that you plan to manage.

The number of events, alerts, and performance data that you plan to collect.

The Management Packs that you plan to deploy.

The frequency for grooming the MOM database.

The maximum supported size for the MOM database is 30 GB. It is recommended that you use a smaller size if possible. For optimum performance, it is a best practice to keep your database size below 15 GB. A smaller database can respond more quickly to events and alerts.

Setup automatically sets the size of the log file to 20 percent of the size of the database file. For example, if you configure the database file size to be 2 GB, MOM sets the log file to 400 MB.

To best estimate the MOM 2005 database size that you need for a given number of managed computers, you should use the Performance and Sizing Guide at https://go.microsoft.com/fwlink/?LinkId=46754 to assist you in determining what size your database should be.

Preparing the hard disk drives

Identify any hard disk drives that will be used for the MOM database and transaction logs and verify that there is sufficient space allocated to accommodate the size requirements of the database and log files.

It is recommended that you install the Microsoft SQL ServerT database and log files for MOM on a different hard disk drive from the paging file, which is usually on the same hard disk drive as the operating system.

Because the MOM database is very active, with events and alerts continuously being added to and removed from it, MOM requires adequate CPU power and memory to keep the host computer performing optimally.

RAID arrays

Proper disk selection is especially important for operating an optimum MOM system. For best performance, install the MOM database on a RAID 10 array. RAID 10 provides high I/O rates by striping RAID 1 segments. If cost is not a concern and optimum performance is the key consideration, use RAID 1 or RAID 1+0 (RAID 10) for both the transaction log hard disk drive and the database hard disk drive.

RAID 10 delivers better performance because it requires only one additional write I/O operation for each write request (one write to each hard disk drive in the mirror). For example, a transaction at RAID 0 generates 10 reads and one write. The same transaction at RAID 1 or RAID 10 generates 10 reads and two writes. In contrast, using RAID 5, the same transaction generates 12 reads and two write operations.

For more information about the performance implications of database and log file location and RAID configurations, see the Performance and Sizing Guide at https://go.microsoft.com/fwlink/?LinkId=46754.

Deployment Scenario Description

The deployment scenario in this chapter describes how you can deploy a single management group. In this scenario, all MOM components are installed on the same computer, and that computer and all managed computers are in the same Windows domain. You can install the MOM components and agents in multiple domains. For more information about installing the MOM components and agents in multiple domains, see chapter 7 "Deploying MOM 2005 in Advanced Environments" in this guide.

Deployment Phases

It is recommended that you divide your deployment tasks into phases to ensure that each MOM is installed in the correct order. The recommended phases for creating the MOM configuration described in this chapter are:

Install the MOM 2005 server components.

Discover computers and deploy agents.

Install MOM 2005 Reporting (optional).

Import Management Packs.

Setup installs the MOM 2005 Management Pack automatically when you install the MOM Server components. You can import additional Management Packs from the MOM 2005 product CD after you have installed the Management Servers, deployed agents, and, optionally, installed MOM Reporting.

Installing the MOM 2005 Components

The MOM server components include the MOM database, Management Server, and user interfaces - the MOM Administrator console and the MOM Operator console.

Before installing the MOM database, you must first install and correctly configure SQL Server 2000 Service Pack 3a or later for use by the MOM database. You should also install all recommended hotfixes for SQL Server 2000 SP3a. If you are installing the MOM database on an existing SQL Server, you must verify that it is correctly configured.

A known issue might arise when MOM is bulk inserting data into the MOM database. A server process ID (SPID) might stop responding with a NETWORKIO (0x800) waittype and a constantly increasing waittime in SQL Server 2000 Enterprise Manager under Process Info or in the sysprocesses table in the master database. The only way to end the process is to remove the SPID.

You can obtain and install this hotfix:https://support.microsoft.com/default.aspx?scid=kb;en-us;884554

For more information about SQL Server configurations that have both SQL Server 2000 and SQL Server 7.0 installed, see article number Q300341 in the Microsoft Knowledge Base at https://go.microsoft.com/fwlink/?LinkId=33376. It is recommended that you review all articles related to SQL Server and MOM at https://go.microsoft.com/fwlink/?linkid=10716.

If you want to install the MOM Administrator console and the MOM Operator console on the Management Server, it is recommended that you set your display resolution to 1024 × 768, with 24-bit color.

For production installations, MOM 2005 supports only Microsoft SQL Server 2000 Service Pack 3.0a as the database for the MOM database.

SQL Server must be configured as follows:

Set database authentication to Windows only.

Set the SQL Server service account to run as Local System.

Set SQL Server to use TCP/IP Sockets for client connections.

If you are installing MOM on a computer that is already running SQL Server and SQL Server is not configured as described, use Enterprise Manager to change the settings.

Configuring Windows Services for SQL Server

Verify that both the SQL Server (MSSQLSERVER) and the SQL Server Agent (SQLSERVERAGENT) services are started and configured to start automatically when the computer starts.

Verifying SQL Server Installation

Open SQL Server Enterprise Manager on the local computer and verify that you can connect to the SQL Server instance (or instances) that you want to use and verify that the default SQL Server databases Tempdb, master, and msdb are installed.

Configuring Database Memory

A best practice is to install sufficient memory to meet the server's needs, but in limited memory situations it is important that you configure the database correctly for memory usage because in such situations, the computer processes can consume all the memory and cause page faults. By default, SQL Server dynamically adjusts its memory usage based on demand and available system resources. This means that SQL Server uses as much unallocated RAM as it requires, and then releases RAM when other resources need memory. To prevent this, you can limit the amount of memory that SQL Server uses by configuring the memory to be static, instead of dynamic.

If you must restrict the memory allocated to SQL Server, to calculate the fixed amount of memory that you should use, subtract the memory required by your operating system and any other critical services or SQL Server instances running on the computer, and then apply the remainder to the fixed memory setting.

To configure SQL Server memory

Open SQL Server Enterprise Manager.

Expand Microsoft SQL Servers, and then expand SQL Server Group.

Right-click the server that you want to configure, and then click Properties.

On the Memory tab, click Use a fixed memory size (MB) and move the slider to specify the amount of RAM that you want to allocate for SQL Server.

The correct installation of the MOM database is very important. If installed incorrectly, the consequence is poor performance.

Some MOM Database installation best practices are as follows:

Before installation, see the Performance and Sizing Guide at https://go.microsoft.com/fwlink/?LinkId=46754 to assist you in determining what size your database should be.

Install the SQL Server database and log files for MOM on a different hard disk drive from the paging file, which is usually on the same hard disk drive as the operating system.

Install the MOM database (EeaData.mdf) and log files (EeaLog.ldf) on separate hard disk drives for greater efficiency.

For more information about configuring SQL Server to avoid possible slow performance of the MOM database, see article number Q295836 in the Microsoft Knowledge Base at https://go.microsoft.com/fwlink/?LinkId=33377.

It is recommended that you review all articles related to SQL Server and Operations Manager at https://go.microsoft.com/fwlink/?linkid=10716.

To install the MOM components on one computer

Log on to the computer on which you want to install MOM using an account with administrative credentials. This account must have at least "DBO" privileges on the master and msdb databases on the SQL Server instance as well.

Close all open applications.

On the MOM 2005 product CD, double-click setup.exe.

In the Microsoft Operations Manager 2005 Setup Resources dialog box, on the Setup Tasks tab,, click Install Microsoft Operations Manager 2005 to start the MOM 2005 Setup Wizard.

On the Installation Options page, click Typical, and then click Next. The Typical installation options installs the MOM database, Management Server, and consoles.

The Prerequisite Check page indicates whether you have met all the requirements for installing the MOM components.

On the SQL Server Database Instance page, select the server instance in the SQL Server database instance list on which you want to install the MOM database.

On the Database and Log File Options page, type the initial size of the MOM database; the default setting is 1 GB (1,000 MB). To change the default installation location of either the data file or the log file (recommended, see the note below), click Advanced, and then click the appropriate Change button.

On the Management Group Name page, type the name that you want to use for the management group. This name represents the database; you can use a name (consisting of alphanumeric characters) of your choice but each management group name should be unique within your MOM environment. A best practice for large systems is to use a naming convention to establish the management groups.

On the Management Server Action Account page, enter the account that you want the Management Server to use to push-install agents on remote computers. If you are using this account to push-install agents on remote computers, it must have administrative privileges on all target computers. If you are not using this account to push-install agents, then this account can be a local user account. For more information, see the Microsoft Operations Manager 2005 Security Guide.

On the Data Access Server Account page, enter the domain account that you want MOM to use to log onto and communicate with the MOM database.

On the MOM Error Reporting page, select the Enable error reporting check box (optional).

If you want MOM to automatically send service error reports to Microsoft, enable error reporting. It is recommended that you use the default Automatically send error reports to Microsoft option. If you choose the Queue error reports and let me approve sending them to Microsoft option, MOM stores error reports on the computer where they occur. The next time that you log onto that computer, a dialog box appears, which you can use to send the accumulated reports.

For more information about error reporting, see the Microsoft Data Collection Policy at https://go.microsoft.com/fwlink/?LinkId=23437.

On the Active Directory Configuration page, select the appropriate option for your environment and for this management group.

If all computers for this management group are in Active Directory domains that trust each other, choose Yes so that MOM can use mutual authentication for all communication between Management Servers and agents. Otherwise, choose No. For more information, see the Microsoft Operations Manager 2005 Security Guide.

On the Ready to Install page, click Install.

On the Last page, leave the Start the MOM Administrator console checkbox selected and click Finish. This will complete setup and then open the MOM 2005 Administrator console so that you can discover computers and install agents on them.

Before you begin deploying agents, determine which computers you want MOM to discover and manage with MOM agents.

For detailed information about discovering computers and deploying agents, see Chapter 4, "Discovering Computers and Deploying Agents."

The MOM Reporting Server includes the MOM Reporting database and a scheduled job that periodically transfers data from the MOM database to the MOM Reporting database. You can then use the MOM Reporting console to run and view MOM reports that use data from the MOM Reporting database. The MOM Reporting console runs within the SQL Server 2000 Reporting Services by using a supported browser.

The MOM Reporting database and the MOM database can be on the same computer or on separate computers, on the same SLQ Server instance or another instance. For optimum performance, especially in a large network environment, it is recommended that you install MOM Reporting a dedicated computer.

For detailed instructions about installing MOM Reporting, see Chapter 5, "Deploying MOM 2005 Reporting."

When you install MOM 2005, the MOM Management Pack is automatically installed. After you have installed all the agents within a management group to MOM 2005, you can import other MOM 2005 Management Packs.

For detailed instructions about importing MOM 2005 Management Packs, see Chapter 6, "Deploying MOM 2005 Management Packs."