- Notes, cautions, and warnings
- About this guide
- About Dell EMC OpenManage Integration with Microsoft System Center (OMIMSSC) for System Center Operations Manager (SCOM)
- Purchase and manage OMIMSSC license
- Port information and Communication Matrix for OMIMSSC appliance
- Support Matrix
- Deploy and configure the OMIMSSC appliance
- OMIMSSC and SCOM interfaces for device management
- Enroll (register) management servers to OMIMSSC
- Tasks you can perform on the OMIMSSC Admin Portal
- Manage OMIMSSC from the SCOM console
- Discovery and monitoring of PowerEdge servers by using the licensed monitoring features of OMIMSSC
- Discover PowerEdge servers by using iDRAC WS-Man through OMIMSSC
- Discover PowerEdge servers by using the SCOM console
- Object discoveries using WS-Man
- Install SNMP services to monitor PowerEdge servers
- Monitoring PowerEdge servers and rack workstations on the SCOM console
- Discovery and monitoring of Dell EMC chassis using OMIMSSC
- Discovery and monitoring of Dell EMC Network Switches using OMIMSSC
- Manage Dell EMC devices using the OMIMSSC appliance
- View jobs in OMIMSSC Admin Portal and OpenManage Integration Dashboard
- Run tasks on the SCOM console for OMIMSSC monitoring features
- Upgrading the OMIMSSC appliance
- De-enroll (Deregister) management servers enrolled to OMIMSSC
- Remove an OMIMSSC VM
- Troubleshooting
- After deploying the OMIMSSC appliance, an IP address is not assigned to the OMIMSSC appliance
- After deploying the OMIMSSC appliance, enrollment of management servers with OMIMSSC is unsuccessful or the management packs are not successfully installed.
- Unable to start the OpenManage Integration Dashboard in the SCOM console
- Unable to connect to the OMIMSSC appliance
- Issues observed when usernames of local account and domain account match but the passwords differ
- Resolve issues in synchronizing data of Dell EMC devices with OMIMSSC
- Manually clean the SCOM console that is unreachable during the de-enrollment
- Connection is unavailable between OMIMSSC and the SCOM console
- Unable to log in to the OMIMSSC Admin portal by using the Mozilla Firefox browser
- A job run on OMIMSSC to discover a device stays in the Progress state for more than five hours
- Unable to discover and monitor devices after restarting OMIMSSC
- Event ID 33333: Data Access Layer rejected retry on SqlError
- Resolve issues in the Dell EMC Feature Management Dashboard
- Reference topics
- Monitoring features supported by OMIMSSC
- Configuring the monitoring features of OMIMSSC by using the Feature Management Dashboard
- Import monitoring features using the Dell EMC Feature Management Dashboard
- Upgrade monitoring features using the Dell EMC Feature Management Dashboard
- Customizing monitoring features using the Feature Management Dashboard for scalable and detailed editions
- Remove monitoring features using the Dell EMC Feature Management Dashboard
- Severity levels of discovered devices
- Key features of licensed monitoring of PowerEdge servers in OMIMSSC
- Hardware components of servers and rack workstations monitored by OMIMSSC
- Hardware components of chassis monitored by OMIMSSC
- Hardware components of network switches monitored by OMIMSSC
- View options provided by the OMIMSSC monitoring features
- OMIMSSC Unit Monitors
- Event rules used by different monitoring features of OMIMSSC
- Additional resources
- Accessing support content from the Dell EMC support site
- Contacting Dell Technologies
- Glossary
- Additional topics
Dell EMC OpenManage Integration Version 7.2 with Microsoft System Center for System Center Operations Manager User's Guide
A job run on OMIMSSC to discover a device stays in the Progress state for more than five hours
The device discovery job that is run from OMIMSSC gets stuck in the running task list for more than five hours.
Workaround—Create and run a new job for the device discovery with same set of IP addresses.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\