Manager event log after agent restart. Objects discovery related When a discovery (including warnings in the Operations relationship discovery) fails to Manager event Log find an instance, a warning is written to the Operations Manager event log stating that null was returned by the discovery script. Alerting in physical node in There are two known issues In clustered environments that clustered environment is associated with monitoring in contains active/passive unreliable clustered environments: nodes; rely on the monitoring information displayed in the  When a node changes from virtual node only. This is active to passive, the monitoring status of the node because the virtual node and associated artifacts may always points to the physical not be reflected correctly in node that is active at any the Operations Console. point in time. In clustered environments,  the Operations Manager creates a virtual node which may display duplicate status and alerts. Relationships and The following are the known The workarounds to address Dependency monitors issues related to relationships these issues are as follows: and dependency monitors: This  Restart the Operations occurs mostly when the BizTalk Manager Health Service Management Pack is re-imported on the BizTalk machine. on a given SCOM Server. The -OR- user is then required to see comment the previous state as Run the Flush Health  Service State and Cache given in the "Steps to Reproduce task. The steps to do this the Behavior" section. are as follows: Relationships between  a. In the navigation tree, BizTalk artifacts are not select Operations discovered. Manager Agent Agent Dependency relationships  Health State. are not displayed as b. Select the computer expected. that is running BizTalk
Manager event log after agent restart. Objects discovery related warnings in the Operations Manager event Log When a discovery (including relationship discovery) fails to find an instance, a warning is written to the Operations Manager event log stating that null was returned by the discovery script. Alerting in physical node in clustered environment is unreliable There are two known issues associated with monitoring in clustered environments:  When a node changes from active to passive, the monitoring status of the node and associated artifacts may not be reflected correctly in the Operations Console.  In clustered environments, the Operations Manager creates a virtual node which may display duplicate status and alerts. In clustered environments that contains active/passive nodes; rely on the monitoring information displayed in the virtual node only. This is because the virtual node always points to the physical node that is active at any point in time. Relationships and Dependency monitors The following are the known issues related to relationships and dependency monitors: This occurs mostly when the BizTalk Management Pack is re-imported on a given SCOM Server. The user is then required to see comment the previous state as given in the "Steps to Reproduce the Behavior" section.  Relationships between BizTalk artifacts are not discovered.  Dependency relationships are not displayed as expected. The workarounds to address these issues are as follows:  Restart the Operations Manager Health Service on the BizTalk machine. -OR-  Run the Flush Health Service State and Cache task. The steps to do this are as follows: a. In the navigation tree, select Operations Manager Agent Agent Health State. b. Select the computer that is running BizTalk
BizTalk%20Server%202010%20Monitoring%20Management%20Pack%20Guide.docx