Users Guide

2. To fix noncomplaint hosts, click Fix non-compliant vSphere Hosts.
The Fix Non-compliant vSphere Hosts wizard is launched. This is a dynamic wizard and only those pages are displayed that are
related to the selected noncompliant hosts.
If all the selected noncompliant hosts are CSIOR-compliant, you can view the Turn On CSIOR page in the wizard.
3. In the Fix Non-compliant vSphere Hosts wizard, click Next in the Welcome page.
4. In the Select vSphere Hosts to Fix Compliance wizard page, select the check boxes for the hosts you want to fix.
5. Click Next.
A warning message is displayed, if there are selected hosts that are not assigned to a connection profile and prompts you to either
continue with the compliance wizard or cancel the fix compliance wizard. To fix the connection profile noncompliance, do any one of
the following:
• To exclude the hosts without the connection profile assigned to it from the compliance wizard, click Continue Compliance
Wizard.
• To exit the wizard and fix the systems from the Connection Profile page, click Cancel. See Creating a connection profile. After
connection profile is created, you can return to the wizard.
6. If you click Continue Compliance Wizard for the warning message, in the Turn On CSIOR window, select the check boxes to turn
on CSIOR for the selected hosts.
7. Click Next.
8. In the Fix 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 is 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 hosts in
maintenance mode and reboot whenever required check box.
• If you want to reboot manually, reboot the host after installing OMSA, configure OMSA manually or through the compliance wizard
once the host is running and if OMSA is not configured, and run the inventory again. See Running Inventory Jobs.
11. Click Next.
12. In the Summary window, review the actions that take place on the noncompliant hosts.
Manual reboots are required for actions in the summary page to take effect.
13. Click Finish.
Fixing iDRAC license compliance for vSphere hosts
The vSphere hosts listed in the vSphere host compliance pages are noncompliant because they do not have a compatible iDRAC license.
The table displays the status of the iDRAC license. You can click a noncomplaint host to view more details such as, how many days are
remaining for the iDRAC license, and then you can update it, as required. If the Run inventory job link is disabled from the vSphere
Hosts page, there are no vSphere hosts that are noncompliant due to the iDRAC license.
1. In OpenManage Integration for VMware vCenter, from the Manage tab, click Compliance > vSphere Hosts.
2. Select a host where iDRAC License Status is Non-compliant.
3. If license is out of date, click the Purchase/Renew iDRAC License link.
4. Log in to the Dell License Management page and update or purchase a new iDRAC license.
Use the information in this page to identify and update your iDRAC.
5. After you install an iDRAC license, run an inventory job for the vSphere host and return to this page after the inventory job is
successfully complete for the host to be compliant.
Using OMSA with 11th generation servers
To manage the Dell PowerEdge 11th generation servers, OMIVV requires OMSA to be running on them. For an 11th generation host that is
deployed though OMIVV, OMSA is installed automatically. For 11th generation hosts that you deploy manually, you can choose either of
the following:
• Install and configure OMSA using OMIVV. See Setting up OMSA trap destination on page 106.
• Install and configure OMSA manually. See Deploying OMSA agent on ESXi system on page 106.
About host, bare-metal, and iDRAC compliance
105