Microsoft Knowledge Base Email Alertz

Updates that are made to alerts in the destination management group may not be applied in the zone management group in Microsoft Operations Manager 2005

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 892096 - Last Review: June 27, 2007 - Revision: 3.3

Updates that are made to alerts in the destination management group may not be applied in the zone management group in Microsoft Operations Manager 2005

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/ ) Description of the Microsoft Windows registry

On This Page

SYMPTOMS

An alert update conflict may occur in Microsoft Operations Manager (MOM) 2005 when you use the MOM-to-MOM product connector to connect a source management group and a destination management group. Additionally, when you try to use multiple management groups in a multi-tiered configuration, updates that are made to alerts in the destination management group may not be applied in the zone management group. For example, the problem may occur if you modify the repeat count of an alert.

CAUSE

This problem occurs if the alert is updated separately in a source management group and in a destination management group in the same polling period. By default, the source management group update takes precedence. The update in the destination management group is dropped when a conflict occurs.

RESOLUTION

A hotfix is available that lets a MOM 2005 administrator modify the MOM 2005 configuration so that the destination management group update takes precedence when an alert update conflict occurs.

After you apply this hotfix and set a registry key on all source Management Servers, the default behavior is reversed. When an alert update conflict occurs, a change in the destination management group takes precedence over a change in the source management group. However, changes in the source management group are not applied in the destination management group when a conflict occurs.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Install this hotfix on computers that meet all the following conditions:
  • The computer hosts a MOM Management Server in the source management group.
  • The computer has MOM-to-MOM product connector installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, this hotfix restarts the MOM service.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   23-Mar-2005  07:42  6.0.2900.2180     150,248  Mom2005-rtm-kb892096-x86-enu.exe  

After the hotfix is installed, the following files will have the listed attributes or later file attributes:
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   23-Mar-2005  09:18  5.0.2749.17       61,440   MomConn.exe  

Installation instructions

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To install the hotfix, follow these steps:
  1. Copy MOM2005-RTM-KB892096-X86-ENU.EXE to a local folder or to a network shared folder. If you use a network shared folder, make sure that you can access the folder from the computers that require this hotfix.
  2. Log on as an administrator to one of the computers that requires this hotfix.
  3. Run MOM2005-RTM-KB892096-X86-ENU.EXE on each applicable computer that meets the predefined criteria. You can run the file at a command prompt or use Windows Explorer to run the file.
  4. Repeat steps 2 through 3 on each computer that requires this hotfix.

After you install the hotfix, add a registry value to each computer that has this hotfix installed. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following subkey:
    HKEY_LOCAL_MACHINE\Software\Mission Critical Software\MomConn
  3. Click the Edit menu, point to New, and then click DWORD Value.
  4. In the right pane, type TopTierConflictResolution as the name of this new registry entry.
  5. Double-click this new registry entry, type 1 in the Value data field, and then click OK.
  6. Restart the MOM-to-MOM Connector service.
To revert to the default behavior where changes in a source management group take precedence over changes in a destination management group, set the TopTierConflictResolution registry entry to 0. Or, remove the registry entry. Then, restart the MOM-to-MOM Connector service.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseinter kbmompre2005sp1fix kbopman2005spfix KB892096
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate