ESXi 6 U2 HTML5 Client

Following an upgrade to ESXi 6 U2 I was interested in checking out the new HTML5 client. I entered the hostname in my browser and select the ‘Open the VMware Host Client’ link. 


On a couple of hosts I tested I was immediately presented by an error stating:

‘503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x1f0db660] _serverNamespace = /ui _isRedirect = false _port = 8308)’


This was resolved by the following steps (documented on VMware Communities and Tech Llama):

1. Log on to your ESXi host (either via SSH or DCUI/ESXi Shell)

2. Edit /etc/vmware/rhttpproxy/endpoints.conf

3. Remove the line:

/ui local 8308 redirect allow

4. Now restart the rhttpproxy:

/etc/init.d/rhttpproxy restart


Overall the client feels quite responsive and looks good. There are a few sections that stood out to me. The first is a Packages tab which lists the hosts installed VIBs and an option to install new VIBs. I can see this being very useful for checking the specific VIBs are installed and that the correct version is installed.



Also quite useful will be the PCI Devices information on the hardware tab which provides an easy way to get the Device ID information that can then be fed into the VMware Compatibility Guide.


Finally, there is a certificates section in which you can confirm the current certificate details and import a new certificate if needed. Appears to be simpler than connected via SSH and/or SCP to replace certs.



Creating a Custom ESXi Image

1. Download the required ESXi software depot

e.g. from

2. Download any additional software from VMware and/or vendors

e.g. from

3. Run PowerCLI

4. Add the ESXi software depot via ‘Add-EsxSoftwareDepot –DeportUrl [path to zip]’

5. Check the Image Profile name via ‘Get-ESXImageProfile | Select Name’

6. Clone the Image Profile to new via ‘New-EsxImageProfile –CloneProfile [Image Name] –Name “[New Image Name]”’

e.g. New-ESXiImageProfile –CloneProfile ESXi-5.5.0-20160204001-standard –Name “dmz”

7. Add additional software via ‘Add-ESXSoftwareDepot –DepotUrl [path to zip]’

e.g. Add-EsxSoftwareDepot -DepotUrl .\

8. Check the additional software names via ‘Get-EsxSoftwarePackage

9. Add the additional software to your Image Profile via ‘Add-EsxSoftwarePackage –ImageProfile [Your Image Name] –SoftwarePackage [Additional Software name]’

e.g. Add-EsxSoftwarePackage -ImageProfile dmz -SoftwarePackage cisco-vem-v173-esx

10. Export the Image Profile to VIB or ISO via ‘Export-EsxImageProfile [Your Image Name] –ExportTo[ISO/Bundle] -FilePath [Export Path]

e.g. Export-EsxImageProfile -ImageProfile dmz -ExportToBundle -Filepath D:\Deploy\Source\DMZ-Custom\


Note: I have encountered an error running this command stating ‘Export-EsxImageProfile : Can not instantiate ‘certified’ policy: VibSign module missing.’

To work around this issue I have added the ‘-NoSignatureCheck’ switch to the Export command.

This has apparently been fixed in

11. Deploy your image via VUM or direct attached ISO