Users Guide
Table Of Contents
- OpenManage Integration Version 7.0 for Microsoft System Center User’s Guide
- Contents
- Introduction
- About OMIMSSC components
- About Admin Portal
- Launching OMIMSSC from enrolled MSSC console
- Use cases
- Profiles
- Launching Configuration and Deployment
- Discovering servers and synchronizing with MSSC console
- About reference server configuration
- Discovering servers in OMIMSSC
- Server discovery in OMIMSSC console extension for SCCM
- Server discovery in OMIMSSC console extension for SCVMM
- System requirements for managed systems
- Discovering servers using auto discovery
- Discovering servers using manual discovery
- Synchronizing OMIMSSC console extensions with enrolled SCCM
- Synchronizing OMIMSSC console extension with enrolled SCVMM
- Synchronizing with enrolled MSSC
- Resolving synchronization errors
- Deleting servers from OMIMSSC
- Launching iDRAC console
- OMIMSSC licensing
- Operational Template
- Preparing for deployment
- Managing Operational Template
- Integration with Dell Repository Manager(DRM)
- Maintenance
- Viewing information in OMIMSSC
- Troubleshooting
- Deploy option not visible in task sequence
- Duplicate VRTX chassis group gets created
- Empty cluster update group does not get deleted during autodiscovery or synchronization
- Failure of creation of update source
- Failure of firmware update because of job queue being full
- Failure of firmware update on cluster update group
- Failure of firmware update on 11th generation of servers
- Failure of firmware update while using DRM update source
- Failure of scheduled job on an update group
- Failure to apply Operational Template
- Failure to access CIFS share using hostname
- Failure to connect to FTP using system default update source
- Failure to create a repository during a firmware update
- Failure to delete a custom update group
- Failure to display Jobs and Logs
- Failure to export LC logs in CSV format
- Failure to export server profiles
- Failure to display Dell EMC logo in OMIMSSC Admin Portal
- Failure to view LC logs
- Firmware update on a few components irrespective of the selection
- Hypervisor deployment failure
- Hypervisor deployment failure due to driver files retained in library share
- Hypervisor deployment failure for 11th generation PowerEdge blade servers when using Active Directory
- Incorrect credentials during discovery
- IG installation issue while running multiple instances of the installer on the same server
- Importing server profile job gets timed out after two hours
- Latest inventory information is not displayed even after firmware update
- SCVMM error 21119 while adding servers to active directory
- Appendix
- Accessing support content from the Dell EMC support site
Duplicate VRTX chassis group gets created
When modular servers that were previously in another chassis are added to a VRTX chassis and discovered, the modular servers
carry previous chassis service tag information and create a duplicate VRTX chassis group in the Appliance.
To resolve, do the following:
1. Remove a modular server from one chassis, and add it in another chassis. For more information, see Server modules section
in Dell PowerEdge VRTX Enclosure Owner's Manual.
2. Configure CMC. For more information, see Installing and Setting Up CMC in Chassis Management Controller Version 2.1 for
Dell PowerEdge VRTX User's Guide, available at dell.com/support /home.
After you do the preceding tasks, if there are duplicate chassis group entries, then as a workaround, do the following:
1. Enable CSIOR and reset iDRAC on the newly added modular server.
2. Manually delete all the servers in the VRTX chassis group, and then rediscover the servers.
Empty cluster update group does not get deleted
during autodiscovery or synchronization
When a cluster group is discovered in the Appliance, 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 of creation of update source
When the Domain Name System (DNS) network configuration of the Appliance is changed, creation of HTTP or FTP type of
update source fails.
As a workaround, restart the Appliance, and then create the update source of type HTTP or FTP.
Failure of firmware update because of job queue being
full
Firmware update jobs submitted from the Appliance to iDRAC fail, and the Appliance main log displays the following error:
JobQueue Exceeds the size limit. Delete unwanted JobID(s).
As a workaround, manually delete the completed jobs in iDRAC, and retry the firmware update job. For more information on
deleting jobs in iDRAC, see iDRAC documentation at dell.com/support/home.
Failure of firmware update on cluster update group
After scheduling a firmware update job on a cluster update group, if the firmware update job fails for various reasons such as
IG is unreachable, the cluster group becomes unresponsive, or the firmware update job was canceled in CAU for an in-progress
job, the DUPs are downloaded and placed in each server cluster node belonging to the cluster group. All the DUP files are placed
under the folder called Dell consuming memory.
As a workaround, delete all the files in Dell folder, and then schedule a firmware update job.
54
Troubleshooting