Users Guide

● 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, then CSIOR is set to ON 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.
4. The host comes out of maintenance mode.
5. Inventory is run to refresh data.
To run the Fix Non-Compliant vSphere Hosts Wizard:
1. In the Dell Management Center, in the left pane, click Compliance > vSphere Hosts.
2. In the vSphere Host Compliance window, view the noncompliant hosts, then click Fix Non-Compliant vSphere Hosts.
3. In the Fix Non-Compliant vSphere Hosts wizard, select the check boxes for the hosts you want to fix.
4. Click Next.
5. If there is a server without a connection profile, you are given the option to exit the wizard and fix these systems from the
Connection Profile page, or continue with this wizard. See, Creating A New Connection Profile. When done, return to this
wizard.
6. In the Turn On CSIOR window, select the check boxes to turn on CSIOR for the selected hosts.
7. Click Next.
8. In the Fixing OMSA window, select the check boxes to fix OMSA for the selected hosts.
9. Click Next.
10. In the Reboot Hosts window, view the ESXi hosts that must be rebooted. An ESXi host reboot is required if OMSA must be
installed or updated. In addition, a reboot is required on any host that has never run CSIOR. Do one of the following:
● If you want to automatically put hosts in maintenance mode and reboot when required, select the Automatically put
hots in maintenance mode and reboot whenever required check box.
● If you want to reboot manually, you must do the following:
a. Once the Install OMSA task is completed for a host, reboot the host.
b. Once the host is up and if OMSA is not configured, configure OMSA manually or use the Compliance Wizard.
c. Re-run inventory, see Running Inventory Jobs.
11. Click Next.
12. In the Summary window, review the actions that take place on the non-compliant hosts. Manual reboots are required for
these to take effect.
13. Click Finish.
Steps to Configure or Edit the OpenManage Integration for VMware vCenter
27