> ## Content Index
> Fetch the complete content index at: https://jesscoburn.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Resolving Remove-DisabledMonitoringObject Errors in System Center Operations Manager
- URL: https://jesscoburn.com/blog/error-running-remove-disabledmonitoringobject-in-system-center-operations-manager/
- Published: 2010-09-08T09:27:21.000Z
- Updated: 2026-03-16T18:57:28.000Z
- Author: Jess Coburn
- Tags: Blog, powershell, scom, system center, Windows Administration

## The Challenge: SCOM's Aggressive Discovery Model

When implementing System Center Operations Manager (SCOM), organizations quickly encounter a fundamental design challenge: management packs enable monitors for every discovered machine by default. This creates unnecessary noise and resource consumption, particularly in large enterprise environments.

During a recent SCOM deployment project, I developed a targeted approach to address this limitation through selective monitoring configuration.

## Strategic Solution: Group-Based Monitoring Control

The solution involves creating controlled monitoring groups and leveraging discovery overrides:

1. **Create dedicated groups:** Establish new groups under Authoring, assigning them to custom management packs (never use the Default Management Pack)
2. **Configure discovery overrides:** Navigate to object discoveries and override unwanted rules for servers in your designated groups
3. **Populate groups strategically:** Add target servers to your control groups
4. **Execute cleanup:** Run Remove-DisabledMonitoringObject via Operations PowerShell Console

This approach prevents SCOM from discovering specified services and monitors on grouped servers, while the PowerShell command removes existing monitors for newly disabled objects.

## Common Execution Error and Resolution

When processing large server groups or multiple rules simultaneously, administrators frequently encounter this error:

> Remove-DisabledMonitoringObject : Microsoft.EnterpriseManagement.Common.DiscoveryDataFromRuleTargetedToDeletedMonitoringObjectException: Discovery data has been received from a rule targeted at a non-existent monitoring object id.

### Root Cause Analysis

The error occurs when too many operations execute concurrently, overwhelming SCOM's processing capacity. This isn't a system failure—it's a resource constraint issue.

### Resolution Strategies

Two approaches resolve this error effectively:

- **Batch processing:** Reduce the number of machines per group to prevent resource conflicts
- **Iterative execution:** Continue running the command until no errors occur, as partial processing continues with each execution

## Strategic Benefits

This methodology provides operational flexibility—servers can be moved between groups to adjust monitoring scope dynamically. When monitoring requirements change, simply relocate servers from control groups to resume full discovery and monitoring.

## Key Takeaway

Effective SCOM management requires understanding its discovery model limitations and implementing strategic workarounds. This group-based approach transforms SCOM's default "monitor everything" behavior into a controlled, scalable monitoring strategy that aligns with enterprise operational requirements.