- Notes, cautions, and warnings
- 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
- Failure of firmware update on 11th generation of servers
- Changing of polling and notification bell color after updating the frequency
- Operating system deployment scenarios in OMIMSSC
- Operating system deployment generic scenarios
- Operating system deployment scenarios for SCCM users
- Operating system deployment scenarios for SCVMM users
- Hypervisor deployment failure due to LC or firewall protection
- Hypervisor deployment failure due to driver files retained in library share
- SCVMM error 21119 while adding servers to Active Directory
- Hypervisor deployment failure for 11th generation PowerEdge blade servers when using Active Directory
- LC driver injection failure
- S2D cluster creation scenarios for SCVMM users
- Server profile scenarios in OMIMSSC
- LC Logs scenarios in OMIMSSC
- Accessing documents from the Dell EMC support site
Dell EMC OpenManage Integration for Microsoft System Center Version 7.2 for System Center Configuration Manager and System Center Virtual Machine Manager Best Practices Guide
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:
- From SCVMM console, select and then select the IG server that was added as the library server.
- In the library server, select and delete the library share.
- After the library share is deleted, connect to the IG share using \\<Integration Gateway server>\LCDriver\.
- Delete the folder that contains the driver files.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\