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

1

Log in to the Management vCenter Server by using the vSphere Web Client.

a

Open a Web browser and go to https://mgmt01vc01.sfo01.rainpole.local/vsphere-client.

b

Log in using the following credentials.

Setting

Value

User name

administrator@vsphere.local

Password

vsphere_admin_password

2

Create a Host Profile from mgmt01esx01.sfo01.rainpole.local.

a

In the Navigator, select Hosts and Clusters and expand the mgmt01vc01.sfo01.rainpole.local tree.

b

Right-click mgmt01esx01.sfo01.rainpole.local and choose Host Profiles > Extract Host Profile.

c

In the Extract Host Profile window, enter SFO01-Mgmt01 as the name of the host profile and click Next.

d

On the Ready to complete page, click Finish.

3

Attach the Host Profile to the management cluster.

a

In the Navigator, select Hosts and Clusters and expand the mgmt01vc01.sfo01.rainpole.local tree.

b

Right-click the SFO01-Mgmt01 cluster, and choose Host Profiles > Attach Host Profile.

c

In the Attach Host Profile window, click SFO01-Mgmt01, select the Skip Host Customization box, and click Finish.

4

Create Host Customizations for the hosts in the management cluster.

a

Click on the Home icon and choose Policies and Profiles from the drop down menu.

b

In the Navigator, click Host Profiles.

c

Right-click SFO01-Mgmt01 and choose Export Host Customizations. Click Save.

d

Choose a safe place to store the SFO01-Mgmt01_host_customizations.csv that is generated.

e

Open the file with Excel.

f

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

mgmt01esx01.sfo01.rainpole.local

ad_admin_password

ad_admin_acct@sfo01.rainpole.local

mgmt01esx01

mgmt01esx02.sfo01.rainpole.local

ad_admin_password

ad_admin_acct@sfo01.rainpole.local

mgmt01esx02

mgmt01esx03.sfo01.rainpole.local

ad_admin_password

ad_admin_acct@sfo01.rainpole.local

mgmt01esx03

mgmt01esx04.sfo01.rainpole.local

ad_admin_password

ad_admin_acct@sfo01.rainpole.local

mgmt01esx04

ESXi Host

Host virtual NIC vDS-Mgmt:vDS-Mgmt-Management:management->IP address settings Host IPv4 address

Host virtual NIC vDS-Mgmt:vDS-Mgmt-Management:management->IP address settings SubnetMask

mgmt01esx01.sfo01.rainpole.local

172.16.11.101

255.255.255.0

mgmt01esx02.sfo01.rainpole.local

172.16.11.102

255.255.255.0

mgmt01esx03.sfo01.rainpole.local

172.16.11.103

255.255.255.0

mgmt01esx04.sfo01.rainpole.local

172.16.11.104

255.255.255.0

ESXi Host

Host virtual NIC vDS-Mgmt:vDS-Mgmt-NFS:<UNRESOLVED>->IP address settings Host IPv4 address

Host virtual NIC vDS-Mgmt:vDS-Mgmt-NFS:<UNRESOLVED>->IP address settingsSubnetMask

mgmt01esx01.sfo01.rainpole.local

172.16.15.101

255.255.255.0

mgmt01esx02.sfo01.rainpole.local

172.16.15.102

255.255.255.0

mgmt01esx03.sfo01.rainpole.local

172.16.15.103

255.255.255.0

mgmt01esx04.sfo01.rainpole.local

172.16.15.104

255.255.255.0

ESXi Host

Host virtual NIC vDS-Mgmt:vDS-Mgmt-VR:vSphereReplication,vSphereReplicationNFC->IP address settingsHost IPv4 address

Host virtual NIC vDS-Mgmt:vDS-Mgmt-VR:vSphereReplication,vSphereReplicationNFC->IP address settingsSubnetMask

mgmt01esx01.sfo01.rainpole.local

172.16.16.101

255.255.255.0

mgmt01esx02.sfo01.rainpole.local

172.16.16.102

255.255.255.0

mgmt01esx03.sfo01.rainpole.local

172.16.16.103

255.255.255.0

mgmt01esx04.sfo01.rainpole.local

172.16.16.104

255.255.255.0

ESXi Host

Host virtual NIC vDS-Mgmt:vDS-Mgmt-VSAN:vsan->IP address settings Host IPv4 address

Host virtual NIC vDS-Mgmt:vDS-Mgmt-VSAN:vsan->IP address settings SubnetMask

mgmt01esx01.sfo01.rainpole.local

172.16.13.101

255.255.255.0

mgmt01esx02.sfo01.rainpole.local

172.16.13.102

255.255.255.0

mgmt01esx03.sfo01.rainpole.local

172.16.13.103

255.255.255.0

mgmt01esx04.sfo01.rainpole.local

172.16.13.104

255.255.255.0

ESXi Host

Host virtual NIC vDS-Mgmt:vDS-Mgmt-vMotion:vmotion->IP address settings Host IPv4 address

Host virtual NIC vDS-Mgmt:vDS-Mgmt-vMotion:vmotion->IP address settings SubnetMask

mgmt01esx01.sfo01.rainpole.local

172.16.12.101

255.255.255.0

mgmt01esx02.sfo01.rainpole.local

172.16.12.102

255.255.255.0

mgmt01esx03.sfo01.rainpole.local

172.16.12.103

255.255.255.0

mgmt01esx04.sfo01.rainpole.local

172.16.12.104

255.255.255.0

g

When you have updated the Excel file, save it in the CSV file format and close Excel.

h

Click the Configure tab.

i

Click the Edit Host Customizations button.

j

On the Select hosts page, click Next.

k

On the Customize hosts page, click the Browse button to find the customization CSV file where it was stored, and then click Finish.

5

Remediate the hosts in the management cluster.

a

On the Policies and Profiles page, click SFO01-Mgmt01, click the Monitor tab, and then click the Compliance tab.

b

Click SFO01-Mgmt01 in the Host/Cluster column and click Check Host Profile Compliance. This compliance test will show that the first host is Compliant, but the other hosts are Not Compliant.

c

Click on each of the non-compliant hosts, click Remediate Hosts Based on its Host Profile, and then click Finish on the wizard that appears.

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

6

Schedule nightly compliance checks.

a

On the Policies and Profiles page, click SFO01-Mgmt01, click the Monitor tab, and then click the Scheduled Tasks subtab.

b

Click Schedule a New Task then click Check Host Profile Compliance.

c

In the Check Host Profile Compliance (scheduled) window click Scheduling Options.

d

Enter SFO01-Mgmt01 Complance Check in the Task Name field.

e

Click the Change button on the Configured Scheduler line.

f

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.

g

Click OK in the Check Host Profile Compliance (scheduled) window.