Export (0) Print
Expand All

Supported Configurations

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Microsoft Corporation

Updated: June 2003

Click here to download a copy of this paper

On This Page

Overview
Support Matrix
Typical Configuration
Scalability
Networks
Availability
Localization/Globalization
Configurations Supported
Security
Agent Management Functionality
Providers and Varset
No Support List

Overview

This document provides information about supported configurations, sizing, and functionality for Microsoft® Operations Manager 2000 (MOM) Service Pack 1 (SP1) deployments. Updates to this document will be posted to the Web at http://www.microsoft.com/windows/reskits/

Revised in this update

  • Supported Installations of Operating Systems (MOM SP1)

Added a note that MOM includes a basic agent for computers running Windows NT Server 4.0 and that NetIQ offers a full-featured Windows NT 4.0-based agent.

Management Maturity

MOM can be used only in IT environments where the organization, processes, and management support the active monitoring of servers. This means having or creating a Network Operations Center or Systems Operations Center, where support individuals are assigned to round-the-clock monitoring duties. In a smaller setting, it might mean having a few administrators who are required to at least check on the status every few hours.

Also, the monitoring organization should be empowered to install agents and rules on the monitored servers and have the appropriate security accounts to do so. Many IT shops use security as a way to disallow monitoring of their servers. Without the empowerment, the monitoring team will not succeed in deploying MOM in these environments.

MOM provides monitoring for Windows-based servers and infrastructure. However, MOM does not deliver real-time heartbeat monitoring of a managed computer’s network accessibility. You must continue to use network monitors, pingers, or both to report on network and systems availability within seconds. These tools can report alerts to MOM.

Support Matrix

The following table lists supported operating systems for MOM SP1.

Supported Installations of Operating Systems (MOM SP1)

Operating system

Managed computer

Agent Mgr Consolidator DAS (DCAM)

Database server

MOM Administrator console

MOM Web console 2

Windows NT Server 4.0 SP4 or later

supcon01 1

 

supcon02

 

supcon02

 

supcon02

 

supcon02

Windows 2000 Professional SP1

 

supcon01

 

supcon02

 

supcon02

 

supcon02

 

supcon02

Windows 2000 Professional SP2 or later

 

supcon01

 

supcon02

 

supcon02

 

supcon01

 

supcon02

Windows 2000 Server SP1

 

supcon01

 

supcon02

 

supcon02

 

supcon02

 

supcon02

Windows 2000 Server SP2 or later

 

supcon01

 

supcon01

 

supcon01

 

supcon01

 

supcon01

Windows 2000 Datacenter Server SP1

 

supcon01

 

supcon02

 

supcon02

 

supcon02

 

supcon02

Windows 2000 Datacenter Server SP2 or later

 

supcon01

 

supcon01

 

supcon01

 

supcon01

 

supcon01

Windows 2000 Advanced Server SP1

 

supcon01

 

supcon02

 

supcon02

 

supcon02

 

supcon02

Windows 2000 Advanced Server SP2 or later

 

supcon01

 

supcon01

 

supcon01

 

supcon01

 

supcon01

Windows Server 2003, Standard Edition

 

supcon01

 

supcon01

 

supcon01

 

supcon01

 

supcon01

Windows Server 2003, Datacenter Edition

 

supcon01

 

supcon01

 

supcon01

 

supcon01

 

supcon01

Windows Server 2003, Enterprise Edition

 

supcon01

 

supcon01

 

supcon01

 

supcon01

 

supcon01

Windows Server 2003, Web Edition

 

supcon01

 

supcon01

 

supcon02

 

supcon01

 

supcon01

Windows XP Professional

supcon01 3

 

supcon02

 

supcon02

 

supcon01

 

supcon02

Windows XP Professional SP1

supcon01 3

 

supcon02

 

supcon02

 

supcon01

 

supcon02

Windows XP Home Edition

 

supcon02

 

supcon02

 

supcon02

 

supcon02

 

supcon02

