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
3. Create a target host group in SCVMM. For more information, see the SCVMM documentation.
4. Create a hypervisor profile in the OMIMSSC console extension for SCVMM. For more information, see Creating a hypervisor
profile.
5. Discover a reference server by using the Discovery page. For more information, see the Discovering servers using manual
discovery.
6. Create an Operational Template. For more information, see Creating Operational Template.
7. Assign an Operational Template. For more information, see Assigning Operational Template.
8. Deploy an Operational Template. For more information, see Deploying Operational Template.
Table 3. Different scenarios for hypervisor deployment
If you require the latest factory drivers and out-of-band
drivers
While creating a hypervisor profile, enable LC (Lifecycle
Controller) driver injection.
If you want to retain the existing hardware configuration While creating the Operational Template, clear the checkbox
for all the physical components .
9. View the job status on firmware update and OSD in the Jobs and Logs Center page. For more information, see Viewing
information in OMIMSSC.
Non-windows OS deployment using OMIMSSC
console extensions
To deploy any flavor of non-windows OS:
1. Create an Operational Template. For more information, see Creating Operational Template.
2. Assign an Operational Template. For more information, see Assigning Operational Template.
3. Deploy an Operational Template. For more information, see Deploying Operational Template.
NOTE:
If DHCP lookup fails while deployment, then the server times out and it is not moved into Managed Lifecycle
Controller Lifecycle Controller (ESXi) collection in SCCM.
Apply updates on servers
You can update the selected servers or server groups by using the following update sources:
● Online FTP and local FTP source
● Online HTTP and local HTTP
● Local Dell Repository Manager (DRM) repository
1. Before you begin updates, view information about update sources and update groups. For more information about update
source, see Update source. Ensure that there is an update source created. For more information, see Creating an update
source.
2. Discover or synchronize servers with registered MSSC. For more information, see Device discovery and
synchronization .Ensure that the servers inventory is up-to-date. For more information, see Launching configuration and
deployment.
3. Update the servers by using one of the following options:
● Select the required server groups to apply the updates. For more information, see Applying updates on servers.
NOTE: Select Allow Downgrade to downgrade the firmware version of the components.
● Use the firmware update component in Operational Template. For more information, see Creating Operational Template.
4. Modify the update source with the latest catalog by using polling and notification. For more information, see Polling and
notification.
Use cases
13