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
Viewing System Lockdown Mode
The System Lockdown Mode setting is available in iDRAC for 14
th
generation of servers and later. The setting when turned on
locks the system configuration including firmware updates. After the System Lockdown mode is enabled, users cannot change
any configuration settings. This setting is intended to protect the system from unintentional changes. To perform any operations
on the managed servers, ensure that you disable the setting on it’s iDRAC console. In OMIMSSC console, the System Lockdown
mode status is represented with a lock image before the iDRAC IP address of the server.
● A lock image is displayed along with the servers’s iDRAC IP if the setting is enabled on that system.
● An unlocked image is displayed along with the servers’s iDRAC IP if the setting is disabled on that system.
NOTE: Before launching the OMIMSSC console extensions, verify the iDRAC System Lockdown Mode setting on the
managed servers.
For more information about iDRAC System Lockdown Mode, see iDRAC documentation available at dell.com/support.
Deleting servers from OMIMSSC
To delete a server, perform the following steps:
Consider the following points before deleting a server:
● After you delete a server, the consumed license is relinquished.
● You can delete a server that is listed in OMIMSSC based on the following criteria:
○ An unassigned server that is listed in the Unassigned servers tab.
○ If you delete a host server that is provisioned in enrolled SCCM or SCVMM and present in OMIMSSC under the Hosts
tab, first delete the server in SCCM or SCVMM, and then delete the server from OMIMSSC.
1. In the OMIMSSC console, click Configuration and deployment, and then click Server View:
● To delete unassigned servers—in the Unassigned Servers tab, select the server, and click Delete.
● To delete host servers—in the Host Servers tab, select the server, and click Delete.
2. In the confirmation dialog box, click Yes.
Deleting Modular Systems from OMIMSSC
To delete a Modular System, perform the following steps:
1. In OMIMSSC console, click Configuration and deployment, and then click Modular Systems View.
2. Select the Modular Systems, and click Delete.
42
Discovering devices and synchronizing servers with MSSC console