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
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. Select the type of device, and enter the IP address of reference device, and then click Next.
NOTE: You can capture the configuration of reference server with iDRAC 2.0 and later.
4. In Device Components, click a component to view the available attributes and their values.
The components are as follows:
● Firmware update
● Hardware components, which are RAID, NIC, and BIOS.
NOTE: In iDRAC Embedded 1 component, following are the privileges and their values for User Admin Privilege
attribute.
Table 9. Privilege value table
Value Privilege
1 Login
2 Configure
4 Configure Users
8 Logs
16 System Control
32 Access Virtual Console
64 Access Virtual Media
128 System Operations
256 Debug
499 Operator Privileges
● Operating system—select either Windows, or ESXi, or RHEL.
5. 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.
6. 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.
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.
7. To save the profile, click Finish.
50
Managing Operational Templates