Install Guide
Table Of Contents
- Dell EMC OpenManage Integration v7.1 for Microsoft System Center for Operations Manager (SCOM) Installation Guide
- Overview
- OMIMSSC components
- System requirements for OMIMSSC
- Installing, configuring, and managing OMIMSSC
- Managing OMIMSSC and its components
- Viewing OMIMSSC details
- Dell EMC OMIMSSC user management
- Viewing or refreshing enrolled consoles
- Modifying Operations Manager account
- Modifying credentials used for the enrolled consoles in Dell EMC OMIMSSC Admin portal
- De-enrolling the Operations Manager console
- Removing Dell EMC OMIMSSC appliance Virtual Machine (VM)
- Viewing jobs
- Installing Dell EMC Server Management Pack suite for Operations Manager
- Pre-requisites
- Installing Dell EMC Server Management Pack suite using .exe file
- Installing Dell EMC Server Management Pack on multiple management servers
- Upgrading from previous versions of Dell EMC Server Management Pack Suite
- Upgrading from Operations Manager 2012 R2 to Operations Manager 2016
- Upgrading from previous Operations Manager
- Using Repair option in the Dell EMC Server Management Pack suite
- Uninstalling the Dell EMC Server Management Packs
- Configuring Operations Manager to monitor Traps and Trap-Based Unit Monitors
- Dell EMC Feature Management Dashboard
- Dell EMC Server Management pack suite version 7.1 supported Monitoring features
- Dell EMC OMIMSSC version 7.1 supported monitoring features
- Troubleshooting
- Connection lost between OMIMSSC appliance and Operations Manager console
- Error message while accessing Dell EMC OMIMSSC admin portal through Mozilla Firefox browser
- Failure to connect to OMIMSSC Appliance
- Test Connection fails between Dell EMC OMIMSSC appliance and Operation Manager console
- IP address not assigned to OMIMSSC appliance
- Appliance discovery job stuck in progress state
- Unable to launch Dell EMC OMIMSSC in the Operations Manager Console
- Discovery and monitoring of the Dell EMC device fail after restarting the Dell EMC OMIMSSC
- Event ID 33333: Data Access Layer rejected retry on SqlError
- Dell EMC Feature Management Dashboard does not populate
- Feature Management Dashboard task fails
- Feature Management alerts
- Health Service of the Feature Management Host Server is nonfunctional
- Appendix
- Accessing documents from the Dell EMC support site
Table 6. Deployment Scenario for Operations Manager 2016 (continued)
Dell EMC devices are discovered as iDRAC, Dell EMC Chassis, or Dell EMC Network switches in Dell EMC OMIMSSC console.
The inputs are provided in the Dell EMC OMIMSSC console and during discovery, the IP address range is provided and
appropriate credential profile is associated with the job.
Scalable 600–5000 Yes For 2000 network
devices, see
Sizing Guide for
required number of
Management Servers.
3–20 Each Proxy MS can monitor
maximum of 250 devices in
scalable mode. For configuration of
Proxy MS, refer Table Proxy MS
Virtual Machine Configuration.
Detailed 120–300 Yes For 2000 network
devices, see
Sizing Guide for
required number of
Management Servers.
4–10 Each Proxy MS can monitor
maximum of 30 devices in detailed
mode. For configuration of Proxy
MS, refer Table Proxy MS Virtual
Machine Configuration.
Table 7. Proxy MS virtual machine Configuration
Components Proxy MS Configuration
CPU Cores
8
RAM in GB
32
Mandatory Prerequisites:
1. Ensure that you do the following registry settings on each of the Proxy MS. Perform the below steps:
After extracting the OMIMSSC_7.1.0.A00_SCOM.zip file, perform the following steps:
a. Copy DellEMC-SCOM-Agent-Registry.reg and DellEMC-Proxy-MS-Configuration-Script.ps1 files from the
unzipped location on each of the Proxy MS machine in the same directory.
b. Run the DellEMC-Proxy-MS-Configuration-Script.ps1 from the PowerShell command prompt (with administrator
privileges).
NOTE:
● The script stops the agent health services, takes a backup of current registry values in the same directory path.
● The required Registry Key changes are implemented on the Proxy MS. Refer to the table below for registry
configuration on Proxy MS
● Microsoft Monitoring Agent Health Services are started.
● Registry Path: "HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters"
Table 8. Proxy MS Registry Configuration
S.No. Registry Configuration
1 Set the Persistence Version Store Maximum Registry Path to 131072.
2 Set the Maximum Global Pending Data Count Registry to 20408.
3 Set the State Queue Items Registry to 20480.
4 Set the Persistence checkpoint Depth Maximum Registry to 20971520.
NOTE: For more information about the registry key settings, see https://blogs.technet.microsoft.com/.
CAUTION: Using Registry Editor incorrectly can cause serious problems that might require you to reinstall
the operating system.
NOTE: The above sample script is provided to simplify configuration of the above required settings on the Proxy MS.
Dell EMC does not officially support this script.
2. The Microsoft public hotfix https://support.microsoft.com/ must be applied on each of the Systems Center Operations
Manager Servers and on every Proxy MS in the Scalability setup.
System requirements for OMIMSSC
13