Host Profiles ensure all hosts in the cluster have the same configuration.

Procedure

  1. Log in to vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://lax01m01vc01.lax01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. Create a Host Profile from lax01m01esx01.lax01.rainpole.local
    1. In the Navigator, select Hosts and Clusters and expand the lax01m01vc01.lax01.rainpole.local tree.
    2. Right-click the ESXi host lax01m01esx01.lax01.rainpole.local and select Host Profiles > Extract Host Profile.
    3. In the Extract Host Profile window, enter lax01-m01hp-mgmt01 for the Name and click Next.
    4. In the Ready to complete page, click Finish.
  3. Attach the Host Profile to the management cluster.
    1. In the Navigator, select Hosts and Clusters and expand the lax01m01vc01.lax01.rainpole.local tree.
    2. Right-click on the lax01-m01-mgmt01 cluster and select Host Profiles > Attach Host Profile.
    3. In the Attach Host Profile window, click the lax01-m01hp-mgmt01 Host Profile, select the Skip Host Customization checkbox and click Finish.
  4. Create a Host Customizations profile for the hosts in the management cluster.
    1. In the Navigator, select Policies and Profiles.
    2. Click Host Profiles, then right click lax01-m01hp-mgmt01 and choose Export Host Customizations.
    3. Click Save.
    4. Select a file location to save the lax01-m01hp-mgmt01_host_customizations.csv file.
    5. Open the lax01-m01hp-mgmt01_host_customizations.csv in Excel.
    6. Edit the Excel file to include the following values.

      ESXi Host

      Active Directory Configuration Password

      Active Directory Configuration Username

      NetStack Instance defaultTcpipStack->DNS configuration

      Name for this host

      NetStack Instance vmotion->DNS configuration

      lax01m01esx01.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      lax01m01esx01

      lax01m01esx01

      lax01m01esx02.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      lax01m01esx02

      lax01m01esx02

      lax01m01esx03.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      lax01m01esx03

      lax01m01esx03

      lax01m01esx04.lax01.rainpole.local

      ad_admin_password

      ad_admin_acct@lax01.rainpole.local

      lax01m01esx04

      lax01m01esx04

      ESXi Host

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-management:management->IP address settings

      Host IPv4 address

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-management:management->IP address settings

      SubnetMask

      lax01m01esx01.lax01.rainpole.local

      172.17.11.101

      255.255.255.0

      lax01m01esx02.lax01.rainpole.local

      172.17.11.102

      255.255.255.0

      lax01m01esx03.lax01.rainpole.local

      172.17.11.103

      255.255.255.0

      lax01m01esx04.lax01.rainpole.local

      172.17.11.104

      255.255.255.0

      ESXi Host

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-nfs:<UNRESOLVED>->IP address settings

      Host IPv4 address

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-nfs:<UNRESOLVED>->IP address settings

      SubnetMask

      lax01m01esx01.lax01.rainpole.local

      172.17.15.101

      255.255.255.0

      lax01m01esx02.lax01.rainpole.local

      172.17.15.102

      255.255.255.0

      lax01m01esx03.lax01.rainpole.local

      172.17.15.103

      255.255.255.0

      lax01m01esx04.lax01.rainpole.local

      172.17.15.104

      255.255.255.0

      ESXi Host

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-replication:vSphereReplication,vSphereReplicationNFC->IP address settings

      Host IPv4 address

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-replication:vSphereReplication,vSphereReplicationNFC->IP address settings

      SubnetMask

      lax01m01esx01.lax01.rainpole.local

      172.17.16.101

      255.255.255.0

      lax01m01esx02.lax01.rainpole.local

      172.17.16.102

      255.255.255.0

      lax01m01esx03.lax01.rainpole.local

      172.17.16.103

      255.255.255.0

      lax01m01esx04.lax01.rainpole.local

      172.17.16.104

      255.255.255.0

      ESXi Host

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-vsan:vsan->IP address settings

      Host IPv4 address

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-vsan:vsan->IP address settings

      SubnetMask

      lax01m01esx01.lax01.rainpole.local

      172.17.13.101

      255.255.255.0

      lax01m01esx02.lax01.rainpole.local

      172.17.13.102

      255.255.255.0

      lax01m01esx03.lax01.rainpole.local

      172.17.13.103

      255.255.255.0

      lax01m01esx04.lax01.rainpole.local

      172.17.13.104

      255.255.255.0

      ESXi Host

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-vmotion:vmotion->IP address settings

      Host IPv4 address

      Host virtual NIC lax01-m01-mgmt01:lax01-m01-mgmt01-vmotion:vmotion->IP address settings

      SubnetMask

      lax01m01esx01.lax01.rainpole.local

      172.17.12.101

      255.255.255.0

      lax01m01esx02.lax01.rainpole.local

      172.17.12.102

      255.255.255.0

      lax01m01esx03.lax01.rainpole.local

      172.17.12.103

      255.255.255.0

      lax01m01esx04.lax01.rainpole.local

      172.17.12.104

      255.255.255.0

    7. When you have updated the Excel file, save it in the CSV file format and close Excel.
    8. Click the Configure tab.
    9. Click the Edit Host Customizations button.
    10. In the Edit Host Customizations window select all hosts and click Next.
    11. Click the Browse button to use a customization file, locate the lax01-m01hp-mgmt01_host_customizations.csv file saved earlier and select it and click Open then click Finish.
  5. Remediate the hosts in the management cluster .
    1. Click the Monitor tab and click Compliance.
    2. Select lax01-m01-mgmt01 and click the Check Host Profile Compliance button.
    3. Select lax01m01esx02.lax01.rainpole.local, click the Remediate host based on its host profile button, and click Finish in the Ready to complete window.
    4. Select lax01m01esx03.lax01.rainpole.local, click the Remediate host based on its host profile button, and click Finish in the Ready to complete window.
    5. Select lax01m01esx04.lax01.rainpole.local, click the Remediate host based on its host profile button, and click Finish in the Ready to complete window.

      All hosts should show a Compliant status in the Host Compliance column.

  6. Schedule nightly compliance checks.
    1. On the Policies and Profiles page, click lax01-m01hp-mgmt01, click the Monitor tab, and click the Scheduled Tasks sub-tab.
    2. Click Schedule a New Task and click Check Host Profile Compliance.
    3. In the Check Host Profile Compliance (scheduled) window, click Scheduling Options.
    4. Enter lax01-m01hp-mgmt01 Compliance Check in the Task Name field.
    5. Click the Change button on the Configured Scheduler line.
    6. In the Configure Scheduler window, select Setup a recurring schedule for this action and change the Start time to 10:00 PM and click OK.
    7. Click OK in the Check Host Profile Compliance (scheduled) window.