ESXi 5.0 Update 2 changes VMware Host ID in the 1000v
It looks like VMware ESXi 5.0 had an open issue with the way it was calculating the UUID that is sent to the VSM and displayed as the VMware host ID when a VEM module is connected. Buried in the resolved issues area of the Update 2 Release notes is : SMBIOS UUID reported by ESXi 5.0 hosts might be different from the actual SMBIOS UUID If the SMBIOS version of the ESXi 5.0 system is of version 2.6 or later, the SMBIOS UUID reported by the ESXi 5.0 host might be different from the actual SMBIOS UUID. The byte order of the first 3 fields of the UUID is not correct. This issue is resolved in this release. As you update ESXi hosts to update 2.0 they will come back with a different VEM number if the host has calculated the UUID in a new way. If you are running the advanced edition of the 1000v this will eat into your available licenses, and then your overdraft licenses. If you consume all of your overdraft licenses you will probably experience a service interruption on some of ...