FAQ

Discovery, synchronization and inventory
scenarios in
OMIMSSC
This section has all the troubleshooting information related to credentials issues, discovering servers, grouping servers, synchronizing
enrolled Microsoft console with OMIMSSC when using OMIMSSC.
Failure to discover servers
When multiple Microsoft consoles are enrolled to an OMIMSSC Appliance, and you try to discover a server, if even one of the SCCM
consoles are not reachable, then the server discovery job will fail.
As a workaround, de-enroll the SCCM console that is not reachable, or x the errors and ensure that the SCCM console is reachable from
OMIMSSC Appliance.
Discovered servers not added to All Dell Lifecycle
Controller Servers collection
After discovering the servers in OMIMSSC for SCCM console extension, the server may not get added into All Dell Lifecycle Controller
Servers collection.
As a workaround, delete the All Dell Lifecycle Controller Servers collection and then discover the server. The collection is automatically
created in SCCM and the server is added to this group.
Failure to discover servers due to incorrect credentials
If you provide incorrect credential details during discovery, then based on the iDRAC version, the following resolutions are available:
•
– While discovering a 12th generation PowerEdge server with iDRAC version 2.10.10.10 and later, if incorrect details are provided in the
credential prole, the server discovery fails, with the following behavior:
◦ For rst attempt, server IP address is not blocked.
◦ For second attempt, server IP address is blocked for 30 seconds.
◦ For third and subsequent attempts, server IP address is blocked for 60 seconds.
You can reattempt server discovery with correct credential prole details after the IP address is unblocked.
– While discovering an 11th or 12th generation PowerEdge server with iDRAC versions prior to 2.10.10.10, if server discovery attempts
fail due to incorrect credential prole details, then rediscover the server with the correct credential prole details.
– For iDRAC versions prior to 2.10.10.10, blocking of IP addresses is congurable. For more information, see iDRAC documentation at
Dell.com/idracmanuals. Based on your requirement, you can also disable blocking of IP addresses. And you can also check if the
iDRAC.IPBlocking.BlockEnable feature is enabled in iDRAC.
– If the default iDRAC credential prole is changed after a server is discovered and added in the Appliance, then no activity can be
performed on the server. To work with the server, rediscover the server with the new credential prole.
6
Discovery, synchronization and inventory scenarios in OMIMSSC 13