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
Latest inventory information is not displayed even
after firmware update
Even though the firmware update job is complete on an 11th generation of PowerEdge server, in the Appliance, the inventory
does not display the latest firmware versions.
In the Appliance, refreshing the inventory is an activity performed immediately after a firmware update job is complete. Firmware
update is completed even before the PowerEdge server’s CSIOR activity is complete, due to which the earlier firmware
inventory information is displayed.
As a workaround, check if the CSIOR activity is complete in the PowerEdge server, and then in the Appliance, refresh the
firmware inventory. Also, ensure to restart the server after applying agent-free staged update. For more information on
refreshing the inventory, see Viewing and refreshing firmware inventory.
For more information on CSIOR, refer to the Troubleshooting section in the latest version of the Dell Lifecycle Controller GUI
User's Guide available at dell.com/support/home.
SCVMM error 21119 while adding servers to active
directory
While adding servers to Active Directory, SCVMM error 21119 is displayed. Error 21119: The physical computer
with <SMBIOS GUID> did not join Active Directory in time. The comptuer was expected to join
Active Directory using the computer name <host.domain>.
As a workaround, do the following:
1. Wait for some time to see if the server is added to the Active Directory.
2. If the server is not added to the Active Directory, then manually add the servers to the Active Directory.
3. Add the server in to SCVMM.
4. Once the server is added in to SCVMM, rediscover the server in OMIMSSC console extension for SCVMM.
The server will be listed under the Host tab.
Troubleshooting
59