Release Notes

Figure 1. Communication error
Version affected: 1.5 and later
Resolution/Workaround: Do the following steps to fix the issue:
1. Open RegEdit.
2. Navigate to the following location:
KHEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings.
Figure 2. Registry
3. Add a new DWORD value for ReceiveTimeout.
4. Set the value to 30 seconds (30000). Try with higher value based on your environment requirements.
5. Exit RegEdit.
6. Restart Internet Explorer.
NOTE:
Opening a new Internet Explorer window does not resolve this issue. You must restart the Internet Explorer browser.
● Issue 27: Using local host for host name causes issues in identifying the source of SNMP alerts.
Description: Starting with ESXi 5.1, a value of local host for the host name causes issues in identifying the source of SNMP
alerts. The use of local host is not supported and a Fully Qualified Domain Name (FQDN) must be used instead.
Version affected: 1.6 and later
Resolution/Workaround: When deploying an ESXi 5.1 server using DHCP, it is strongly recommended that a combination of
a DHCP reservation based on the selected NIC MAC addresses, and a DNS host entry using the reservation’s IP address
must be configured. You can view the MAC address in Deployment Wizard’s Server Identification page, Network Interface
drop-down, and provided to help identify the network interfaces. The DHCP reservation and DNS entry should be created
for the server prior to scheduling the deployment, and if properly configured, should set the hostname to the value from
DNS.
● Issue 28: Deployments failure error message displayed on R210 II machines.
Description: Timeout issue on R210 II systems produces a hypervisor deployments failure error due to failure of BIOS to boot
from attached ISO.
7