1. MOM includes a basic agent for computers running Windows NT Server 4.0. This agent does not collect Application event log events, WMI data, and some performance counters. NetIQ offers a full-featured Windows NT 4.0-based agent that provides the same functionality as the MOM agent on computers running Windows 2000. The NetIQ Extended Management Pack for Windows NT 4.0 extends MOM functionality to the Windows NT 4.0 operating system. For more information, contact NetIQ.

2. You must install the Web console on a DCAM server. To access the Web console from a remote computer requires Internet Explorer 4.01 SP2 or later.

3. MOM supports the monitoring of Windows XP by using the MOM Management Pack and custom-developed rules.

Note: Setup does not specifically halt installation on any unsupported platforms.

Supported Upgrade Paths

MOM SP1 supports upgrades from the following final releases:

  • MOM to MOM SP1

  • MOM SP1, beta version, to MOM SP1

  • MOM with Application Management Pack to MOM SP1

  • MOM with Application Management Pack and SP1, beta version to MOM SP1

  • NetIQ Operations Manager 3.3 SP2 or NetIQ Operations Manager 3.22 SP1

If you have a full installation of either the Select or evaluation version of MOM SP1, upgrade NetIQ Operations Manager products the same way as upgrading from MOM to MOM SP1.

Minimum Hardware Requirements

To use MOM SP1, you must have:

  • Computer with 550 MHz or higher Pentium-compatible CPU, minimum (effectively manages up to 20 computers).

  • 512 MB of RAM, minimum (more memory improves performance).

  • Hard disk drive with 5 GB of available space depending on the MOM SP1 components installed. The size of MOM SP1 components is:

    • MOM Administrator console: 52 MB

    • Database: 500 MB

    • MSDTC: 512 MB

    • Log file: 100 MB

    • MOM Reporting: 50 MB

    • DCAM only: 145 MB

    • DCAM with Web console: 150 MB

  • CD-ROM drive.

  • Super VGA with 800 x 600 or higher-resolution monitor.

  • Microsoft Mouse or compatible pointing device.

  • 10 MBPS network connection.

For each managed computer, you must have:

  • Computer with 200 MHz or higher Pentium-compatible CPU, minimum.

  • 64 MB of RAM, minimum (more memory might be needed depending on the number of Management Packs deployed to the computer).

  • 100 MB of available hard-disk space.

Additional items or services required for using certain features:

  • Access to the Internet, which might require payment or a separate fee to an Internet service provider.

Minimum Software Requirements

To use MOM SP1, you must have:

  • Operating system:

    • Microsoft Windows Server 2003, Standard Edition

Windows Server 2003, Datacenter Edition

  • Windows Server 2003, Enterprise Edition

  • Windows Server 2003, Web Edition

  • Windows 2000 Server

  • Windows 2000 Advanced Server

  • Windows 2000 Datacenter Server

    Note: For the appropriate Service Pack requirements, refer to the "Supported Installations of Operating Systems (MOM SP1)" table earlier in this document.

  • For production environments, Microsoft SQL ServerTM 2000 Standard or SQL Server 2000 Enterprise Edition or later recommended (latest service pack recommended). Ensure that all hotfixes have been applied.

  • For non-production environments, Microsoft Data Engine (MSDE), which has a 2 GB database size limit.

  • Microsoft Outlook 98 or later, if you want to send e-mail notifications (Exchange Server required).

  • Microsoft Management Console (MMC) version 1.1 or later for the MOM Administrator console.

  • Microsoft Office Graph Component for the MOM Reporting server.

  • Microsoft Access Snapshot View Control (Snapview.ocx) for the MOM Reporting server.

  • Microsoft Access RunTime 2000 (provided on the MOM product CD) or Microsoft Access 2000 of later for the MOM Reporting server.

  • Microsoft Data Access Component (MDAC) version 2.6 or later for the MOM Reporting server.

  • Microsoft Internet Explorer 4.01 SP2 or later to access the MOM Web console.

All software requirements are included on the MOM product CD, except operating system and Internet Explorer software, Exchange Server, SQL Server, Outlook, Access 2000, and the Microsoft Office Graph component, which are sold separately.

