Systems Management General

Last reply by 05-11-2021 Unsolved
Start a Discussion
2 Bronze
2 Bronze

SCOM MP Version 7.2 generates massive amount of override MP's


I've got SCOM MP 7.2 in combination of OMIMSSC running. And couple of hours after installation the MP starts generating override mp's with name Dell EMC Agent Resource 0 Override. While the numer is counting up. For the moment i have 64 of those mp's.

Creating of these mp's is causing a very high load on management servers and sql. What is the purpose of these mp's?

Inside you can find this.

<?xml version="1.0" encoding="utf-8"?><ManagementPack ContentReadable="true" SchemaVersion="2.0" OriginalSchemaVersion="1.1" xmlns:xsd="" xmlns:xsl="">
      <Reference Alias="SystemCenter">
      <Reference Alias="SystemCenter1">
      <MonitorConfigurationOverride ID="Microsoft.SystemCenter.Agent.HealthService.HandleCountThreshold.ThresholdValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.HealthService.HandleCountThreshold" Parameter="Threshold">
      <MonitorPropertyOverride ID="Microsoft.SystemCenter.Agent.HealthService.HandleCountThreshold.EnabledValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.HealthService.HandleCountThreshold" Property="Enabled">
      <MonitorConfigurationOverride ID="Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold.ThresholdValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold" Parameter="Threshold">
      <MonitorPropertyOverride ID="Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold.EnabledValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.HealthService.PrivateBytesThreshold" Property="Enabled">
      <MonitorConfigurationOverride ID="Microsoft.SystemCenter.Agent.MonitoringHost.HandleCountThreshold.ThresholdValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.MonitoringHost.HandleCountThreshold" Parameter="Threshold">
      <MonitorPropertyOverride ID="Microsoft.SystemCenter.Agent.MonitoringHost.HandleCountThreshold.EnabledValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.MonitoringHost.HandleCountThreshold" Property="Enabled">
      <MonitorConfigurationOverride ID="Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold.ThresholdValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold" Parameter="Threshold">
      <MonitorPropertyOverride ID="Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold.EnabledValue.Override" Context="SystemCenter!Microsoft.SystemCenter.HealthService" ContextInstance="7831cb98-260e-97bb-1b0e-0056c6598c6e" Enforced="false" Monitor="SystemCenter1!Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold" Property="Enabled">
    <LanguagePack ID="ENU" IsDefault="false">
        <DisplayString ElementID="Dell.AgentResource1.Override">
          <Name>Dell EMC Agent Resource 1 Override</Name>


if i look to the id's, than they are windows vm's running on vmware. So not Dell related in any way.

Labels (4)
Replies (11)



I would suggest starting with page 12 found here, then let me know what you're seeing afterwards. 


Let me know if this helps. 



Chris Hawk
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services

Did I answer your query? Please click on ‘Accept as Solution’
‘Kudo’ the posts you like!


In my case

( Object is Windows Computer AND True ) is set as dynamic rule for the DellProxyMSGroup.

If i understand correct only the proxy management servers should be in there...

I did not configure this group like this, the MP has done this. 


Hi @Charlez79 Please refer this link: and refer to the note on this page. You need to configure a Proxy MS and add to the group DellProxyMSGroup and perform sync with MSSC. Also, you can plan the number of Proxy MS to be added based on the number of devices you need to monitor and the number of devices supported per Proxy MS If you perform the above step you should be able to see the number of agent resource override MP = number of Proxy MS added to the DellProxyMSGroup. Regards, Anjana


OK, clear. But why was that group populated with all windows computers in my case?

Cleared that and added 2 proxy's.

How is the discovery called who will create the agent override mp's?





OMIMSSC Proxy's should be configured on SCOM management servers, correct?

So if i only have 2 management servers, i can only have 2 proxy's.

If i have more devices than 2 proxy's can hold, i need to configure an extra management server only for installing extra proxy.

Would have been better that you can just use any windows machine with agent on it as a proxy.



Hi @Charlez79 

  • A Proxy Management Server (PMS) is used for offloading workload from the management servers (MS) to a virtual machine which has a Windows OS. These are discovered as Windows Computer in SCOM. These virtual machines are recommended to be used dedicatedly for hosting the devices.
  • Once they are discovered as Windows Computers in SCOM, they have to be added to DellProxyMSGroup and a sync with MSSC operation has to be performed from the Dell EMC OpenManage Integration Dashboard before you start device discovery from this dashboard. 
  • One Proxy MS supports 250 devices in scalable mode of discovery and 30 devices in detailed mode of discovery.
  • It is recommended to host 4 ProxyMS agents per MS when discovery is performed in scalable mode and 2 ProxyMS agents per MS when discovery is performed in detailed mode.
  • In your setup, you have 2 management servers, hence you can scale up to 2000 devices by using 8 Proxy MSes (i.e., 4 per MS) with discovery mode of devices set to scalable mode.
  • In case you are using detailed mode of discovery, you can discover upto 120 devices by using 4 Proxy MS (i.e., 2 per MS) .

To scale up beyond these numbers, you need to add another MS to the SCOM management group. 

You can find a detailed information on planning the number of ProxyMS as per number of devices to be monitored in the installation guide i had shared in previous post here. 

with regards,




Would like to clarify this point:

"It is recommended to host 4 ProxyMS agents per MS when discovery is performed in scalable mode and 2 ProxyMS agents per MS when discovery is performed in detailed mode."

A Management Server may be hosting more that the mentioned numbers of agents. Of these agents, when you add those windows computers which are dedicated as Proxy MS, ensure that in scalable mode, not more than 4 or 2 as per scalable or detailed mode respectively are used, when adding them to the DellProxyMSGroup. 





Thx for clearing out. Still some things that are not clear to me.

In the OMIMSSC appliance i only added 1 Management server console and my second management server is added automatically. So it it showing 2, but only added 1. 

Is this normal? Is only 1 Management server used or both in this case? I recall if i remove one of the 2, they will be both removed.

If you have 2 management servers, what proxy is talking to what Management server?

thx for the help!




Yes, during enrollment process, all the management servers which are part of the management group (specifically, they all should be part of the All Management Server Resource Pool) are getting enrolled (registered) with the OMIMSSC appliance. Hence, you are seeing both the server getting listed in the Console Enrollment page in OMIMSSC Admin Portal.

Yes, selecting any one of these to de-enroll, de-enrolls the all the enrolled ones.At a time only one management group should be enrolled in the appliance.

The relation between the ProxyMS and the MS is controlled by the user (you). When you discover the ProxyMS as a windows computer in SCOM, you have the option to select which management server should host it (Discovery Wizard in SCOM).

Latest Solutions
Top Contributor