Users Guide
Table Of Contents
- OpenManage Integration for Microsoft System Center Version 7.2.1 for System Center Configuration Manager and System Center Virtual Machine Manager Unified User’s Guide
- Introduction to OMIMSSC
- OMIMSSC components
- System requirements for OMIMSSC
- Deploy OMIMSSC
- OMIMSSC licensing
- Enrolling Microsoft console in OMIMSSC
- Managing OMIMSSC and its components
- Backup and Restore OMIMSSC Appliance
- Uninstalling OMIMSSC
- Upgrading OMIMSSC for SCVMM
- Rebooting OMIMSSC Appliance
- Logging out of OMIMSSC Appliance
- Managing profiles
- Discovering devices and synchronizing servers with MSSC console
- Views in OMIMSSC
- Managing Operational Templates
- Predefined Operational Templates
- About reference server configuration
- Creating Operational Template from reference servers
- Creating Operational Template from reference Modular Systems
- Viewing Operational Template
- Modifying Operational Template
- Configuring system specific values (Pool values) using Operational Template on multiple servers
- Deleting Operational Template
- Assigning Operational Template and running Operational Template compliance for servers
- Deploying Operational Template on servers
- Assigning Operational Template for Modular Systems
- Deploying Operational Template for Modular System
- Unassigning Operational Template
- About reference Modular System configuration
- Preparing for operating system deployment
- Creating clusters using Operational Template
- Firmware update in OMIMSSC
- Managing devices in OMIMSSC
- Provisioning devices from OMIMSSC
- Configuration and deployment
- Use cases
- Creating Operational Templates
- Installer folders
- Assign Operational Templates
- Deploy Operational Templates
- Windows OS component for the OMIMSSC console extension for SCCM
- Windows component for the OMIMSSC console extension for SCVMM
- Non-Windows component for the OMIMSSC console extension for SCCM/SCVMM
- Discovery in enrolled MSSC
- Importing server profile
- Export server profile
- Viewing LC logs
- Collect LC logs
- Part replacement
- Polling and notification
- Launch iDRAC
- Launch Input Output Module
- Resolving synchronization errors
- Synchronizing OMIMSSC with enrolled Microsoft console
- Deploy Azure Stack HCI cluster
- Trouble shooting scenarios
- Resources required for managing OMIMSSC
- Verifying permissions for using OMIMSSC console extension for SCCM
- Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM
- Install and upgrade scenarios in OMIMSSC
- Enrollment failure
- Failure of test connection
- 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
- 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 SCCM
- Empty cluster update group not deleted during autodiscovery or synchronization
- Failure to perform maintenance-related tasks on rediscovered servers
- Generic scenarios in OMIMSSC
- Firmware update scenarios in OMIMSSC
- Failure of creation of update source
- Failure to connect to FTP using system default update source
- Failure of test connection for local update source
- Failure to create DRM update source
- Failure to create repository during firmware update
- Failure to display comparison report after upgrading or migrating OMIMSSC
- 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 display latest inventory information after firmware update
- 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
- Appendix 2
- Accessing documents from the Dell EMC support site

NOTE: Irrespective of the selection made in the check box against each component, all the configurations are captured
in the template.
In Operating System component, perform the steps in either of the following options, as per your requirement:
● For Windows operating system deployment on SCCM, see Windows component for the OMIMSSC console extension for
SCCM.
● For Windows operating system deployment on SCVMM, see Windows component for the OMIMSSC console extension
for SCVMM.
● OMIMSSC
● For non-Windows operating system deployment, see Non-Windows component for the OMIMSSC console extensions.
8. To save the profile, click Finish.
Installer folders
The following folders are created after installing the console extension:
● Log—this folder consists of console-related log information.
NOTE: If the credentials for domain administrator account and local administrator account are different, do not use domain
administrator account to log in to SCCM or SCVMM. Instead use a different domain user account to log in to SCCM or
SCVMM.
Assign Operational Templates
1. In OMIMSSC click Configuration and Deployment, and then click Server View. Select the required servers and click
Assign Operational Template and Run Compliance.
The Assign Operational Template and Run Compliance page is displayed.
2. Select the required servers and click Assign Operational Template and Run Compliance.
3. In OMIMSSC click Configuration and Deployment, and click Modular Systems View. Select the required Modular
System and click Assign Operational Template .
The Assign Operational Template page is displayed.
4. Select the required Modular Systems, and click Assign Operational Template and Run Compliance.
The Assign Operational Template page is displayed.
5. Select the template from Operational Template drop-down menu, enter a job name, and then click Assign.
The Operational Template drop-down lists templates, of the same type as that of the devices selected in the previous step.
If the device is compliant to the template, and then a green color box with a check mark is displayed.
If the Operational Template is not applied successfully on the device or the hardware component in Operational Template is
not selected, and then an information symbol box is displayed.
If the device is noncompliant to the template, and then a warning symbol box is displayed. Only if the device is noncompliant
to assigned Operational Template, you can view a summary report by clicking the template name link. The Operational
Template Compliance-Summary Report page displays a summary report of the differences between the template and
device.
To view a detailed report, perform the following steps:
a. Click View Detailed Compliance. Here, the components with attribute values different from those of the assigned
template are displayed. The colors indicate the different states of Operational Template compliance.
● Yellow color warning symbol—non-compliance. represents that the configuration of the device does not match with
the template values.
● Red color box—represents that the component is not present on the device.
Configuration and deployment
87