Users Guide
Table Of Contents
- OpenManage Integration for Microsoft System Center Version 7.3 for Microsoft Endpoint Configuration Manager and System Center Virtual Machine Manager Unified User’s Guide
- Contents
- Introduction to OMIMSSC
- OMIMSSC license
- OMIMSSC components
- Support Matrix for OMIMSSC
- Deploy OMIMSSC
- Enroll Microsoft console in OMIMSSC
- Manage OMIMSSC and its components
- Backup and Restore OMIMSSC Appliance
- Uninstall OMIMSSC
- Upgrade OMIMSSC
- Manage Credential and Hypervisor profiles
- Discover devices and sync servers with OMIMSSC console
- Remove devices from OMIMSSC
- Views in OMIMSSC
- Manage Operational Templates
- Predefined Operational Templates
- About reference server configuration
- About reference Modular System configuration
- Create Operational Template from reference servers
- Create Operational Template from reference Modular Systems
- Create clusters using Operational Template
- View Operational Template
- Edit Operational Template
- Configure system specific values (Pool values) using Operational Template on multiple servers
- Assign Operational Template and Run Operational Template Compliance for servers
- Deploy Operational Templates
- Unassign Operational Template
- Delete Operational Template
- Deploy operating system using OMIMSSC
- Provision devices using OMIMSSC
- Update firmware using OMIMSSC
- Manage devices using OMIMSSC
- Deploy Azure Stack HCI cluster
- Troubleshooting
- Resources required for managing OMIMSSC
- Verifying permissions for using OMIMSSC console extension for MECM
- Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM
- Install and upgrade scenarios in OMIMSSC
- Enrollment failure
- Failure of test connection
- Failure to launch OMIMSSC after installing MECM console extension
- 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
- Failure to auto discover iDRAC 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 MECM
- Empty cluster update group not deleted during autodiscovery or synchronization
- Failure to create cluster while applying cluster features
- Unable to retrieve the Cluster Aware Update job status
- Failure to perform maintenance-related tasks on rediscovered servers
- Generic scenarios in OMIMSSC
- Firmware update scenarios in OMIMSSC
- Failure of test connection for local update source
- Failure to create DRM update source
- Failure to create repository during firmware update
- 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 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 I: Time zone attribute values
- Appendix II: Populate Pool values
- Accessing support content from the Dell EMC support site
Unable to synchronize host servers with enrolled MECM
During synchronization of OMIMSSC console extension with enrolled MECM, the servers are not listed as sub tasks in
synchronization job and hence does not get synchronized.
As a workaround, launch MECM console with "Run as Administrator Privilege" and update out of band configuration for a server.
Then synchronize OMIMSSC console extension with enrolled MECM.
For more information, see Synchronizing with enrolled Microsoft console topic in OpenManage Integration for Microsoft System
Center Version 7.3 for Microsoft Endpoint Configuration Manager and System Center Virtual Machine Manager Unified User's
Guide.
Empty cluster update group not deleted during autodiscovery or
synchronization
When a cluster is discovered in OMIMSSC, a cluster update group gets created in the Maintenance Center with all the servers
listed in the cluster update group. Later, if all the servers are removed from this cluster through SCVMM, and an autodiscovery
or synchronization with SCVMM operation is performed, the empty cluster update group is not deleted in Maintenance
Center.
As a workaround, to delete the empty server group, rediscover the servers.
Failure to create cluster while applying cluster features
When cluster creation fails on nodes while applying cluster features, and the operating system deployment is successful.
During cluster creation an error message, Failed to install the features on hosts that are required for
creating clusters is displayed and the logs display, Failed to run Pre Cluster Creation Scripts on Host
Create Cluster.
As a workaround, ensure that the Computer Access Credential selected in Physical Computer Profile used for cluster
creation is same as the Enrolled User. The enrolled user should be either a domain admin or domain user with privileges to add
system to the domain.
Unable to retrieve the Cluster Aware Update job status
When the Cluster Aware Update job status post the update job completion.
As a workaround, check the job status using Microsoft Failover Cluster Manager tool and ensure to delete OMIMSSC created
files in SCVMM server post job completion.
Failure to perform maintenance-related tasks on rediscovered
servers
When you delete a server or all the servers in an update group from OMIMSSC, and rediscover them you cannot perform
any other operations on these servers like updating firmware, exporting and importing LC logs, exporting and importing server
profiles.
As a workaround, after rediscovering the deleted server or servers, perform firmware updates using the Deploy Operational
Template feature in Server View and for other maintenance scenarios use iDRAC.
96
Troubleshooting