Hi everyone,
We've noticed some Win7 linked clones remain in the "Agent Unreachable" state for a while before getting refreshed. We think we narrowed it down to these clones ending up with a 169.254 (apipa) address instead of a DHCP address on our network. Our lease times are only an hour so I believe the clones in this state try to get a DHCP address 30 minutes later and it fixes itself. If we manually go into a clone exhibiting this behavior and try and get a valid DHCP address using ipconfig it gets one and the system gets refreshed.
Here are some things we've researched already.
1. The systems only have one virtual NIC and it is a VMXNET3 NIC
2. Within "Edit Settings" for a VM it is showing the NIC as "Connected" and is set to "Connect at Power on"
3. The VMware View agent service is running within the VM
4. The VM is listed as running the latest, current, VMware Tools inside of vCenter
5. This has happened on different ESXi hosts so it doesn't seem limited to one host.
6. We checked the DHCP scope on the DHCP server, of the 900+ addresses only 8% are being used so there are plenty of addresses available
7. As mentioned earlier, if you go into the VM's console and do an ipconfig /release then /renew it gets a valid address and completes the refresh process
8. Within the virtual network switch the number of ports (120 per switch) is well above the number of VM's on the switch (at the most about 15 VMs).
9. We checked the DHCP server logs and it doesn't look like the VM's are making a request for a new address on it's own (at least not during the logoff time frame).
The View environment is version 6.1.1 build 2769403
Any suggestions would be greatly appreciated :-)