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
Predefined Operational Templates
Predefined templates have all the configurations that are required to create Storage Spaces Direct clusters or Windows Server
Software-Defined (WSSD). OMIMSSC supports creating clusters on R740XD, R740XD2, and R640 Storage Spaces Direct
Ready Node models along with their specific network adapters.
Table 8. List of predefined Operational Templates
Operational Template name Description
R740XD_Mellanox_S2D_Template
Use this template for R740XD Storage Spaces Direct Ready
Node models having Mellanox card.
R740XD2_Mellanox_S2D_Template
Use this template for R740XD2 Storage Spaces Direct Ready
Node models having Mellanox card.
R740XD_QLogic_S2D_Template Use this template for R740XD Storage Spaces Direct Ready
Node models having QLogic card.
R740XD2_QLogic_S2D_Template Use this template for R740XD2 Storage Spaces Direct Ready
Node models having QLogic card.
R640_Mellanox_S2D_Template Use this template for R640 Storage Spaces Direct Ready
Node models having Mellanox card.
R640_QLogic_S2D_Template Use this template for R640 Storage Spaces Direct Ready
Node models having QLogic card.
Consider the following points before deploying an Operational Template:
● The predefined templates are available only for management systems running SCVMM 2016 and 2019.
● The predefined Storage Spaces Direct template shows NIC card in slot 1. However, while deploying the Operational Template
the NIC configuration is applied on the right slot. And if there are multiple NIC cards on the device, all the NIC cards are
configured with the same configuration that is specified in the Operational Template.
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 and capture the reference server settings in an Operational Template, and replicate it across
different servers with same hardware configuration.
Creating Operational Template from reference servers
Before creating Operational Template, ensure that you complete the following tasks:
● Discover a reference server by using the Discovery feature. For information about discovering servers, see Discovering
servers using manual discovery.
● For SCCM users:
○ Create a task sequence. For more information, see Creating task sequence.
○ For non-Windows operating system deployment, have a device type credential profile. For more information, see Creating
credential profile.
● For SCVMM users:
○ Create a hypervisor profile. For information about creating hypervisor profile, see Creating hypervisor profile.
○ For Windows deployment, have a device type credential profile. For more information, see Creating credential profile.
● 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 server. After capturing the
configuration, you can directly save the template, or edit the attributes for update source, hardware configuration, and Windows
component as per your requirement. Now you can save the template, which can be used on PowerEdge homogeneous servers.
Managing Operational Templates
49