For each managed computer, you must have:

  • Operating system:

    • Windows Server 2003, Standard Edition

    • Windows Server 2003, Datacenter Edition

    • Windows Server 2003, Enterprise Edition

    • Windows Server 2003, Web Edition

    • Windows 2000 Server

    • Windows 2000 Advanced Server

    • Windows 2000 Datacenter Server

    • Windows NT Server 4.0, with SP4 or later

      Note: MOM includes a basic agent for computers running Windows NT Server 4.0. This agent does not collect Application event log events, WMI data, and some performance counters. NetIQ offers a full-featured Windows NT 4.0-based agent that provides the same functionality as the MOM agent on computers running Windows 2000. The NetIQ Extended Management Pack for Windows NT 4.0 extends MOM functionality to the Windows NT 4.0 operating system. For more information, contact NetIQ.

    • Windows NT Server 4.0, Enterprise Edition, with SP4 or later

    • Windows XP Professional

    • Windows XP Professional, with SP1 or later

  • Windows Management Instrumentation (WMI) installed.

Typical Configuration

Use the "Performance and Sizing"s white paper to determine the actual size of computer, networks, database, etc. Use the database calculators in Appendix C of this white paper to set up grooming rates. For example, a configuration needed to manage 250 servers, with room to grow, would look like this:

System Type

DCAM

Processor Count

2

Processor Type

550 MHz Pentium 3

Memory

1 GB

Disk Count OS

1 × 9.1 RAID 0, 2 × 9.1 RAID 1

Disk Designation OS + MOM

C: Drive (9.1 GB)

Network Capacity

100 Mbits, 12.5 MB

System Type

MOM Database

Processor Count

2

Processor Type

550 MHz Pentium 3

Memory

1 GB

Disk Count OS

1 × 9.1

Disk Designation OS + MOM

C: Drive (9.1 GB)

Disk Designation DB + Log (or separate optional log disk)

D: Drive (6 × 9=54 GB), RAID 0+1

Database Size (+ Log)

12 GB

DB IO Capacity

840 Read Write/sec

Network Capacity

100 Mbits, 12.5 MB

Supported Installation Combinations

This information describes which MOM SP1 and MOM components are supported in a rolling upgrade scenario (upgrading in a distributed environment, without shutting down monitoring for the upgrade). Anything not specifically stated is not supported. The scenarios are divided into three sections, depending on whether your MOM database is a MOM version, a MOM SP1 installation, or a MOM to MOM SP1 upgrade.

MOM Database

This database is supported with a MOM DCAM and all MOM components.

MOM SP1 Installation of Database

This database is supported with either a new installation of an MOM SP1 DCAM or an upgraded MOM SP1 DCAM and the following components:

  • All MOM SP1 components

  • MOM agents

  • Imported MOM Management Packs

MOM SP1 Upgraded Database

This database is supported with a MOM DCAM and the following components:

  • MOM Reporting

  • MOM SP1 Reporting

  • MOM SP1 MOM Administrator console

  • MOM agents

  • MOM SP1 agents

  • Imported MOM Management Packs

  • Imported MOM SP1 Management Packs

This database is supported with a MOM SP1 new installation of DCAM and the following components:

  • All MOM SP1 components

  • MOM agents

  • Imported MOM Management Packs

This database is supported with a MOM SP1 upgraded database and the following components:

  • All MOM SP1 components

  • MOM agents

  • Imported MOM Management Packs

Scalability

  • Maximum managed computers per DCAM: 1000

  • Maximum DCAMs per configuration group: 10

  • Maximum zone configuration groups per master configuration group: 10

  • Maximum alerts to the top tier (alert forwarding): 120,000 per day

  • Maximum tiers for alert forwarding: 2

  • Maximum MOM Administrator consoles per DCAM: 15

  • Maximum MOM Web consoles per DCAM: 15

  • Maximum reporting subsystems per database: 1

  • Maximum partitions per configuration group: 6

  • Maximum DCAMs per partition for N+1 failover: 6

  • Maximum agents per configuration group: 2000

  • Maximum size of MOM database: 30 GB

  • Maximum active DCAMs per agent: 4 for multi-homing (Multi-homing can expand the memory usage on an agent to a level beyond what the MOM Agent Performance Processing Rule thresholds are set for. You must increase the threshold size to avoid getting error messages).

