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
Discovering servers and synchronizing with
MSSC console
Discovery is the process of adding supported PowerEdge bare-metal server or host servers in OMIMSSC, and synchronization
with MSSC console allows you to add host servers from SCCM or SCVMM console into OMIMSSC.
Topics:
• 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
About reference server configuration
A server configuration with a preferred boot sequence, BIOS, RAID settings, hardware configuration, firmware update
attributes, and operating system parameters that is ideally suited for an organization is called reference server configuration.
Discover a reference server by capturing these settings in an Operational Template, and replicate it across different servers with
same hardware configuration.
Discovering servers in OMIMSSC
You can discover hosts and unassigned servers in OMIMSSC. The discovered servers information is saved in the OMIMSSC
database.
Consider the following points after discovering a server:
● The discovered server is added to the Hosts or Unassigned tab in the Configuration and Deployment page of
OMIMSSC.
● The discovered server is marked as hardware compatible when it contains supported versions of LC firmware, iDRAC, and
BIOS to work with OMIMSSC. For information about the supported versions, see OpenManage Integration for Microsoft
System Center Release Notes.
● A license is consumed for the discovered server.
The Licensed Nodes count in License Center page decreases as the number of servers are discovered.
● When you discover a PowerEdge server with an operating system deployed on it, and the server is already present in SCCM
or SCVMM console, then the server is listed as a host server under the Hosts tab in OMIMSSC console extensions where
the discovery job is initiated.
○ If the host is a modular server, then the service tag of the chassis containing the server is also displayed on the
Configuration and Deployment page.
● When you discover a PowerEdge server that is not listed in SCCM or SCVMM, then the server is listed as an unassigned
server under the Unassigned tab in all the enrolled OMIMSSC console extensions.
8
20 Discovering servers and synchronizing with MSSC console