When a monitored object, such as a computer or distributed application, goes offline for maintenance, Operations Manager 2007 detects that no agent heartbeat is being received and, as a result, might generate numerous alerts and notifications. To prevent alerts and notifications, place the monitored object into maintenance mode. In maintenance mode, alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts are suppressed at the agent.
 Important |
|---|
| We do not recommend that you put Operations Manager 2007 servers into maintenance mode. Configuration distribution, the heartbeat feature, and other features for the system might become unreliable. If you place a management server into maintenance mode, alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts generated on the management server will be suppressed. The health service on the management server continues to run. Alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts from other agent-managed computers will be processed and displayed as appropriate. |
You can initiate maintenance mode by clicking Start Maintenance Mode in the Actions pane of the Monitoring area in the Operations console. You can define maintenance mode for a monitored object and the entities it hosts. While the monitored object is in maintenance mode, you can edit the maintenance mode settings. You can also specify duration for an object to remain in maintenance mode, or schedule a time for the managed object to be removed from maintenance mode.
See Also
Did you find this information useful? Please send your suggestions and comments about the documentation.