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
Changing of polling and notification bell color after updating the
frequency
If a managed server is not discovered in OMIMSSC, and you change the frequency of polling and notification option, the bell
color changes to yellow after sometime, even if there are no changes in the catalog.
As a workaround, discover managed servers and then change the frequency of polling and notification option.
Operating system deployment scenarios in OMIMSSC
This section has all the troubleshooting information related to operating system, or hypervisor (for SCVMM) deployment using
Operational Template in OMIMSSC.
Operating system deployment generic scenarios
This section has all the generic troubleshooting information related to operating system deployment.
Failure to deploy Operational Template
After deploying the Operational Template on the selected servers, the attributes or attribute values are not appropriate for the
selected .CSV file, or the iDRAC IP or iDRAC credentials are changed due to the configurations in the template. The job in
iDRAC is successful, however the status of this job in OMIMSSC is shown as unsuccessful or failure due to invalid .CSV file, or
the job cannot be tracked due to the iDRAC changes on the target server.
As a workaround, ensure the selected .CSV file has all the proper attributes and attribute values, and the iDRAC IP or
credentials do not change due to the configurations in the template.
Failure to save an Operational Template
When you are creating an Operational Template, if you select and clear a dependent attribute’s check box having pool value, you
are not able to save the Operational Template with the following error message:
Select atleast one attribte, under the selected components, before creating the
Operational Template.
As a workaround, perform any one of the following:
● Select any other dependent attribute having pool value or the same dependent attribute and save the Operational Template.
● Create a new Operational Template.
Failure to deploy Windows Server 2016 operating system on AMD servers
Windows Server 2016 operating system deployment on AMD platforms does not support x2apic. Hence the operating system
deployment fails.
As a workaround, edit the operational template used for deployment, select the BIOS component, and disable the BIOS x2apic
and logical processor settings. Then retry the deployment using this template. For more information see Dell EMC AMD Server
will hang on the Windows Logo while installing Windows Server 2016 KB article.
100
Troubleshooting