The membership of the computer groups does not appear in the destination management group when you connect multiple Microsoft Operations Manager 2005 management groups (904662)



The information in this article applies to:

  • Microsoft Operations Manager 2005

SYMPTOMS

Computer grouping does not work correctly in the destination management group. For example, computers in the source management groups do not appear in most of the computer groups that are in the destination management group. This symptom occurs if two or more Microsoft Operations Manager (MOM) 2005 management groups are connected by using the MOM to MOM Product Connector (MMPC).

CAUSE

This problem occurs because the computer type information is not forwarded to the destination management group. Most computer groups use this information to determine the membership of the computer groups. The computer type can be any one of the following computer types:
  • Server
  • Client
  • Domain Controller
  • Unknown
  • Cluster Virtual Server
Computers from the source management group appear as Unknown computer types in the destination management group. Because most computer groups do not include the Unknown computer type in their definition, these Unknown computer type computers are excluded. This exclusion occurs even if the computer group formula matches these Unknown computer type computers.

WORKAROUND

To work around this problem, change the definition of each computer group in the destination management group to include the Unknown computer type.

Important Only change the computer groups that you want to be populated with computers from the source management group to include the Unknown computer type. Additionally, you cannot use this workaround for any Domain Controller computer groups. For Domain Controller computer groups, setting the definition to match the Unknown computer type causes all computers from the source management group to be included in the computer group. For Domain Controller computer groups, add the domain controllers computers by name. This exception has been documented in the MOM 2005 release notes.

STATUS

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

Modification Type:MajorLast Reviewed:7/27/2005
Keywords:kbtshoot kbprb KB904662 kbAudITPRO