Manualshelf

FAQ

ManualsBrandsDell ManualsActive System ManagerOpenManage Integration Version 7.2 for Microsoft System Center
16171819202122232425
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.
Hypervisor deployment failure for 11th generation
PowerEdge blade servers when using Active Directory
Hypervisor deployment fails on the 11th generation PowerEdge blade servers when using the Active Directory user credentials. The 11th
generation PowerEdge blade servers use the Intelligent Platform Management Interface (IPMI) protocol for communication. However, the
IPMI standard is not supported for using credentials from the Active Directory setup.
As a workaround to deploy operating systems on these servers, use supported credential profiles.
LC driver injection failure
When deploying OS and injecting LC drivers using SC2012 VMM, the OS is deployed successfully but, the LC drivers are not injected.
To resolve the issue, apply the latest rollup for SCVMM.
S2D cluster creation scenarios for SCVMM users
This section has all the troubleshooting information related to creating Storage Spaces Direct using OMIMSSC in SCVMM console.
Health status of S2D cluster is unknown
When you create a Storage Spaces Direct cluster on nodes that were part of an existing cluster, then the storage pool and the disk
configurations have the configurations of the existing cluster. Hence, the cluster storage pool might not be created and if the cluster
storage pool is created the health status may be displayed as unknown.
As a workaround, clear the storage pool and disk configuration having existing cluster details and then create the Storage Spaces Direct
cluster. For more information on clearing the storage pool, see Troubleshoot Storage Spaces Direct health and operational states section
from Microsoft documentation.
22
Operating system deployment scenarios in OMIMSSC