Users Guide
Table Of Contents
- OpenManage Integration for Microsoft System Center Version 7.3 for Microsoft Endpoint Configuration Manager and System Center Virtual Machine Manager Unified User’s Guide
- Contents
- Introduction to OMIMSSC
- OMIMSSC license
- OMIMSSC components
- Support Matrix for OMIMSSC
- Deploy OMIMSSC
- Enroll Microsoft console in OMIMSSC
- Manage OMIMSSC and its components
- Backup and Restore OMIMSSC Appliance
- Uninstall OMIMSSC
- Upgrade OMIMSSC
- Manage Credential and Hypervisor profiles
- Discover devices and sync servers with OMIMSSC console
- Remove devices from OMIMSSC
- Views in OMIMSSC
- Manage Operational Templates
- Predefined Operational Templates
- About reference server configuration
- About reference Modular System configuration
- Create Operational Template from reference servers
- Create Operational Template from reference Modular Systems
- Create clusters using Operational Template
- View Operational Template
- Edit Operational Template
- Configure system specific values (Pool values) using Operational Template on multiple servers
- Assign Operational Template and Run Operational Template Compliance for servers
- Deploy Operational Templates
- Unassign Operational Template
- Delete Operational Template
- Deploy operating system using OMIMSSC
- Provision devices using OMIMSSC
- Update firmware using OMIMSSC
- Manage devices using OMIMSSC
- Deploy Azure Stack HCI cluster
- Troubleshooting
- Resources required for managing OMIMSSC
- Verifying permissions for using OMIMSSC console extension for MECM
- Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM
- Install and upgrade scenarios in OMIMSSC
- Enrollment failure
- Failure of test connection
- Failure to launch OMIMSSC after installing MECM console extension
- Failure to connect to OMIMSSC console extension for SCVMM
- Error accessing console extension after updating SCVMM R2
- IP address not assigned to OMIMSSC Appliance
- SCVMM crashes while importing OMIMSSC console extension
- Failed to login to OMIMSSC console extensions
- SC2012 VMM SP1 crashing during update
- OMIMSSC admin portal scenarios
- Discovery, synchronization and inventory scenarios in OMIMSSC
- Failure to discover servers
- Failure to auto discover iDRAC servers
- Discovered servers not added to All Dell Lifecycle Controller Servers collection
- Failure to discover servers due to incorrect credentials
- Creation of incorrect VRTX chassis group after server discovery
- Unable to synchronize host servers with enrolled MECM
- Empty cluster update group not deleted during autodiscovery or synchronization
- Failure to create cluster while applying cluster features
- Unable to retrieve the Cluster Aware Update job status
- Failure to perform maintenance-related tasks on rediscovered servers
- Generic scenarios in OMIMSSC
- Firmware update scenarios in OMIMSSC
- Failure of test connection for local update source
- Failure to create DRM update source
- Failure to create repository during firmware update
- Failure to update firmware of clusters
- Failure of firmware update because of job queue being full
- Failure of firmware update when using DRM update source
- Firmware update on components irrespective of selection
- Failure to delete a custom update group
- Failure to update WinPE image
- Changing of polling and notification bell color after updating the frequency
- Operating system deployment scenarios in OMIMSSC
- Server profile scenarios in OMIMSSC
- LC Logs scenarios in OMIMSSC
- Appendix I: Time zone attribute values
- Appendix II: Populate Pool values
- Accessing support content from the Dell EMC support site
You can create an update source or a repository, and set it as a default update source for generating a comparison report, and
receiving alerts when new catalog files are available at the repository.
Using OMIMSSC, you can keep the devices firmware up-to-date using online or offline update sources.
Online update sources are repositories that are maintained by Dell EMC.
Offline update sources are local repositories and used when there is no Internet connection.
It is recommended that you create custom repositories and place the network share in the local intranet of OMIMSSC Appliance.
This would save the Internet bandwidth and also provide a secure internal repository.
Update firmware using one of the following update sources:
● DRM repository—is an offline repository. Export the inventory information of discovered devices from OMIMSSC
Appliance to prepare a repository in DRM. For information about integration with DRM, and creating an update source
through DRM, see Integration with DRM. After creating a repository in DRM, in OMIMSSC, select the update source that
is created through DRM, relevant devices, and initiate an update on the devices. For information about DRM, see Dell
Repository Manager documents available at dell.com\support.
● HTTPS—can be an online or offline repository. Update specific components of devices with respect to the latest update
provided on HTTPS site. Dell EMC prepares a repository at every two months cadence and publishes the following updates
through PDK catalogs:
○ Server BIOS and firmware
○ Dell EMC certified operating system driver packs—for operating system deployment
NOTE: If you select an online update source, while deploying the Operational Template, the latest firmware versions
are downloaded and applied on the managed devices. Hence, the firmware versions might differ between reference and
deployed device.
● Reference firmware inventory and comparison—can be converted to an offline repository through DRM. Create a
reference inventory file that contains the firmware inventory of the selected devices. The reference inventory file can
contain inventory information of a device of the same type or model, or can have multiple devices of different types or
models. You can compare the inventory information of devices present in OMIMSSC against the saved reference inventory
file. To pass the exported file to DRM and create a repository, see Dell Repository Manager documents available at
dell.com\support.
Predefined and default update source
OMIMSSC includes the predefined update source that is available after a fresh installation, or upgrade. DELL EMC
ENTERPRISE CATALOG is a predefined default update source of type HTTPS. However, you can create another update
source and mark it as a default update source.
NOTE:
If you are using proxy server, to access the repository, edit the update source to add the proxy details and save the
changes.
Predefined and default update sources for Windows server HCI clusters
OMIMSSC supports updating Windows server HCI clusters through specific predefined update sources. These update sources
have reference to catalog files that contain latest and recommended firmware versions of components for Windows server HCI
clusters. They are listed only on Maintenance Center page.
UPDATE CATALOG FOR MICROSOFT HCI SOLUTIONS is a predefined default update source of type HTTPS, and is part of
DELL EMC ENTERPRISE CATALOG.
Predefined and default update sources for Modular Systems
OMIMSSC supports updating Modular Systems through specific predefined update sources. These update sources have
reference to catalog files that contain latest and recommended firmware versions of components for Modular Systems. They are
listed only on Maintenance Center page.
DELL EMC MX SOLUTION CATALOG is a predefined default update source of type HTTPS, and is part of DELL EMC
ENTERPRISE CATALOG.
Update firmware using OMIMSSC
77