Users Guide

Hosts using Lifecycle Controller can update from a custom repository which is hosted on a accessible network shared
folder. To create a custom repository, Dell recommends using Dell Repository Manager to create it and then save it to a
shared location where the hosts and OpenManage Integration can access it. Enter the location of the repository's catalog
file below.
3. If you select Shared Network Folderenter the full the of catalog file in the Catalog File Location field
4. Click Begin Test.
5. Click Apply.
Server Security using White list
Restrict the set of deployable servers using a white list. If a server is in the white list, it is provided with credentials during the
Auto-Discovery and handshake process and is displayed in the list of servers that are used for deployment. The white list is
maintained by manually adding server service tags, deleting service tags, or importing a list of service tags from a CSV file.
WARNING: This feature is not functional in this release for security reasons.
About Host, Bare Metal, and iDRAC Compliance Issues
To manage hosts, bare metal servers, and iDRAC with the OpenManage Integration for VMware vCenter each must meet
certain minimum criteria. If not compliant, then they are not managed properly by the OpenManage Integration for VMware
vCenter. Use the Fix Non-Compliant Hosts, Bare Metal Server, and iDRAC compliance links to see which host/bare metal
servers/iDRACs in your configuration are not compliant and fix them. This wizard displays hosts/bare metal servers/iDRACs
where:
● Hosts have not been assigned to a connection profile.
If a connection profile is not assigned to a host, a dialog box is offered to take you to the Connection Profile screen. This
configuration is outside this wizard. Return later to run this wizard.
● Collect System Inventory on Reboot (CSIOR) is disabled or has not been run, which requires a manual reboot.
● The OMSA agent (Host Root credentials ) is not installed, is out of date, or not configured properly.
● Bare metal servers have outdated Integrated Dell Remote Access Controller (iDRAC) firmware, Lifecycle Controller (LC)
firmware, or BIOS versions.
CAUTION:
Hosts in Lockdown Mode will not appear in compliance checks even if they are non-compliant. They
do not display because their compliance status cannot be determined. Make sure to check the compliance of
these systems manually. When this is the case a warning displays.
In each case, you need to fix the compliance issues by running one of the following:
● To fix vSphere host compliance issues, see Running The Fix Non-Compliant vSphere Hosts Wizard
● To fix bare metal servers that have compliance issues, see Running The Fix Non-Compliant Bare Metal Server Wizard
● To fix iDRAC compliance issues: iDRAC License Compliance
Related Information:
● Re-Checking Bare Metal Server Compliance
Running The Fix Non-Compliant vSphere Hosts Wizard
Run the Fix Non-Compliant vSphere Hosts Wizard to fix non-compliant hosts. For information about compliance, see About
Host And Bare Metal Compliance Issues. Some non-compliant ESXi hosts require reboots. An ESXi host reboot is required if
OpenManage Server Administrator (OMSA) must be installed or updated. In addition, a reboot is required on any host that has
never run CSIOR. If you select to automatically reboot an ESXi host, the following actions take place:
● For a CSIOR status fix:
If CSIOR is not enabled on the host, you can enable CSIOR on the host, and then the host is set into maintenance mode and
rebooted.
● For an OMSA status fix:
1. OMSA is installed on the host.
2. The host is set to maintenance mode and rebooted.
3. After the reboot completes, OMSA is configured for the changes to take effect.
Steps to Configure or Edit the OpenManage Integration for VMware vCenter
25