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 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 ONLINE FTP MX7000 CATALOG is a predefined update source of type FTP, and is part of DELL ONLINE FTP
CATALOG.
DELL ONLINE HTTP MX7000 CATALOG is a predefined update source of type HTTP, and is part of DELL ONLINE HTTP
CATALOG.
DELL ONLINE HTTPS MX7000 CATALOG is a predefined default update source of type HTTPS, and is part of DELL ONLINE
HTTPS CATALOG.
Validating data using test connection
To verify if the location of the update source is reachable by using the credentials that are mentioned while creating the update
source, use Test Connection. Only after the connection is successful, you are enabled to create an update source.
Setting up local FTP
To set up local FTP:
1. Create a folder structure in your local FTP that is an exact replica of the online FTP, ftp.dell.com.
2. Download the catalog.gz file from online FTP and unzip the files.
3. Open the catalog.xml file and change the baseLocation to your local FTP URL, and compress the file with .gz
extension.
For example, change the baseLocation from ftp.dell.com to ftp.yourdomain.com.
4. Place the catalog file and the DUP files in your local FTP folder replicating the same structure as in ftp.dell.com.
Setting up local HTTP
To set up local HTTP:
1. Create a folder structure in your local HTTP that is an exact replica of downloads.dell.com.
2. Download the catalog.gz file from the online HTTP which is from the following location: http://
downloads.dell.com/catalog/catalog.xml.gz and extract the files.
3. Extract the catalog.xml file and change the baseLocation to your local HTTP URL, and compress the file with .gz
extension.
For example, change the baseLocation from downloads.dell.com to host name or IP address such as hostname.com.
4. Place the catalog file with the modified catalog file, and the DUP files in your local HTTP folder replicating the same
structure in downloads.dell.com.
Setting up local HTTPS
To set up local HTTPS:
1. Create a folder structure in your local HTTPS that is an exact replica of downloads.dell.com.
2. Download the catalog.gz file from the online HTTPS which is from the following location: https://
downloads.dell.com/catalog/catalog.xml.gz and extract the files.
3. Extract the catalog.xml file and change the baseLocation to your local HTTPS URL, and compress the file with .gz
extension.
For example, change the baseLocation from downloads.dell.com to host name or IP address such as hostname.com.
4. Place the catalog file with the modified catalog file, and the DUP files in your local HTTPS folder replicating the same
structure in downloads.dell.com.
Firmware update in OMIMSSC
67