Users Guide
• To configure host credentials without Active Directory, perform the following actions:
○ In the User Name text box, the user name is root.
The root user name is the default user name, and you cannot change it.
NOTE: If Active Directory is set, you can choose any Active Directory user name and not root.
○ In the Password text box, type the password. The password is limited to 127 characters.
○ In the Verify Password text box, type the password again.
○ For certificate check, select one of the following:
▪ To download and store the host certificate and validate it during all future connections, select Enable Certificate
Check.
▪ To not perform any check and not store the host certificate, do not select Enable Certificate Check.
NOTE: The OMSA credentials are the same credentials used for the ESXi hosts.
4. Click Next.
5. In the Select Hosts window, select hosts for this connection profile and click OK.
6. In the Associated Hosts page, add one or more hosts for the connection profile, if required.
To add hosts, click , select hosts, and then click OK.
NOTE: If the OEM hosts are not displayed on the Select Hosts window, add the OEM hosts using the Add OEM Hosts
wizard. For more information about adding OEM hosts, see Adding OEM Hosts.
7. To test the connection profile, select one or more hosts and click .
NOTE:
This step is optional and verifies whether the host and iDRAC credentials are correct. Although this step is
optional, it is recommended that you to test the connection profile.
NOTE: If the WBEM service is disabled for all hosts running ESXi 6.5 or later, WBEM is automatically enabled when
you perform the test connection and inventory on those hosts.
NOTE: If you select All Registered vCenter while creating the connection profile, test connection fails for all hosts
running ESXi 6.5 or later that has the WBEM service disabled. In such case, it is recommended to complete the
connection profile wizard actions, run the inventory on hosts, and then test the connection profile again.
NOTE: : Do not add an MX server having iDRAC IPv4 disabled to a connection profile. These servers can be managed
using a chassis profile.
NOTE: You may see test connection is failing for the host and indicating that invalid credentials are entered, even
after entering valid credentials. It may happen because the ESXi is blocking the access. At this point, wait for 15
minutes and retry the test connection.
8. To complete the profile creation, click Next.
For servers that do not have either an iDRAC Express or Enterprise card, the iDRAC test connection result states Not Applicable for
this system.
After hosts are added to connection profile, the IP address of OMIVV is automatically set to SNMP trap destination of host's iDRAC, and
OMIVV automatically enables the Web-Based Enterprise Management (WBEM) service for hosts running ESXi and later. OMIVV uses the
WBEM service to properly synchronize the ESXi host and the iDRAC relationships. If configuring the SNMP trap destination fails for
particular hosts, and/or enabling the WBEM service fails for particular hosts, those hosts are listed as noncomplaint. To view the
noncomplaint hosts that require SNMP trap destination to be reconfigured and/or WBEM services to be enabled, see Running the fix
noncompliant vSphere hosts wizard.
Modifying connection profile
After you create a connection profile, you can edit the profile name, description, associated hosts and iDRAC, and host credentials.
NOTE:
The vCenters listed during this procedure are authenticated using the same Single Sign On (SSO). If you cannot
view a vCenter host, it might be on a different SSO or you might be using a VMware vCenter version earlier than version
5.5.
48 Profiles