FAQ

2. Manually delete all the servers in the VRTX chassis group, and then rediscover the servers.
Unable to synchronize host servers with enrolled
SCCM
During synchronization of OMIMSSC console extension with enrolled SCCM, the servers are not listed as sub tasks in synchronization job
and hence does not get synchronized.
As a workaround, launch SCCM console with "Run as Administrator Privilege" and update out of band configuration for a server. Then
synchronize OMIMSSC console extension with enrolled SCCM.
For more information, see Synchronizing with enrolled Microsoft console topic in OpenManage Integration for Microsoft System Center
Version 7.2 for System Center Configuration Manager and System Center Virtual Machine Manager User's Guide.
Empty cluster update group not deleted during
autodiscovery or synchronization
When a cluster is discovered in OMIMSSC, a cluster update group gets created in the Maintenance Center with all the servers listed in
the cluster update group. Later, if all the servers are removed from this cluster through SCVMM, and an autodiscovery or synchronization
with SCVMM operation is performed, the empty cluster update group is not deleted in Maintenance Center.
As a workaround, to delete the empty server group, rediscover the servers.
Failure to perform maintenance-related tasks on
rediscovered servers
When you delete a server or all the servers in an update group from OMIMSSC, and rediscover them you cannot perform any other
operations on these servers like updating firmware, exporting and importing LC logs, exporting and importing server profiles.
As a workaround, after rediscovering the deleted server or servers, perform firmware updates using the Deploy Operational Template
feature in Server View and for other maintenance scenarios use iDRAC.
14
Discovery, synchronization and inventory scenarios in OMIMSSC