OpenManage Integration for VMware vCenter Version 4.0 Web Client User's Guide

Reporting and fixing compliance for vSphere hosts

1. In OpenManage Integration for VMware vCenter, from the Manage tab, click Compliance > vSphere Hosts.
   1. In the vSphere Hosts page, view the list of noncompliant hosts.
      A table is displayed that lists the noncompliant hosts along with the host IP or host name, model, connection profile, the CSIOR status, OMSA status, hypervisor, and the iDRAC license status.
   2. To view further details of a noncompliant host, select a noncompliant host.
   3. To swap the columns within the table, drag and drop columns within the data grid.
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.