Note: See the "Performance and Sizing" white paper for specifications of test workloads and test results. See Appendix C of this white paper for database calculators and their usage. The "Performance and Sizing" white paper is located on the MOM Web site at http://www.microsoft.com/mom/techinfo/administration/perfsize.asp.

Networks

Agent—DCAM—LANs 10/100/1000 megabits, WANs 64k-OC12, Firewalls, Dial up. Agent Manager functionality is not supported in environments such as satellite-based networks.

  • DCAM—DB—LANs 10/100/1000 megabits, WANs 64k-OC12

  • DCAM—DCAM (alert forwarding)—LANs 10/100/1000 megabits, WANs 64k-OC12, Firewalls (special installation instructions apply before separating DCAMDCAM with a firewall.)

Availability

Network Failures

  • Agent—DCAM: The agent stores data up to the buffer limits, sends data on a reconnect of the agent to the DCAM, and sends alerts for heartbeat failure. Local actions occur based on cached rules.

  • DCAM—DB: DCAM stops taking data from agents.

  • DCAM—DCAM: DCAM stops sending alerts. Local data collection, heartbeats, and rules deployment continue. If network recovers before queues overflow, cached alerts are forwarded.

Managed Computer Failures/Outages/Unavailability

  • Agent Failure: Alerts are sent for heartbeat failure. When the managed computer starts, service is automatically restarted.

  • DCAM Failure: The agent fails over to an alternative DCAM in the configuration group or partition, but no events or alerts are lost. The heartbeat resumes. If there is no failover DCAM, the DCAM failure is treated as a network failure by the agent. Alert forwarding stops.

  • Database Server Failure: The DCAM stops all activity; agents store data locally and take actions.

Localization/Globalization

Localization/Globalization Support

With MOM SP1, robust localization and globalization support has been added to the product.

MOM SP1 itself has not been localized and is still shipped in English only. However, the use of localized strings in Management Pack modules is now supported. This means that Management Pack authors can create Management Pack modules that contain completely localized customer and company knowledge. Rule objects can also be defined by using non-English characters.

From a globalization support perspective, significant improvements that enable installation and use of MOM components on non-English operating systems have been introduced. Management of managed computers using localized versions of Windows operating systems and applications is also supported.

Supported Languages: Operating Systems and Applications

The table below indicates the operating system and application language support that MOM SP1 provides. MOM SP1 components can be installed and used on any of the languages that are marked with a checked box. Management of operating systems and applications in any of the languages marked with a checked box is also supported.

Language

Support

Language

Support

Arabic

 

supcon03

Hungarian

 

supcon01

Brazilian

 

supcon01

Italian

 

supcon01

Bulgarian

 

supcon01

Japanese

 

supcon01

Chinese (Simplified)

 

supcon01

Korean

 

supcon01

Chinese (Traditional)

 

supcon01

Latvian

 

supcon01

Chinese (Hong Kong)

 

supcon01

Lithuanian

 

supcon01

Croatian

 

supcon01

Norwegian

 

supcon01

Czech

 

supcon01

Polish

 

supcon01

Danish

 

supcon01

Portuguese

 

supcon01

Dutch

 

supcon01

Romanian

 

supcon01

English

 

supcon01

Russian

 

supcon03

Estonian

 

supcon01

Slovak

 

supcon01

Finnish

 

supcon01

Slovenian

 

supcon01

French

 

supcon01

Spanish

 

supcon01

German

 

supcon01

Swedish

 

supcon01

Greek

 

supcon01

Thai

 

supcon03

Hebrew

 

supcon03

Turkish

 

supcon01

supcon01 IS supported on the relevant language.

