Users Guide
Table Of Contents
- Dell Lifecycle Controller Integration Version 1.3 for Microsoft System Center Virtual Machine Manager User’s Guide
- Contents
- About Dell Lifecycle Controller Integration for Microsoft System Center Virtual Machine Manager
- Installing and setting up DLCI Console Add-in
- Getting Started
- Workflows
- About golden configurations
- Creating golden configurations
- Creating, managing, and deleting credential profiles
- Creating, managing, and deleting update sources
- Creating, managing, and deleting custom update groups
- Applying updates on servers
- Creating, managing, and deleting protection vaults
- Exporting server profile
- Importing server profile
- Hypervisor deployment
- Deleting servers
- Configuring replaced components
- Collecting and viewing LC logs
- Setting up the environment for deploying hypervisors
- Server discovery
- System requirements for managed systems
- Enabling CSIOR in managed systems
- Discovering servers using auto discovery
- Discovering servers using manual discovery
- Deleting servers from DLCI Console
- Viewing device inventory
- Synchronization with SCVMM
- Synchronizing appliance with SCVMM
- Resolving synchronization errors
- Launching iDRAC Console
- License for the appliance
- Server management
- Profiles and templates
- About credential profile
- Creating hardware profile
- Modifying hardware configuration profile
- Deleting hardware profile
- Creating hypervisor profile
- Modifying hypervisor profile
- Deleting hypervisor profile
- WinPE Update
- About hypervisor deployment
- Creating deployment template
- Modifying deployment template
- Deleting deployment template
- Deploying hypervisors
- Viewing information in appliance
- Troubleshooting
- Empty cluster update group does not get deleted during autodiscovery or synchronization
- Discovery jobs not submitted
- Duplicate VRTX chassis group gets created
- Exporting configuration profile of another server after IP address is changed
- Failure applying RAID configuration
- Failure of creation of update source
- Failure of firmware update because of job queue being full
- Failure of firmware update while using DRM update source
- Failure of a scheduled job on an update group
- Failure of firmware update on cluster update group
- Failure of firmware update on 11th generation of servers
- Failure to connect to FTP using system default update source
- Failure to create a repository during a firmware update
- Failure to delete a custom update group
- Failure to export LC logs in CSV format
- Failure to view LC logs
- Failure to export server profiles
- Firmware update on a few components irrespective of the selection
- IG installation issue while running multiple instances of the installer on the same server
- Importing server profile job gets timed out after two hours
- Hypervisor deployment failure
- Hypervisor deployment failure due to driver files retained in library share
- Latest inventory information is not displayed even after firmware update
- SCVMM error 21119 while adding servers to active directory
- Hypervisor deployment fails for 11th generation PowerEdge blade servers when using Active Directory
- RAID configuration failure for virtual disks with RAID10
- Configuration of RAID failure due to configuration of hot spares on software RAID S130
- Accessing support content from the Dell EMC support site
Duplicate VRTX chassis group gets created
When modular servers that were previously in another chassis are added to a VRTX chassis and discovered, the modular servers
carry previous chassis service tag information and create a duplicate VRTX chassis group in the appliance.
To resolve, do the following:
1. Remove a modular server from one chassis, and add it in another chassis. For more information, see Server modules section
in Dell PowerEdge VRTX Enclosure Owner's Manual.
2. Configure CMC. For more information, see Installing and Setting Up CMC in Chassis Management Controller Version 2.1 for
Dell PowerEdge VRTX User's Guide, available at dell.com/support /home.
After you do the preceding tasks, if there are duplicate chassis group entries, then as a workaround, do the following:
1. Enable CSIOR and reset iDRAC on the newly added modular server.
2. Manually delete all the servers in the VRTX chassis group, and then rediscover the servers.
Exporting configuration profile of another server after
IP address is changed
After an Export Server Profile job on a server is scheduled, if the IP address of this server is assigned to another server, then
the appliance exports the server profile of this new server.
As a workaround, cancel the Export Server Profile job, rediscover the server whose IP address has changed, and then
schedule the Export Server Profile job on this server.
Failure applying RAID configuration
Applying a hardware profile with RAID configuration may fail with the following error messages: Error An unknown
exception has occurred and has been logged in the extended logs.
Error RAID configuration failed with error: An unknown exception has occurred and has been
logged in the extended logs. <iDRAC IP address>
Error 0_EX_MSG
As a workaround, do a Power Cycle System for the server and reapply the hardware configuration.
Failure of creation of update source
When the Domain Name System (DNS) network configuration of the appliance is changed, creation of HTTP or FTP type of
update source fails.
As a workaround, restart the appliance, and then create the update source of type HTTP or FTP.
Failure of firmware update because of job queue being
full
Firmware update jobs submitted from the appliance to iDRAC fail, and the appliance main log displays the following error:
JobQueue Exceeds the size limit. Delete unwanted JobID(s).
As a workaround, manually delete the completed jobs in iDRAC, and retry the firmware update job. For more information on
deleting jobs in iDRAC, see iDRAC documentation at dell.com/support/home.
Troubleshooting
47