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
As a workaround, install the SCCM client server, and then perform a synchronization to add the servers in Managed Lifecycle
Controller Lifecycle Controller (ESXi) collection.
Operating system deployment scenarios for SCVMM users
This section has all the troubleshooting information related to hypervisor deployment using OMIMSSC in SCVMM console.
Hypervisor deployment failure due to LC or firewall protection
Hypervisor deployment fails displaying the following error message in activity log: Error New-SCVMHost failed with
following error : An out of band operation (SMASH) for the BMC <IP ADDRESS> failed on IDRAC
IP : <IP ADDRESS>.
This error may occur due to one of these reasons:
● Dell Lifecycle Controller’s state is bad.
As resolution, log in to iDRAC user interface and reset Lifecycle Controller.
After resetting Lifecycle Controller, if you still face the problem try the following alternative:
● The antivirus or firewall may restrict the successful run of the WINRM command.
See the following KB article for workaround: support.microsoft.com/kb/961804
Hypervisor deployment failure due to driver files retained in library share
Hypervisor deployment fails displaying the following error message in activity log:
● Error: Error while applying Hypervisor Profile to host <IP Address>. Failed with error :
For input string: ""
● Information: Successfully deleted drivers from library share
sttig.<MicrosoftConsoleName>.com for <server uuid>
● Error: Deleting staging share (drivers) for <server uuid> failed.
These errors may occur due to exception output by the VMM command-let GET-SCJOB status and driver files are retained
in the library share. Before you retry or do another hypervisor deployment you must remove these files from the library share.
To remove files from library share:
1. From SCVMM console, select Library > Library Servers and then select the IG server that was added as the library server.
2. In the library server, select and delete the library share.
3. After the library share is deleted, connect to the IG share using \\<Integration Gateway server>\LCDriver\.
4. Delete the folder that contains the driver files.
After this, you can deploy the hypervisors.
SCVMM error 21119 while adding servers to Active Directory
While adding servers to Active Directory, SCVMM error 21119 is displayed. Error 21119: The physical computer
with <SMBIOS GUID> did not join Active Directory in time. The comptuer was expected to join
Active Directory using the computer name <host.domain>.
As a workaround, do the following:
1. Wait for some time to see if the server is added to the Active Directory.
2. If the server is not added to the Active Directory, then manually add the servers to the Active Directory.
3. Add the server in to SCVMM.
4. After the server is added in to SCVMM, rediscover the server in OMIMSSC.
The server will now be listed under the Host tab.
104
Trouble shooting scenarios