supcon03 IS NOT supported on the relevant language.

Supported Configuration Guidelines

Although the "Supported Languages: Operating Systems and Applications" section in this paper lists the languages supported for MOM SP1, there are some guidelines that you should follow when you configure your MOM SP1 infrastructure. There are two configuration scenarios and guideline sets that you should understand and consider before you plan your deployment of MOM SP1 into environments where localized operating systems and applications exist. These include:

Multi-Language Mode

  • For maximum language flexibility for managing computers.

  • Must run English versions of Windows operating systems, MSDE, or SQL Server on core MOM infrastructure. This means the operating systems used for the DCAM and the database server must be English. Additionally, the database server component (SQL Server 2000) must also be English.

  • Supports deployment and use of MOM agents on managed computers that are running any supported localized operating system language.

Single Language Mode

  • For standardizing on a single language version across an enterprise.

  • Must run the same language version of Windows operating systems, MSDE, or SQL Server on core MOM infrastructure (DCAM server and database server).

  • Supports deployment and use of MOM agents on managed computers that are running a single localized operating system language.

Globalization Issues in MOM SP1

Although MOM SP1 provides greatly improved international support, there are some issues that have not been resolved for MOM SP1. These issues include the following:

  • Setup does not support special or double-byte characters.

  • Discovery does not detect or deploy agents to computers whose name or domain consists of special or double-byte characters.

These issues have been documented with additional details in the MOM SP1 release notes.

Configurations Supported

  • DAS, Consolidator, Agent Manager, database, MOM Web console, MOM Administrator console, agent, Reporting, and browser, all on one computer.

  • Database can be on a different computer.

  • Managed Agents are always on a different computer, except for the DCAM or Database/DCAM monitoring.

  • Reporting can be on a different computer (a recommended practice).

  • MOM Administrator console can be on a different computer.

  • Browser can be on a different computer.

  • Database can be shared with a DCAM using either the same or a different service account.

  • Agent can report to one or more DCAMs (maximum of 4) either in the same configuration group (failover configuration) or in different configuration groups (multi-homing).

  • MOM SP1 database can be installed on a SQL Server cluster in Active/Passive mode only (for database failover). Other applications can run in Active/Active mode on the same SQL Server cluster as the MOM database.

Security

For a secure operation, MOM requires the following further restrictions:

  • Physical and password protected DCAM servers and MOM database servers

  • Secure networks between DCAM and managed computers

  • Secure managed computers

Agent Management Functionality

Agent Manager functionalities include discovery, agent push install, and classification into different computer groups.

  • Agent Manager functionalities are not supported on agents within a workgroup environment.

  • Agent Manager functionalities are not supported on agents within a non-trusted domain environment.

  • Agent Manager functionalities are not supported in a forest trust environment.

Providers and Varset

MOM supports incoming data from WMI, Windows NT logs, application logs, system logs, and Service Control Manager (SCM). However, if data is coming in from many SNMP devices, funnel the devices into MOM through an SNMP collector computer.

WMI providers can provide data, but you should be aware that WMI events that are generated when the MOM agent is down could be lost.

Varsets are stored either locally or per DCAM. A service recycle at the agent will lose any local varset state, and a DCAM recycle will lose the DCAM varset state. Scripts that use the varsets would be affected.

Consolidation is supported only up to the first 25 parameters.

No Support List

  1. There is no support for Alpha.

  2. There is no support for multiple paging services when direct paging is being done.

  3. There is no support for Outlook XP without creating policy changes on the mail server.

  4. There is no support for DAS-CAM separation.

  5. There is no support for 64-bit agents.

  6. There is no support for installing a DCAM on a domain controller.

  7. There is no support for the MOM Web console installed on a separate server.

  8. There is no support for installing agents in computers that have the same name and are in two separate forests.

  9. There is no support for running the MOM SP1 database on a SQL Server cluster in Active/Active mode, which means that you cannot have more than one instance of the MOM database running on the same cluster. Other applications can run in Active/Active mode on the same SQL Server cluster as the MOM database.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft