4 Maintain2005

Microsoft
Operations
Manager 2005
Operations Guide
Maintain
Authors: Anat Kerry, Brenda Carter, Alicia Burmester
Program Managers: Thomas Theiner, Tom Keane, Travis Wright
Published: December 2004
Applies To: Microsoft Operations Manager 2005
Document Version: Release 1.0
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.
 2004 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.
Acknowledgments
Primary Reviewers: Thomas Theiner, Starr Parker, Stephanie Couch, Bill Hodgehead,
Bill Morchin
Managing Editor: Sandra Faucett
Did you find this information useful? Please send your suggestions and comments about
the documentation to momdocs@microsoft.com.
Looking for more MOM information? Experience the power of customer communities!
MOM Community
Maintain
C H A P T E R 4
Introduction
This chapter provides information and guidance to help you maintain a healthy Microsoft
Operations Manager (MOM) 2005 environment, and it also provides maintenance tasks for
specific MOM components.
In This Chapter
• Task Lists
• Tasks Not Supported
• Changing Passwords, Logins, and Accounts
• Maintaining the MOM Management Server
• Maintaining the MOM Database
• Maintaining the MOM Reporting Server and Reporting Database
• Maintaining MOM Agents
• Patches for MOM 2005
• Additional Resources
Send feedback to the MOM Documentation Team: momdocs@microsoft.com.
MOM Community
6 Chapter 4 Maintain
Task Lists
These are the recommended maintenance tasks, based on frequency:
• Daily
• Weekly
• Monthly
• Ad hoc
More information about performing these tasks can be found later in this chapter, and in other
chapters within this guide.
Table 4.1 Daily Tasks
Task Description
Check the Pending Actions node of For more information about
the MOM Administrator console for monitoring MOM agent installation,
computers awaiting agent see the “Monitoring MOM” section in
installation or uninstallation. Chapter 3 of this guide, “Monitor”.
Use the MOM Operator console to For more information about setting
monitor issues with MOM up the monitoring environment and
components. monitoring MOM components, see
Chapter 3 of this guide, “Monitor”.
Perform an incremental backup of For more information about backup,
the MOM Operational Database see Chapter 5, ‘Backup and Restore”.
(Onepoint).
Table 4.2 Weekly Tasks

Task Description
Perform a full backup of the MOM For more information about backup,
Operational database (Onepoint). see Chapter 5, ‘Backup and Restore”.
Perform an incremental backup of For more information about backup,
the MOM Reporting database see Chapter 5, “Backup and
(SystemCenterReporting). Restore”.
Table 4.3 Monthly Tasks

Task Description
MOM Community
Maintaining the MOM Reporting Server and Reporting Database 7
Perform a full backup of the MOM For more information about backup,
Reporting database see Chapter 5, “Backup and
(SystemCenterReporting). Restore”.
Backup Management Packs and For more information about backup,
Reports (.xml and .akm files) see Chapter 5, ”Backup and
Restore”.
Table 4.4 Ad Hoc Tasks

Task Description
Change the Action Account See “Changing the Action Account
password. Password”, later in this chapter.
Change the agent Action Account See “Changing the Agent Action
password and/or login. Account Password/login”, later in this
chapter.
Change the DAS Account or account See “Changing the DAS Account”,
password. later in this chapter.
Configure the Web console as Read- See “Configuring the Web console as
only. Read-only”, later in this chapter.
Configure the agent Action Account See “Granting Management Pack-
with Management Pack-specific specific Permissions to the Action
permissions. Account in a Lockdown Security
Environment”, later in this chapter.
Change passwords for running the See “MOM Reporting”, later in this
MOM Reporting Scheduled task. chapter.
Grant users access to view Reports. See “MOM Reporting”, later in this
chapter.
Modify settings for Microsoft error See “Modify Settings for Microsoft
reporting. Error Reporting”, later in this
chapter.
Add or remove a Management See “Adding and Removing
Server. Management Servers”, later in this
chapter.
Change the agent communication See “Changing the Agent
port number. Communalization Port Number”,
later in this chapter.
Change the agent control level of See “Changing the Agent Control
MOM Community
manually installed agents. Level of Manually Installed Agents”,

Configure agents to report to a See “Configuring an Agent to Report
different primary Management to a Different Primary MOM
Server. Management Server”, later in this
chapter.
Migrate agents to a new See “Migrating Agents to a New
management group. Management Group”, later in this
chapter.
Migrate agents across domains. See “Migrating Agents Across
Domains”, later in this chapter.
Renaming a MOM agent computer. See “Renaming a MOM Agent
Computer”, later in this chapter.
Removing orphaned agents. See “Removing Orphaned Agents”,
Apply a MOM 2005 patch. See “Patching MOM 2005”, later in
this chapter.
SQL Reporting Database Back up as often as needed,
(ReportServer) depending on how often reports
change in your organization, or back
up after significant changes to report
definitions (additions, changes and
deletions).
For more information about backup,
see Chapter 5, ‘Backup and Restore”.
Master Database (Master) Perform a full backup after installing
and configuring the MOM database
components, and after making
significant changes to logons or
other security changes.
Perform an incremental backup only
if you change the scheduled
SQL Server Agent jobs that MOM
uses.
see Chapter 5, “Backup and
Restore”.
MSDB Database (MSdbdata) Perform a full backup only after first
MOM Community
installing and configuring the MOM

database components.
Perform an incremental backup only
if you change the scheduled
SQL Server Agent jobs that MOM
uses.
Management Packs and Reports Back up after performing any
(.xml and .akm files) significant changes. You only need to
back up the changed Management
Packs.
see Chapter 5, “Backup and
Restore”.
File Transfer files Back up as needed.
see Chapter 5, ‘Backup and Restore”.
Manually run the DTS package to As needed, or to move smaller
move data packets of data. For more
information, see “Reporting Server
and Reporting Database”, later in
this chapter.
Tasks Not Supported

The following operational tasks are not supported for MOM 2005:
• Renaming the MOM Management Server
• Renaming the MOM database server
• Moving the MOM Management Server or the MOM database server to a different domain.
• Changing agent-related registry settings on managed computers. Instead, use the MOM
Administrator console to change agent settings.
MOM Community
Changing Passwords, Logins,

and Accounts
Because MOM uses domain accounts for some of its components and tasks, and global policies
can force domain account passwords to expire periodically, you must update these passwords for
these specific components and tasks. You might also want to change these passwords regularly,
as part of your IT policy for security, or for other reasons.
You can also change the accounts used by some MOM components.
The sections below discuss changing these passwords. For more information about the accounts
that MOM uses, see the MOM 2005 Security Guide.
MOM Management Server

The MOM Service on the Management Server uses the Local System or Network Service
account (running Windows Server 2003). Because this account is immune to forced password
changes, you do not need to change the password.
The Management Server Action Account, however, must be a domain account and is, therefore,
affected by password policy.
Changing the Action Account password

Because the Action Account must be a domain user account to access Active Directory®, its
password might expire or be forced to change by Global Policy. You can use the
SetActionAccount.exe tool, in the %Program Files%\Microsoft Operations Manager 2005
directory, to change the password, as follows:
SetActionAccount.exe <management group> [options]
Options:
-query //returns the current Action Account settings for the specified
management group.
-set <domain> <username> //sets the Action Account for the specified management
group. Note - the tool will prompt you for the new password.
Note - the management group must be specified, even if the agent is not
multihomed.
MOM Community
Note
You must restart the MOM Service on the computer to
complete this change, or any other permission change to the
Action Account.
Changing the DAS account

You can specify a different account or change the DAS account password at any time; however,
if you do, you also need to do the following:
• Change the account settings on the Identity tab of the Microsoft Operations Manager Active
Operations Data Access Service COM+ application on the Management Server.
• If you are using a different account, you must also add that account as a SQL Server™
Security Login with “Permit” server access.
• Give the db_owner Account access to the OnePoint database on the MOM database server, if
you are using a different account. MOM setup grants the DAS account this access by default.
• If you also have the MOM to-MOM Product Connector installed, add the account to the
MOM Service security group on the Management Server.
Note
You must restart the COM+ application to commit the
changes.
Configuring the Web Console As Read-Only

You can configure the Web console to be Read-only, so that operations data can be seen, but tasks
cannot be run and changes cannot be made. This setting does not affect the Operator console
read/write access.
To enable or disable Read-Only access for the Web Console
1. On the server hosting the Microsoft Operations Manager 2005 Web console application,
open the %INSTALLDRIVE%\ Program Files\Microsoft Operations Manager
2005\WebConsole\web.config file in a text editor.
2. In the <appSettings> node, change the node “” to
“<add key="Readonly" value="true"/>”.
3. Restart the Microsoft Operations Manager 2005 Web console application in the Internet
Information Services (IIS) snap-in.
MOM Community
Database
Changing the DAS Account
The DAS Account changes must be made on the Management Server that connects to the MOM
database.
Using the Network Service Account for DAS

Windows Server 2003 supports the Network Service Account, which is a predefined local
account that is used to start a service, and provide the security context for that service. The name
of the account is NT AUTHORITY\NetworkService. The Network Service Account has limited
access to the local computer, and authenticated access to network resources (similar to the
Computer Account).
You can use this account, rather than a local, or domain, user account, for the DAS security
context to lower the privileges, under which the DAS functions, and to avoid policy-driven
password expirations.
To use Network Service for DAS

This process requires procedures to be completed on both the MOM database server and the
MOM Management Server.
Important
You can only do this if the Management Server is running on
Windows Server 2003. Windows 2000 does not support the
Network Service Account.
On the MOM Database Server:

1. On the MOM Database Server, verify that the MSSQLSvc Service Principal Name is
registered by using “setspn.exe -L <SQL Server FQDN>" at the command line, where
<SQL Server FQDN> is the Fully-Qualified Domain Name of the MOM database server
Instance.
2. In SQL Server Enterprise Manager, expand the OnePoint folder.
3. Add a new database user by right-clicking the Users sub-node of the OnePoint database
folder, and then selecting New Database User.
4. In the Database Users - New User dialog, enter the computer name in the Login name text
box. Computer names follow the format: domain\computername$.
MOM Community
5. Grant the computer account user the db_owner database role membership, and then click
OK.
6. Navigate to the Security folder for the SQL Server instance.
7. Add a new SQL Server Login by right-clicking the Logins folder, and then selecting New
Login.
8. On the General tab of the SQL Server Properties - New Login dialog, enter the computer
name in the Name text box. Computer names follow the format domain\computername$.
9. On the Database Access tab, grant this computer account db_owner access to the OnePoint
database by selecting the Permit check box, next to the OnePoint database, and then select
the db_owner check box, below.
10. Click OK.
On the Management Server
1. On the Management Server, stop the MOM Service.
2. In the Component Services snap-in, expand Component Services / Computers / My
Computer / COM+ Applications.
3. Right-click the Microsoft Operations Manager Data Access Server node, and click Shut
down.
4. After the application has stopped, open its properties.
5. On the Identity tab, select the System Account and the Network Service options, and then
click OK.
6. Start the MOM Service.
7. After the MOM Service has started, open the MOM Administrator console and confirm that
you do not see any DAS errors.
MOM Agent
The MOM agent uses the Action Account to gather information about, and run responses on, the
managed computer. This account can be affected by password policy, and you can change the
password on this account manually.
Changing the agent Action Account password/login

You can use the SetActionAccount.exe utility in the %Program Files%\Microsoft Operations
Manager 2005 directory to change the password, easily. You can also use this utility to specify a
different account for the Action Account. You can use the utility as follows:
MOM Community
SetActionAccount.exe <management group> [options]
Options:
-query //returns the current Action Account settings for the specified
management group.
-set <domain> <username> //sets the Action Account for the specified management
group. Note - the tool will prompt you for the new password.
Note - the management group must be specified, even if the agent is not
multihomed.
Note
You must restart the MOM Service on the computer to perform
this change, or any other permission change, to the Action
Account.
Granting Management-Pack Specific Permissions to the Action

Account in a Lockdown Security Environment
Monitoring functionality on an agent computer is provided by both the MOM Service
(MOMService.exe) and the Action Account. On computers running Windows 2000, the Action
Account must be a member of the local administrators group. On computers running
Windows 2003, you can use a low-privileged account for the agent’s Action Account, under
certain circumstances. However, configuring the Action Account, with the necessary rights and
privileges to run Management Pack features, might require significant manual configuration on
the agent computer.
Each Management Pack uses a different set of resources on an agent computer. Consequently,
support for, and configuration of, a low privilege account varies across Management Packs.
Information about Management Pack features that are supported using a low privilege account
and information about how to configuring low privilege accounts is documented in the individual
guides for each Management Pack.
MOM Reporting
If you change the passwords for any accounts that are members of the SCDW DTS security
group on the MOM Reporting Server, you must also replicate these changes to the DTS
scheduled task and the SCDW data source.
To change the password in the MOM Reporting Scheduled Task
1. Click Start, select Settings, Control Panel, Scheduled Tasks, and then click
SystemCenterDTSPackage Task.
MOM Community
2. In the SystemCenterDTSPackage Task properties dialog, on the Task tab, enter the new
account domain\name in the Run as text box.
3. Click the Set password button.
4. In the Set Password dialog, enter and confirm the password, and then click OK.
5. Click OK to complete the change.
To change the password in SCDW Data Source
1. In the MOM Reporting console, on the Home page, click SCDW.
2. On the Properties page, make sure that the Credentials stored securely in the report
server option and the Use Windows credentials when connecting to the data source
check box are both selected.
3. Type the new domain\username in the User name text box, and type the password in the
Password text box.
4. Click Apply.
Adding Permissions for Users to View Reports

When MOM 2005 Reporting is installed, only the BUILTIN\Administrators group, on the
Reporting computer, has permission to read or modify MOM reports. To grant access to a
specific security group, follow the procedure below. Additionally, you can give users access to
specific reports and report directories through the SQL Reporting Services User Interface.
To grant permissions to view Reports
1. Login to the MOM Reporting Console as an Administrator, and then connect to
http://localhost/Reports.
2. Click Properties.
3. Click New Role Assignment, and then enter the name of the security group to which you
want to grant access.
4. Click Browser, and then click OK.
MOM Community
Maintaining the MOM

Management Server
Configuring Settings
This section covers the configuration of settings that are not configured through the MOM
Administrator console. For information about configuring settings in the MOM Administrator
console, see Chapter 7, “Administrator Console Reference”.
Modifying Settings for Microsoft Error Reporting

If you enable MOM Error Reporting, MOM sends error report data to Microsoft. If a MOM error
occurs, the computer uses an encrypted channel to send information to Microsoft, where it is
stored in controlled-access facility. This feature applies to all MOM servers and to all computers
that MOM manages. Microsoft uses error report data to find and fix problems in the software that
you use. It is not used for other purposes. For more information about this error reporting feature,
see Microsoft’s Data Collection Policy at <http://oca.microsoft.com/en/dcp20.asp>.
You can modify the settings for error reporting in the following ways:
• Queue error reports.
• Enable or disable error reporting.
Use the chosen procedure on every MOM computer, for which you wan to modify error reporting
settings. After modifying settings on agents, run the Update Agent Settings task.
To queue error reporting data
1. Navigate to the following registry hive: HKEY_LOCAL_MACHINE\SOFTWARE\Mission
Critical Software\OnePoint.
2. Right-click QueueErrorReports, and click Modify.
3. Enter a value of 1.
4. Restart the MOM service.
To disable Microsoft error reporting:
1. Navigate to the following registry hive: HKEY_LOCAL_MACHINE\SOFTWARE\Mission
Critical Software\OnePoint.
MOM Community
2. Righ-click EnableErrorReporting, and click Modify.

3. Change the value from 1 to 0. Click OK.
4. Right-click QueueErrorReports, and click Modify.
5. Enter a value of 0.
6. Restart the MOM service.
To update agent settings:
1. In the Details pane, right-click the agent computer and click Update Agent Settings.
2. Click OK.
Adding and Removing Management

Servers
This section describes the process for adding and removing Management Servers from a
management group, including the process for deleting orphaned Management Servers.
Adding Additional MOM Management Servers and

Redistributing the Agent Load
Use the following process to add additional Management Servers to a management group and to
re-distribute the agent load:
• Use the MOM setup program to install the new Management Server.
• Redistribute the agent load by updating computer discovery rules.
• Manually initiate computer discovery.
• Update agent settings.
• Update agent settings for manually-installed agents, if necessary.
Installing the New Management Server

Use the MOM setup program to install the new MOM Management Server. Be sure to specify the
existing database for the management group. For more information, see “Installing Additional
Management Servers” in Chapter 3 of the Microsoft Operations Manager 2005 Deployment
Guide, “Deploying MOM 2005 across Multiple Computers”
MOM Community
Re-distributing the Agent Load

To re-distribute the agent load, manually update the computer discovery rules for the computers
you want to report to the new Management Server. Specify the name of the new Management
Server.
Initiating Computer Discovery

Initiate computer discovery for all of the affected Management Servers. You can initiate a full
computer discovery, at any time, for just one Management Server, or for all Management Servers
in the management group.
To initiate a full computer discovery for just one Management Server
1. In the MOM Administrator console, expand Administration, expand Computers, and then
click Management Servers.
2. In the Details pane, right-click the Management Server that you want to perform computer
discovery for, and then click Run Computer Discovery Now.
To initiate a full computer discovery for all Management Servers

1. In the MOM Administrator console, expand Administration, and then expand Computers.
2. Right-click Management Servers, and then click Run Computer Discovery Now.
Updating Agent Settings

Send configuration changes to the affected agent computers by updating agent settings.
To update agent settings
1. In the details pane, right-click the agent computer, and then click Update Agent Settings.
2. Click OK.
Updating Manually Installed Agents

The process for updating the Management Server assignment, for agents that are manually
installed, depends on the level of agent control that is applied to the agent:
• If the agent control level is set to Full: update the associated computer discovery rule, run
computer discovery, and then update agent settings.
• If the agent control level is set to None: re-run the manual agent setup. Select Modify, and
then select Modify Management Group. Update the name of the Management Server. After
completing the setup wizard, run computer discovery for the affected Management Servers.
MOM Community
Removing a MOM Management Server

Use the following process to remove a MOM Management Server:
• Redistribute agent load across remaining servers by manually updating computer discovery
rules.
• Run computer discovery.
• Update agent settings.
• Update agent settings for manually-installed agents, if necessary.
• Use Add/Remove Programs to uninstall MOM from the server.
For information about performing the first four steps, see the preceding section of this chapter,
“Adding Additional MOM Management Servers and Redistributing the Agent Load”.
Maintaining the MOM

Database
Proper database maintenance improves MOM performance, and reduces the amount of
unnecessary data in your MOM database. This section covers the following:
• Database Size
• Grooming
• Moving the MOM Database
Database Size
MOM stores all data and configuration information in the Microsoft SQL Server™ 2000
(OnePoint) database. The MOM database can grow very large, particularly in environments
where MOM collects significant amounts of data, or monitors a large number of computers.
MOM supports a maximum database size of 30 GB. You must maintain at least 40 percent free
space to allow indexing and database jobs to complete successfully.
To maintain the optimum database size, MOM periodically grooms data from the MOM
database. When MOM grooms data, you can lose performance, alert, event, security, and
capacity planning data. You might want to retain this historical data for a number of business
reasons, such as long-term security auditing or capacity planning.
MOM Community
To retain historical MOM data, while keeping the MOM database at optimum levels, you can
create a MOM Reporting database. For more information, see Chapter 5, “Deploying MOM 2005
Reporting”, and Chapter 7, “Deploying MOM 2005 in Advanced Environments”, in the
Microsoft Operations Manager 2005 Deployment Guide.
Conditions That Can Affect Database Size

The following situations can cause conditions in which database size is affected.
• Database is Configured to Grow Automatically
• Too Many Management Packs Installed
• Audit Log Is Enabled
Database is Configured to Grow Automatically

The database should not be configured for automatic file growth. During automatic file growth,
all database operations are suspended. A database operation that must have uninterrupted access
to the database (for example, insertion or a maintenance job) might attempt to write to the
database during automatic file growth, but the attempt does not succeed. If you have already
configured your OnePoint database for automatic file growth, use the following procedure to
disable this function:
To safely disable automatic file growth
1. Stop the MOM Service on all Management Servers in the management group.
2. In SQL Server 2000 Enterprise Manager, expand SQL Server Group under Microsoft
SQL Server.
3. Click the server name, and then expand Databases.
4. Right-click the OnePoint database, click Properties, and then click the Data Files tab.
5. Clear the Automatically grow file check box.
Too Many Management Packs Installed

You should include only the Management Packs that you plan to use, initially, because it is
possible to install others later. When only the intended-use rules are pushed to the agents, less
superfluous data is transmitted between the agent and the MOM Management Server.
Reindexing
MOM provides the OnePoint–Reindex job that runs each Sunday at 3 A.M. This reindex job
locks the tables during the indexing process and prohibits any Write operations to those database
MOM Community
tables. If the database gets too large, it takes longer to run the reindexing jobs, which can impact
performance. It can also take longer for an event to be written to the database, and for an alert to
be generated. Finally, failure to run this reindexing job can cause data read operations to take
longer in the database.
Grooming
Database grooming refers to the process of deleting data from the MOM database and
automatically resolving alerts. The grooming process is a SQLSERVERAgent batch job that
resolves alerts or deletes the collected events, alerts, performance counters, and other events from
the database. When customizing your grooming jobs, it is important to remember the following:
• Ensure sufficient lag time between grooming jobs to allow for growth and event storms.
• More data in your database results in longer grooming cycles. Query the MOM database to
determine how many alerts and events are waiting to be groomed out of the database, and
adjust the grooming settings accordingly.
• Configure an alert rule to automatically alert you of grooming job failures.
Entering New Grooming Jobs

MOM does not allow you to enter new grooming jobs through the MOM Administrator console.
You can only set the number of records to delete per grooming job, and set the age of the records
being removed. However, you can use SQL Server Enterprise Manager to create a custom
grooming job. For more information about custom grooming jobs, see the SQL Server 2000
documentation.
Scheduling Grooming Jobs

You can change the default settings for grooming jobs using SQL Server Enterprise Manager.
Caution
If you change the default scheduled times for database
grooming, the new times must not interfere with other
scheduled MOM tasks. For example, do not schedule a
database grooming job for 2:05 A.M., because this is the
default time to scan for managed computers.
To modify scheduled database jobs

1. Log on with a Windows 2000 Administrator account to the computer on which you installed
the database.
2. From the Microsoft SQL Server folder, open Enterprise Manager.
MOM Community
3. Expand SQL Server Group, and then expand the server that contains the MOM database.
4. Expand Management, and then expand SQL Server Agent.
5. In the left pane, click Jobs.
6. In the right pane, right-click the job that you want to reschedule, and then select Properties.
7. Click the Schedules tab.
8. In the Properties window, click Edit.
9. In the Edit Job Schedule window, click Change.
10. In the Edit Recurring Job Schedule window, enter the values you want, and then click OK.
11. In the Edit Job Schedule window, click OK.
12. In the Properties window, click OK.
Default Grooming Settings

The MOM 2005 grooming task automatically sets the status of Error, Warning, Inactive,
Information, Service Unavailable, and Success alerts from New to Resolved if an operator has
not assigned them a status. The OnePoint–Update Database job is responsible for changing the
resolution state. This job affects records that are older than the values defined on the Database
Grooming tab in the Global Settings dialog box.
Note
Active alerts are not groomed.
When an alert is set to the Resolved status, either by an operator or by the Auto Resolve
grooming task, it will remain in the database for 4 days by default. The OnePoint–Groom Alerts
job will delete alerts older than the value defined in the Global Settings dialog box. This default
value of 4 days can be changed to delete resolved alerts sooner. For more information, see the
“Modifying Grooming Settings” section, later in this chapter.
Alerts Stored in the Database Some alerts that are not set to Resolved might remain in the
database indefinitely. Only Error, Warning, Information, and Success alerts are automatically set
to Resolved by the OnePoint–Update Database job. Unresolved alerts can consume database
space, over time. Acknowledged alerts will not be automatically resolved and deleted from the
database. The acknowledged alerts need to be manually set to Resolved for the grooming jobs, in
order to delete them from the database.
Table 4.5 shows the default database grooming settings:
Note
While each grooming job has a maximum run time of
15 minutes, the OnePoint–Groom Events job consists of three
Did you jobs,
find this
andinformation
can total upuseful? Please send your suggestions and comments about
to 45 minutes.
MOM Community
Table 4.5 Default Database Grooming Settings

Auto-resolution Settings Older than
Automatically resolved critical error 90 days
alerts
Automatically resolved error alerts Two days
Automatically resolved inactive alerts One hour
Automatically resolved informational Four hours
alerts
Automatically resolved security issue 90 days
alerts
Automatically resolved service 90 days
unavailable alerts
Automatically resolved success alerts Four hours
Automatically resolved warning alerts One day
Querying the MOM Database

You can query the MOM database, directly, to determine if there are very large numbers of alerts
and events waiting for grooming. This is helpful in determining whether you should adjust your
grooming job frequency, and to help you ensure that your database grooming jobs are being
completed in an appropriate timeframe.
To query the database for grooming job time
1. In SQL Server Query Analyzer, create a new query.
2. In the Query window, type the following:
SELECT jobname, timestarted, duration=datediff(s, timestarted, timeended)
FROM groomhistory GH
INNER join groomjob GJ on GH.idGroomJob=GJ.idGroomJob
3. From the Query menu, select Change Database, and then select the OnePoint database
from the drop-down menu.
To query the database for alerts awaiting grooming
SELECT COUNT(*) AS AlertsAwaitingGrooming
MOM Community
FROM dbo.Alert
WHERE (ResolutionState=255)
To query the database for all specific alerts awaiting grooming
SELECT Name, Description, AlertLevel, RepeatCount, ResolvedBY, TimeResolved
FROM dbo.Alert
WHERE (ResolutionState=255)
To query the database for events awaiting grooming
SELECT COUNT(*) AS EventCount---
FROM dbo.Event
WHERE (TimeGenerated>90 days)
Modifying Grooming Settings

MOM provides easy access to database grooming settings in the MOM Administrator console
Global Settings dialog box. On the Database Grooming tab, you can change the retention time
for automatic resolution of alerts. You can also set the retention time for events, alerts
performance data, and logs.
To change database grooming in the Global Settings dialog box
1. From the Microsoft Operations Manager program folder, start the MOM Administrator
console.
2. In the left pane, expand Microsoft Operations Manager, and then expand Administration.
3. In the left pane, click Global Settings.
4. In the right pane, right-click Database Grooming, and click Properties.
MOM Community
5. Specify the number of days data is retained, or

6. To specify when alerts are automatically resolved, click the alert type, and click Edit. Once
you have specified the auto-resolve behavior, click OK.
Default Database Jobs

MOM provides default SQL jobs in the MOM database.
Table 4.6 Default Database Jobs
Grooming Job Definition
MOMX Partitioning And Grooming Scheduled to run daily at 12 A.M.
This job updates the partitioning
information and grooms appropriate
partitions.
OnePoint–Check Integrity Scheduled to run once per week, on
Saturday at 10 P.M. This job validates
the integrity of everything in the
MOM database. For example, it
checks that the index and data
pages are correctly linked and that
indexes are in their proper sort order.
OnePoint–Computer Maintenance Scheduled to run every five minutes.
This job checks for computers that
should come out of maintenance
mode.
OnePoint–Reindex Scheduled to run once per week, on
Sunday at 3 A.M. This job rebuilds
the MOM table indexes to improve
performance. The OnePoint–Reindex
job requires approximately
40 percent of free space within the
database to successfully complete.
For example, a 10-GB database
needs 14 GB of database space to
successfully rebuild the indexes. If
the jobs fail due to a lack of disk
space, the failure will not adversely
affect your MOM implementation.
OnePoint– Scheduled to run every five minutes.
TodayStatisticsUpdateComputersAnd This job updates the OnePoint
MOM Community
Alerts Operations Manager Today window.

OnePoint– Scheduled to run every 30 minutes.
TodayStatisticsUpdateEvents This job updates the OnePoint
Operations Manager Today window.
OnePoint– Scheduled to run every hour. This job
TodayStatisticsUpdatePerfmonRulesK updates the performance, rules and
B Management Pack knowledgebase.
OnePoint–Update Database Scheduled to run every hour. This job
grooms automatically resolved alerts
based on the information specified in
the Global Settings dialog box.
OnePoint–Update Statistics Scheduled to run once per day at
1 A.M. This job updates information
about key value distribution in the
database to improve performance.
Emergency Grooming
If you have run into a situation where you have to quickly free up some space on your OnePoint
database, it is recommended that you manually run the grooming job. If you find that this occurs
frequently, change the data retention time to groom the data more frequently.
To manually run the MOM 2005 grooming job
1. Log on, with a Windows 2000 Administrator account, to the computer on which you
installed the database.
2. From the Microsoft SQL Server folder, open Enterprise Manager.
3. Expand SQL Server Group, and then expand the server that contains the MOM database.
4. Expand Management, and then expand SQL Server Agent.
5. In the left pane, click Jobs.
6. In the right pane, right-click the MOMX Partitioning and Grooming job, and then select
Start Job.
7. Validate that the job was successful in the Last Run Status (Start Date) column.
MOM Community
Moving the MOM Database

Moving the MOM database is only recommended for failure recovery reasons, because it can
cause serious problems, and might require a reinstallation of the server. This section provides
instructions for moving the database in the following scenarios:
• Moving the OnePoint Database from a Server Running SQL Server to Another
• Moving the MOM Database That Resides on a MOM Management Server or a Server that
hosts other MOM components
• Relocating the Database to an Active/Passive Clustered SQL Server
Moving the OnePoint Database from a Server

Running SQL Server to Another
Caution
Before you edit the registry, create an emergency startup disk
and back up any critical data. Incorrectly editing the registry
can have serious, unexpected consequences that might
require you to restore the registry, or possibly reinstall
Windows. For more information about the registry, see the
Windows documentation or the registry reference in the
resource kit for your version of Windows, available at
http://go.microsoft.com/fwlink/?LinkId=14253.
Moving the OnePoint database is not a standard maintenance procedure. However, you might
need to move it for various reasons, including, but not limited to:
• Relocation of the MOM database to a clustered SQL Server.
• Volume size restrictions.
• Performance improvements, such as separating the database from the logs.
• Relocation of the database to a fault-tolerant volume.
You should only move the OnePoint database for one of these reasons. Moving the OnePoint
database can cause serious problems that can require a reinstallation SQL Server.
Important
To move the MOM database from one server running SQL Server to
The following steps are for moving the MOM database from a
server running SQL Server to another server running
SQL Server. If your Database server is also the MOM
Management Server, you must first move the other MOM
components to the new computer.
MOM Community
1. Install SQL Server on the destination computer.

2. Install the MOM database component by running the MOM2005 Setup.exe.
3. Uninstall all other MOM components that reside on the database computer.
4. Stop the MOM service on all MOM Management Servers.
5. Back up the current OnePoint database to a file.
6. On the destination computer, open SQL Server Enterprise Manager.
7. On the Restore menu, click From Device, and then select the backup file you created in
step 5.
8. On all MOM Management Servers, start Regedt32.exe, and then change the following
registry values from the current SQL Server Instance to the new SQL Server
Instance(format: Computer\SQLinstance):
• HKEY_LOCAL_MACHINE\Software\Mission Critical Software\DASServer\
DataSource Value
• HKEY_LOCAL_MACHINE\Software\Mission Critical Software\Onepoint\
Configurations\<configuration group name>\Operations\Database Value
9. For each of these keys, delete the current SQL Server value, and then create a new
SQL Server name value.
10. MOM will recreate the MOM Management Server keys, as needed, under this new key when
the MOM service restarts.
11. Restart the MOM service on the MOM Management Server.
12. Make the same registry changes that you made in step 8 on each MOM Management Server
in this management group.
Moving the MOM Database That Resides on a MOM

Management Server or a Server that hosts other
MOM components
In addition to the changes discussed in the previous section, you may need to modify other MOM
components residing on the old MOM Database computer. If there are other MOM components
installed on the computer from which you are moving the MOM Database you must uninstall
those components prior to or at the same time you uninstall the MOM Database. If you want to
install the other MOM components on the new computer as well, it is important to install them
on the new computer before uninstalling them on the old computer so as to minimize downtime
in your monitoring environment.
MOM Community
Note
Moving the MOM Management Server to a computer with a
different name might have an effect on the MOM agents if this
is the only MOM Management Server in the management
group. Contact Microsoft Product Support Services if this is the
case.
To move the MOM database that resides on a MOM Management

Server
1. Install the MOM Management Server on the new computer.
2. Update the agent settings to reflect the new MOM Management Server.
3. Follow the directions in the “To Move the MOM Database” section earlier in this chapter.
To move the MOM database that resides on a computer hosting other
MOM components
1. Install the MOM components on the new computer.
2. Uninstall the MOM components (other than the MOM database) on the old computer.
3. Follow the directions in the “To Move the MOM Database” section earlier in this chapter.
Relocating the Database to an Active/Passive

Clustered SQL Server
You might want to relocate the MOM database to a clustered SQL Server, while preserving the
configuration data in the MOM OnePoint database.
To relocate the MOM database to a clustered SQL Server
1. Install the MOM 2005 database on the replacement computer according to the “Installing the
MOM Database on the Cluster Nodes” section in Chapter 7 of the Microsoft Operations
Manager 2005 Deployment Guide.
2. Stop the MOM Service on all the management servers in the configuration group. Back up a
copy of the OnePoint database and move it to the active cluster machine. Detach the current
OnePoint database from the new clustered SQL instance.
3. Reattach the OnePoint database from the old machine onto the new clustered SQL instance.
4. Point all Management Servers to the new SQL instance (as listed in the “Moving the MOM
database” section)
5. Restart the MOM service on all Management Servers.
MOM Community
6. Once the management group is running without error, you may uninstall the MOM Database
component through Add/Remove Programs on the old MOM Database computer.
Uninstalling the MOM Database

Completely removing MOM from your enterprise requires the removal of the MOM database
from the MOM Management Server or database server. If the setup program does not
automatically remove the database, use the SQL Server administrator tools to remove it. For
more information about removing the MOM database, see the SQL Server documentation.
Important
Uninstall MOM from the old database server, or take the
server offline if you want to keep it as a recent backup of the
MOM database, in case anything goes wrong with the new
database server. If you leave the old database server online,
but do not uninstall MOM, and there are still MOM
Management Servers configured to communicate with the old
MOM database, they will continue sending data, and your
configuration group will be in an inconsistent state.
Monitoring Size and Performance

issues
Maintaining optimum performance of the MOM database server is critical to monitoring your
environment. A good monitoring strategy includes monitoring for thresholds and creating custom
views to monitor other performance counters. For more information about monitoring your
database, see Chapter 3, “Monitoring”, in this guide.
Maintaining the MOM

Reporting Server and
Reporting Database
This section presents several tasks that are necessary for the standard maintenance of the
Reporting server, including:
MOM Community
• Sizing
• Configuring Data Transformation Services (DTS)
• Grooming
Sizing
The MOM 2005 Reporting server database is a SQL Server database that stores historical data
for trend analysis. Although data does not get inserted as frequently as for the MOM OnePoint
database, it is still important to allocate enough space.
To estimate the prospective Reporting database size, figure out how much your OnePoint
database grows within one day. Multiply that number by the number of day’s worth of data that
you want to retain. Then, double that number, to account for indexes.
The TempDB on the SQL Instance containing the OnePoint database needs to be large enough for
one day’s growth. Also, the SystemCenterReporting database log file should be the size of one
day’s growth, multiplied by five to account for indexes.
Configuring Data Transformation

Services (DTS)
This section covers the following maintenance tasks for the MOM Reporting Server and DTS.
• Change the Schedule for Transferring MOM Data to the MOM Reporting database
• Moving a Large Amount of Data using DTS Latency
Change the Schedule for Transferring MOM Data to the MOM

Reporting database
MOM runs a scheduled task to periodically transfer data from the MOM database to the MOM
Reporting database. By default, this task is scheduled to run at 1:00 A.M., every day. You can
change the schedule, but it is important that this task not run when the SystemCenterReporting
grooming task is running, or it will fail. It should not be set to run too frequently either..
To change the schedule of the MOM data transfer task
1. Log on by using an account that has administrative credentials.
2. On the Start menu, point to Programs, point to Accessories, point to System Tools, and
then click Scheduled Tasks.
3. In the Scheduled Tasks window, double-click SystemCenterDTSPackageTask.
MOM Community
4. Click the Schedule tab and set the start time and frequency at which you want the task to
run.
Note
The grooming for the MOM Database uses information in the
Reporting DTS job to prevent the grooming from removing
data that has not been transferred to the Reporting database.
If the DTS job fails, MOM will not groom the MOM Database for
the full 60 days, to avoid removing data that has not been
transferred to the Reporting database.
Moving a Large Amount of Data using DTS Latency

The DTS job collects fact and dimension data that has been changed or added since the last time
the DTS job was run, and before a latency time. By default, the latency time is 5 minutes;
therefore, data that came in within the last 5 minutes, before the DTS job ran, will not be inserted
in the Reporting database. This latency period exists to make sure that the records are committed
across all tables in the operation database, before they are transferred.
Therefore, it is recommended that you move data in smaller packets if you have a large amount
of data to move one time. For example, you may have ten days worth of data in your MOM
operational (OnePoint) database stored, because you did not install MOM Reporting when you
initially deployed MOM. You can modify the latency settings from the default 5 minutes so that
you can move smaller packets ofdata. By using the /latency switch on the
MOM.Datawarehousing.DTSPackageGenerator.exe, you can increase the latency to 9 days,
for example, and only transfer the data that is older than 9 days ago. Changing the latency switch
can prevent the DTS task from failing due to lack of space, and ensures the task takes less time
overall.
To run the latency switch on the DTS task
1. Log on using an account that has administrative credentials.
2. Point to Start, Run, and type CMD to open the command line window.
3. Copy the command line of the SystemCenterDTSPackageTask into the command-line
window and type /latency:9 (the “9” represents 9 days in this example).
4. Repeat the steps above using smaller latency timeframes until your data is all moved.
MOM Community
Note
Once you have moved all of your data to the Reporting Server,
you must remove the latency on the scheduled job.
Grooming
By default, the period to retain data in the SystemCenterReporting database is 395 days. When
you install the MOM 2005 Reporting component, a stored procedure that is named
p_updategroomdays is created in the SystemCenterReporting database. You can use this stored
procedure to configure the number of days that data is retained in the SystemCenterReporting
database. By default, fact data older then 13 months (395 days) is deleted. Snapshot facts older
then 3 days are deleted. Dimension data is not deleted. To modify the number of days to retain
data in the SystemCenterReporting database, follow these procedures:
To modify the number of days to retain data in the
SystemCenterReporting database
2. Change the database to the SystemCenterReporting database.
exec p_updategroomdays 'TableName', DaysToRetainData
Note
In this example, TableName is one of the six main tables, and
DaysToRetainData is the number of days to retain data in that
table.
Repeat step 4 for each fact table you want to modify.
For example, to retain data in the SC_AlertFact_Table for 300 days, use the following
query:
Exec p_updategroomdays ‘SC_AlertFact_Table’, 300
To verify the number of days to retain data in the

SystemCenterReporting database
2. Change the database to the SystemCenterReporting database.
MOM Community
SELECT cs.cs tablename ‘Table Name’, wcs.wcs groomdays ‘Groom Days’ from
warehouseclassschema wcs
Join classschemas cs
On cs.cs classID = wcs.wcs classID
Where cs.cs tablename = ‘SC AlertFact Table‘
And wcs.wcs.mustbegroomed = 1
4. Repeat step 3 for each table you want to verify.
Note
MOM Reporting server grooming settings can only be changed
by the SystemCenterReporting database owner.
Reporting Database Tables

There are three types of tables in the Reporting database:
• Dimension Tables
• Fact Tables
• Periodic Snapshot Fact Tables
Dimension Tables
Dimension tables contain information about computers, event details, or alert levels. Data is
added to dimension tables, and if the data already exists, it is updated with the most current
information. Dimension records are never deleted. Therefore, the computer dimension will
contain the latest information on the computers. It may also contain the last known configuration
information for computers that have since been removed from the MOM management group, so
we may still be storing events and alert for those computers.
The following is the list of dimension tables:
• SC_AlertLevelDimension_Table
• SC_AlertResolutionStateDimension_Table
• SC_ClassAttributeDefinitionDimension_Table
• SC_ClassDefinitionDimension_Table
• SC_ComputerDimension_Table
• SC_ComputerRuleDimension_Table
• SC_ComputerToConfigurationGroupDimension_Table
MOM Community
• SC_ConfigurationGroupDimension_Table
• SC_CounterDetailDimension_Table
• SC_DateDimension_Table
• SC_EventDetailDimension_Table
• SC_EventTypeDimension_Table
• SC_OperationalDataDimension_Table
• SC_ProcessRuleDimension_Table
• SC_ProcessRuleToConfigurationGroupDimension_Table
• SC_ProviderDetailDimension_Table
• SC_RelationshipAttributeDefinitionDimension_Table
• SC_RelationshipDefinitionDimension_Table
• SC_ScriptDimension_Table
• SC_ScriptToConfigurationGroupDimension_Table
• SC_TimeDimension_Table
• SC_UserDimension_Table
Dimension Views
When querying, use only the corresponding view names SC_*_View Eg. SC_
AlertLevelDimension_View
Fact Tables
Fact tables contain the primary data of the Reporting database, and tend to be very large.
Example data includes alerts, events, and sampled numeric data (performance counters). Rows
that are added to the MOM database, since the last DTS job, are added to the fact tables. Facts
are groomed over time based on the date in the groom column. The default time to retain fact
data is 395 days.
The following is the list of additive fact tables:
Table Name Groom Column
SC_AlertFact_Table DateTimeAdded
SC_AlertHistoryFact_Table DateTimeLastModified
SC_AlertToEventFact_Table DateTimeEventStored
SC_EventFact_Table DateTimeStored
MOM Community
SC_EventParameterFact_Table DateTimeEventStored
SC_SampledNumericDataFact_Table DateTimeAdded
Fact Views
When querying, use only the corresponding view names SC_*_View Eg. SC_ AlertFact _View.
Use clustered index columns in your where clause for best performance.
Periodic Snapshot Fact Tables

These tables contain the latest state information. Reports that use these fact tables are only
concerned with the most recent information. Each time the DTS job is run, all the new data is
added to these tables regardless of whether it is already there. Old data is groomed quickly and
data is only retained for 3 days by default based on the DateTimeOfTransfer column
Following is the list of periodic snapshot fact tables:
• *SC_ClassAttributeInstanceFact_Table
• *SC_ClassInstanceFact_Table
• SC_ComputerRuleToProcessRuleGroupFact_Table
• SC_ComputerToComputerRuleFact_Table
• SC_ProcessRuleMembershipFact_Table
• SC_ProcessRuleToScriptFact_Table
• *SC_RelationshipAttributeInstanceFact_Table
• *SC_RelationshipInstanceFact_Table
Latest Views
For user convenience, these fact tables have a “latest” view defined for them (it is named
SC_*_Latest_View, E.g. SC_ComputerToComputerRule_Latest_View). The latest view returns
the rows that were transferred from all configuration groups, corresponding to the latest time of
transfer for each configuration group.
Maintaining MOM Agents

This section includes instruction on how to:
• Configure agent settings that are not configured through agent global settings.
• Migrate and rename agents.
MOM Community
• Remove orphaned agents.
Configuring Agent Settings

This section covers the configuration of agent settings that are not configured through the agent
global settings. For information about global agent settings, see Chapter 7, “Administrator
Console Reference”.
Changing the Agent Communication Port Number

By default, agents communicate with the MOM Management Server through port 1270. If the
agent is installed manually, and the control level is set to Full, additional ports are used during
the setup process and during subsequent agent scans.
Consider changing the communication port (1270) to a port that is known only to the
administrators of your organization. Changing the communication port impacts agents
differently, depending on how they are installed:
• If you change the port number after you install agents manually, then you must rerun the
manual agent setup program on the agent computers to point to the new port.
• Agents that are installed remotely will begin communicating through the new port after they
receive updated configuration settings (every one minute, by default). No additional
configuration is necessary on agents that are installed remotely.
Finally, be sure to verify that the port you specify is enabled through the routers on the wide area
network (WAN) link.
To change the communications port on the MOM Management Server
1. In the left pane, expand Administration, and click Global Settings.
2. In the right pane, right-click Communications, and then select Properties.
3. On the Communications tab, change the port number to the desired port.
4. Restart the MOM service on the MOM Management Server.
Changing the Agent Control Level of Manually

Installed Agents
Agents that are installed manually are configured to use one of the following control levels:
MOM Community
• None — The Management Server does not remotely upgrade or uninstall agents. MOM
never remotely updates manually-installed agents with the agent control level set to None.
When applying patches, or installing service packs, to MOM, you must manually update
these agents. You also must upgrade and uninstall the agent software manually.
• Full — The Management Server performs all operations for the agent, including agent
configuration, upgrade, agent uninstall, and attribute collection. Use this option for
computers on your internal network to provide automatic agent configuration.
If an agent is configured with a control level of None, then you are prevented from remotely
upgrading, applying MOM-related updates, or uninstalling the agent. As a result, you must
manually perform these actions on the agent computer.
To change the control level of manually-installed agents, use one of the following methods:
• Manually change the control level to Full.
• Modify the agent control level setting by running a query against the MOM database.
Manually Changing the Agent Control Level to Full

To manually change the agent control level to Full, use the following process:
• On the agent computer, run the manual agent setup wizard to modify the agent configuration.
• On the Management Server, change the agent state to Unmanaged and then commit the
configuration change.
• On the agent computer, restart the MOM service.
• On the Management Server, approve the agent for management.
Running the manual agent setup wizard
To change the agent control level to Full, run the Manual Agent Setup Wizard on the agent
computer. You can launch the Manual Agent Setup Wizard either by using Add/Remove
Programs (select Change, not Remove) or by using the MOM 2005 Setup Resources.
To manually change the agent control level to full:
1. Launch the Manual Agent Setup Wizard.
2. On the Program Maintenance page, select Modify, and then click Next.
3. On the Manage Agent Management Groups page, select Modify Management Group.
4. If the agent is multihomed, select the applicable management group, and click Next.
5. On the Agent Configuration page, change the agent control level to Full, and then finish
the setup wizard.
Changing the agent state to unmanaged
MOM Community
Updating the agent control level on the MOM Management Server and in the database requires a
few additional steps on the Management Server.
To change the agent state to unmanaged:
click Agent-managed Computers.
2. Right-click the computer that you want to stop MOM from managing, and then click Force
to Unmanaged.
3. In the left pane of the MOM Administrator console, right-click on Management Packs and
select Commit Configuration Change.
Approving the agent for management
After changing the agent state to unmanaged, complete the process by re-approving the agent for
management. It may be necessary to wait for the agent to heartbeat before it will appear in the
Pending Actions list. The wait time can be eliminated by stopping and restarting the MOM
service on either the MOM Management Server or the agent computer.
To approve the agent for management:
click Pending Actions.
2. Right-click the agent and click Approve.
Modifying the Agent Control Level Setting by Running a Query

Against the MOM Database
The agent control level setting is stored in the MOM database. This setting is not stored on the
MOM agent and is not configurable through the MOM Administrator console.
By default, manually-installed agents are configured with a control level of Full. When an agent
is installed with a control level of None, then MOM adds a table to the database record,
specifying this control level. This table is not added for agents that are configured with a control
level of Full. Therefore, to change the agent control level, run a query against the MOM database
to either add or remove the agent control level table. Run the query once for each manually-
installed agent.
First, to determine the unique ID of an agent, run the following query:
SELECT idComputer FROM Computer WHERE Name = ‘ComputerName’
To change the agent control level from Full to None, use the following query to add the agent
control level record to the database:
INSERT INTO [OnePoint].[dbo].[Configuration](
MOM Community
[idConfiguration],
[idComponent],
[idComputer],
[DataCategory],
[DataName],
[DataValue],
[TimeAdded],
[LastModified],
[LastModifiedBy]
)
VALUES(
newID(),
‘74B6DF0B-5094-497A-9DED-39C807452863’,
‘<idComputer (uniqueID)>’,
‘Management’,
‘ManageType’,
‘Group’,
GetUTCDate(),
GetUTCDate(),
SYSTEM_USER
)
To change the agent control level from None to Full, use the following query to delete the record
from the database:
DELETE FROM Configuration
WHERE idComputer = '<uniqueID>'
and DataCategory = 'Management'
and DataName = 'ManageType'
and DataValue = 'Group'
Migrating and Renaming Agents

This section includes instructions for the following processes:
• Configuring agents to report to a different primary MOM Management Server
• Migrating agents to a new management group
• Migrating agents across domains
• Renaming agent computers
MOM Community
Configuring an Agent to Report to a Different

Primary MOM Management Server
By default, the Management Server that you use to install an agent becomes the agent’s primary
Management Server. You can configure agents to report to a different primary MOM
Management Server. The following caveats apply:
• The MOM Management Server that an agent reports to is configured in the computer
discovery rule that applies to the agent. Therefore, if a computer discovery rule targets more
than one agent, a change to the primary MOM Management Server will apply to all targeted
computers.
• If an agent is targeted by more than one computer discovery rule, resulting in multiple
Management Server managing the agent, then the last computer discovery rule to run is
applied to the agent. MOM will generate an alert in this scenario.
To configure an agent to report to a different primary MOM
Management Server:
click on Computer Discovery Rules.
2. In the details pane, right-click on the computer discovery rule that applies to the agent that
you are configuring, and then click Properties.
3. Under Management Server, select a new primary MOM Management Server and click OK.
4. In the left pane of the MOM Administrator console, right-click Computer Discovery Rules,
and click Run Computer Discovery Now.
5. Verify that the agent is reporting to the desired MOM Management Server:
6. In the left pane of the MOM Administrator console, click on Agent-managed Computers.
7. In the details pane, locate the agent computer and then view the Management Server
column to determine the primary MOM Management Server.
8. Send the configuration change to the agent computer by updating agent settings:
9. In the details pane, right-click the agent computer and click Update Agent Settings.
10. Click OK.
Migrating Agents to a New Management Group

Use one of the following methods to migrate an agent to a new management group:
MOM Community
• Uninstall the agent from the first management group, and then reinstall the agent to the new
management group.
• To ensure continued monitoring, first multihome the agent by installing it to the new
management group. After monitoring from the new management group is verified, then
uninstall the agent from the old management group.
For more information about installing and uninstalling agent computers, see Chapter 4,
“Discovering Computers and Deploying MOM Agents”, of the Microsoft Operations Manager
2005 Deployment Guide.
Migrating Agents Across Domains

When you move an agent computer from one domain to another, you must uninstall and then re-
install the agent computer from all management groups that it belongs to. Data associated with
the agent computer, prior to the domain move, is not retained.
To migrate an agent across domains
1. Uninstall the agent.
2. Delete all computer discovery rules for the agent that meet the following criteria:
• Rule type = Include
• Computer name = computer_name (where computer_name is the name of the affected
computer)
3. Move the computer to the new domain.
4. Reinstall the computer to the management group, either remotely or manually.
Renaming a MOM Agent Computer

When you rename a MOM agent computer, you must uninstall and then re-install the agent
computer from all management groups that it belongs to. Data associated with the agent
computer, prior to name change, is not retained.
To rename an agent computer
1. Uninstall the agent.
2. Delete all computer discovery rules for the agent that meet the following criteria:
• Rule type = Include
MOM Community
• Computer name = computer_name (where computer_name is the name of the affected

computer)
3. Rename the computer.
4. Reinstall the computer to the management group, either remotely or manually.
Removing Orphaned Agents

There are several scenarios that can lead to an orphaned agent. An agent can be orphaned if it is
left behind during the removal of the MOM server components. Or, an agent can become
orphaned if the computer is taken offline, or if the computer changes roles before you have
uninstalled the MOM agent.
To remove an orphaned agent
• After running the manual agent setup program, uninstall the agent using Add/Remove
Programs, in Control Panel.
Before reinstalling the agent to a management group, first resolve the problem that caused the
agent computer to be orphaned. If possible, install the agent remotely from a Management
Server, instead of installing the agent manually.
Patches for MOM 2005

Occasionally, Microsoft releases a patch (also referred to as a hotfix) for MOM 2005, to fix one
or more issues with the product. To ensure that MOM operates properly, you must apply those
patches to the computers in your MOM environment.
MOM patches are packaged and installed using Windows Installer. The patch executable file
name indicates the product name, the product version, the associated KB article number, the
platform and the language that the patch applies to. When installing a patch on the MOM
Management Server, MOM generates a corresponding .msp file in the <MOM installation folder
>\x86\Patches folder.
Applying a Patch
MOM patches contain a fix for either server components, the MOM Agent component, or for
both. After installing the patch on the MOM Management Server, MOM determines if MOM
agents also need the patch.
MOM Community
To apply a patch in your MOM environment:

1. Manually patch each MOM Server in your MOM management groups.
2. If the patch also contains a fix for the MOM Agent component:
• Use the MOM Administrator console to apply the patch to MOM agents with Control
Level = Full.
• Manually apply the patch on each MOM agent, which is set with a Control Level =
None.
After installing the patch on the MOM Management Server, MOM determines whether the patch
also contains fixes for the MOM agent component. If the patch contains fixes for the MOM agent
component, then MOM examines the control level of MOM agents in the management group, to
determine which MOM Agents require the patch. You can then review this classification, and
apply the patch to the appropriate MOM agents from the MOM Administrator console.
To apply the patch to a MOM server
1. Download the patch .exe file to the local MOM server that you want to patch.
2. Run the patch .exe file.
3. Open the Release Notes from the setup dialog box to review information about the patch,
and to view the installation instructions. Follow those instructions to complete the
installation.
4. Before applying a patch, MOM stops the MOM Service on the server, and then restarts the
service after the installation is complete.
To view and to apply the patch to MOM Agents with Control Level =
Full
Perform this procedure once, on the MOM Management Server.
1. In the MOM 2005 Administrator console, expand Administration.
2. Expand Computers, and then select Pending Actions.
3. In the details pane, select one or more computers on which you want to install the patch.
Select computers which are classified with a Pending Action of Requires Patching, and
with Control Level of Full.
4. Right-click the selected computers, and select either of the following:
• Apply Patches Now - This starts the patch installation on the selected computers
immediately.
• Approve for Processing by Computer Discovery - This approves the patch
installation for the selected computers, and queues the patch to be installed during the
next computer discovery cycle.
MOM Community
Important
After the administrator approves a patch installation, MOM
installs all patches that have not yet been installed, even
patches that were not specifically approved by the
administrator.
• Reject Pending Installation - This prevents the installation of the patch on the selected
computers. When rejecting a patch, you must also remove the corresponding .msp file
from the <MOM installation folder>\x86\Patches folder.
Important
If you reject one patch, and then approve a different patch,
then if the un-approved patch .msp file still exists in the
<MOM installation folder>\x86\Patches folder, the un-
approved patch will be installed along with the approved
patch.
To apply the patch to agents with Control Level = None

Perform this procedure on each managed computer on which the agent has a Control Level of
None.
1. Download the patch .exe file to the local computer that you want to patch.
2. Run the patch .exe file.
3. Open the Readme file to view information about the patch, and to view the installation
instructions. Follow those instructions to complete the installation.
Monitoring and Verifying the Patch Installation

You can verify that a patch was successfully installed by verifying that:
• The computer no longer has a Pending Action of Requires Patching.
• The MOM version of the computers has been patched to reflect that the patch is installed.
If MOM cannot successfully install the patch, it raises an alert for each computer on which the
installation failed. You can check the log file: <MOM installation
folder>/AgentLogs/filename??? for details about the failure.
MOM Community
Additional Resources
For the latest information about MOM, see the MOM Web site at
http://go.microsoft.com/fwlink/?linkid=6727.
To access the MOM core product documentation on the Web, see to the Technical Resources
section of the MOM Web site at http://go.microsoft.com/fwlink/?LinkId=8943.
MOM Community

4 Maintain2005

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

4 Maintain2005

Caricato da

Copyright:

Formati disponibili

Microsoft

Table 4.2 Weekly Tasks

Table 4.3 Monthly Tasks

Table 4.4 Ad Hoc Tasks

manually installed agents. Level of Manually Installed Agents”,

installing and configuring the MOM

Tasks Not Supported

Changing Passwords, Logins,

MOM Management Server

Changing the Action Account password

Changing the DAS account

Configuring the Web Console As Read-Only

Using the Network Service Account for DAS

To use Network Service for DAS

On the MOM Database Server:

Changing the agent Action Account password/login

SetActionAccount.exe <management group> [options]

Granting Management-Pack Specific Permissions to the Action

Adding Permissions for Users to View Reports

Maintaining the MOM

Modifying Settings for Microsoft Error Reporting

2. Righ-click EnableErrorReporting, and click Modify.

Adding and Removing Management

Adding Additional MOM Management Servers and

Installing the New Management Server

Re-distributing the Agent Load

Initiating Computer Discovery

To initiate a full computer discovery for all Management Servers

Updating Agent Settings

Updating Manually Installed Agents

Removing a MOM Management Server

Maintaining the MOM

Conditions That Can Affect Database Size

Database is Configured to Grow Automatically

Too Many Management Packs Installed

Entering New Grooming Jobs

Scheduling Grooming Jobs

To modify scheduled database jobs

Default Grooming Settings

Table 4.5 Default Database Grooming Settings

Querying the MOM Database

Modifying Grooming Settings

5. Specify the number of days data is retained, or

Default Database Jobs

Alerts Operations Manager Today window.

Moving the MOM Database

Moving the OnePoint Database from a Server

1. Install SQL Server on the destination computer.

Moving the MOM Database That Resides on a MOM

To move the MOM database that resides on a MOM Management

Relocating the Database to an Active/Passive

Uninstalling the MOM Database

Monitoring Size and Performance

Maintaining the MOM

Configuring Data Transformation

Change the Schedule for Transferring MOM Data to the MOM

Moving a Large Amount of Data using DTS Latency

Repeat step 4 for each fact table you want to modify.

Exec p_updategroomdays ‘SC_AlertFact_Table’, 300

To verify the number of days to retain data in the

On cs.cs classID = wcs.wcs classID

Where cs.cs tablename = ‘SC AlertFact Table‘