Momadadmin.exe

The Operations Manager R2 management pack is automatically installed when you install System Center Operations Manager. Operations Manager 2007 R2 Management Pack Guide. Read the Management Pack guide as this covers items such as how to enable recovery for Health Service Heartbeats and creating Momadadmin.exe As accounts. Issue: AD integrated agent deployment was not functional.

Add the security group, which was provided as parameter to MOMADAdmin. Operations Manager Administrators, added the group specified when using the MomADAdmin. Alert: Agent proxying needs to be enabled for a health service to submit discovery data about other computers. Issue: The agent specified in the alert description does not have agent proxy enabled. Check the Allow this agent to act as a proxy and discover managed objects on other computers checkbox. Resolution: This is a bug in WMI.

It would be preferable if the problem was fixed properly, but the workaround does not seem to cause any adverse effects. UPDATE: Found this on another system with a different type of service. The start name was null, and the service would not start when attempted to start it. Used the sc delete to remove the service, rebooted the system, and it worked like a champ.

Issue: On a TCP Port monitor, two alerts are generated when the system cannot be communicated with. Resolution: The system in question was offline and needed to be brought back online, so the monitor functioned as expected. Issue: Failed attempting to push the agent to the system. Resolution: Logged into the system and manually installed the agent. Issue: After importing a large number of management pack files, the data warehouse started reporting issues. The health explorer listed an event number 31552 that the data filed to store in the data warehouse due to a SQLException Timeout expired.

The alerts were automatically closed after this action was performed. The health explorer listed an event number 31554 on the workflow Microsoft. In this case, the domain name had a typo on it. Issue: Issues providing notification via Instant Messaging. Issue: Email was being sent to a remote email environment and communication was lost between the environments. Resolution: When communication between the environments was restored, notification began to function again. Closed the alert, as it did not recur after communication was re-established.

Configured the notification to use Windows Integrated authentication. Once the network communication was back online, notifications were able to be sent. Issue: Network communication between the RMS and the Operations Manager database was interrupted. Created an override to disable this alert for the RMS that was reporting these occasionally per the link listed in the issue section of this alert. Alert: Recipient address is not valid. Issue: Recipient address is not valid for notification. Email was sent to remote email environment and communication was lost between the environments.

Closed the alert as it did not recur once communication was re-established. The health manager has detected that entity state collection has stalled. This adversely affects all availability calculation for the entire management group. Restart the Health, SDK, and Config services on the RMS after this change. Resolution: Brought back online the domain controllers for the domain, and this alert auto-resolved itself. The account may be disabled or has an expired password. This occurs on both CPU Utilization and Memory Utilization.

Resolution: The only option on this if the NAS was going to be monitored agentless was to disable the alert for the RMS. Stopped the WMI service, when that failed killed the process and re-started the WMI service. Closed the alert to see if it would recur on this system. Issue: Paging file is too small. Resolution: Needed to add memory to the system.

Search or use up and down arrow keys to select an item. The Operations Manager R2 management pack is automatically installed when you install System Center Operations Manager. Operations Manager 2007 R2 Management Pack Guide. Read the Management Pack guide as this covers items such as how to enable recovery for Health Service Heartbeats and creating Run As accounts. Issue: AD integrated agent deployment was not functional. Add the security group, which was provided as parameter to MOMADAdmin. Operations Manager Administrators, added the group specified when using the MomADAdmin.

Alert: Agent proxying needs to be enabled for a health service to submit discovery data about other computers. Issue: The agent specified in the alert description does not have agent proxy enabled. Check the Allow this agent to act as a proxy and discover managed objects on other computers checkbox. Resolution: This is a bug in WMI. It would be preferable if the problem was fixed properly, but the workaround does not seem to cause any adverse effects. UPDATE: Found this on another system with a different type of service.

The start name was null, and the service would not start when attempted to start it. Used the sc delete to remove the service, rebooted the system, and it worked like a champ. Issue: On a TCP Port monitor, two alerts are generated when the system cannot be communicated with. Resolution: The system in question was offline and needed to be brought back online, so the monitor functioned as expected. Issue: Failed attempting to push the agent to the system. Resolution: Logged into the system and manually installed the agent. Issue: After importing a large number of management pack files, the data warehouse started reporting issues.