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

Creating Operational Template from reference
Modular Systems
Before creating Operational Template, ensure that you complete the following tasks:
● Discover a Modular System by using the Discovery feature. For information about discovering Modular Systems, see
Discovering Modular System using manual discovery.
● If you are not using the default update source, and then create an update source. For more information, see Creating update
source.
You can create an Operational Template by capturing the configuration of the reference Modular Systems. After capturing the
configuration, you can directly save the template, or edit the attributes for update source and hardware configuration as per
your requirement. Now you can save the template, that can be used to configure other Modular Systems of the same model.
NOTE: If you want to configure Active Directory (AD) users on other MX7000 devices ensure that you create an
Operational Template from an MX7000 Modular System where all the AD users are configured.
NOTE: User account’s passwords are not captured in Operational Template, from reference Modular System for security
reasons. Edit the Operational Template to add a new user account and password, and then apply the Operational Template
on the managed Modular Systems. Else, you can apply the Operational Template without any changes to user accounts, and
the same passwords that are used in the reference Modular System are applied on the managed Modular System.
1. In OMIMSSC, do any of the following to open an Operational Template:
● In the OMIMSSC dashboard, click Create Operational Template.
● In the navigation pane, click Profiles > Operational Template, and then click Create.
The Operational Template wizard is displayed.
2. Enter a name and description for the template.
3. In Device Components, click a component to view the available attributes and their values.
The components are as follows:
● Firmware update
● Management Module Embedded
NOTE:
Ensure that the Web Server attribute is enabled. If this component is not enabled, and then the MX7000
Modular Systems cannot be accessed through OMIMSSC after deploying the Operational Template.
NOTE: For SNMP Configuration and Syslog Configuration, ensure that you select all four configurations
available in each attribute, to apply them on managed devices.
4. Use the horizontal scroll bar to locate a component. Select the component, expand a group, and then edit its attribute
values. Use the vertical scroll bar to edit a groups and attributes of a component.
5. Select the check box against each component, because, the configurations of selected components are applied on the
managed device, when the Operational Template is applied. However, all the configurations from the reference device are
captured and saved in the template.
6. To save the profile, click Finish.
Viewing Operational Template
To view Operational Templates created:
In OMIMSSC console, click Profiles and Templates, and then click Operational Template. All the templates that are created
are listed here.
Modifying Operational Template
You can modify the update source, hardware configurations, and operating system of an operational template.
Consider the following before modifying an Operational Template:
52
Managing Operational Templates