White Papers

Technical support and resources
7 Scalability with Dell EMC OpenManage Integration with Microsoft System Center (OMIMSSC) for System Center
Operations Manager (SCOM)
After running the DellEMC-Proxy-MS-Configuration-Script.ps1 script:
• The script stops the agent health services and backs up current registry values in the same directory
path.
• The required registry key changes are implemented on the proxy management server. See Proxy
management server registry configuration definitions.
• Microsoft Monitoring Agent Health Services are started.
1.4.4 Proxy management server registry configuration definitions
• CAUTION: Using Registry Editor incorrectly can cause serious issues that might require you
to reinstall the operating system.
The registry path: "HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters".
• Persistence Version Store Maximum Registry Path is set to 131072.
• Maximum Global Pending Data Count Registry is set to 20408.
• State Queue Items Registry is set to 20480.
• Persistence checkpoint Depth Maximum Registry is set to 20971520.
• NOTE: For more information about registry key settings, see https://docs.microsoft.com/en-
us/archive/blogs/.
1.5 Deployment scenarios and correlation between management server
and Proxy MS
The Dell EMC devices can be discovered in the SCOM console and by using the Dell EMC OMIMSSC
appliance. One instance of OMIMSSC provides support to only one management group for discovery and
monitoring of devices.
You can configure the management server and proxy management server as per the deployment scenarios
that is required for your environment.
There are required configurations which must be done on management servers running specific version of
Microsoft SCOM. See the following sections for the required configurations for:
• Management Servers running with Microsoft SCOM 2012 R2
• Management Servers running with Microsoft SCOM 2016 and later
1.6 Required configuration for SCOM 2012 R2
• NOTE:
• To monitor 600+ devices in the scalable mode, upgrade SCOM 2012 R2 to SCOM 2016 and
later by using this issue fix, which is available only for SCOM 2016 and later versions:
https://support.microsoft.com/en-us/help/4481376/system-center-operations-manager-hotfix-
for-snmp-modules.
• The OMIMSSC appliance features are not supported on the SCOM 2012 SP1 version.