I have had a ticket open with VMware since February regarding this issue. We have a newly created Windows 10 image for use with 2 automated pools (M10 and M60). On a daily basis, half of the m10 pools desktops will be in an agent unreacheable state. When this happens a user logging in will see a message "desktops are currently not responding". The desktops in question will have correct IP addresses, but are not pingable or self assigned IPs. The agent version is 7.0.3 on both pools. Turned off firwalls, issue persists.
Some additional details:
1. The issue only happens on these 2 pools and a set of 3 Grid servers with dedicated graphics (so when this issue happens we cannot see the desktops through vsphere). The issue is not with every desktop, we may have 4 available and then have 4 agent unreachable machines.
2. A little over a month ago we disabled apipa and the found that the machines that would get self assigned ips now get ip v6 addresses.
3. If we keep deleting machines, upwards of 10, we can get a set that are all available, but they will eventually come back as users log off.
4. Here is another new thing that has become noticeable within the past month. Sometimes machines will have correct ips (ones that are on the the correct vlan), but when pinging the machine name, I get a different IP. When I check dhcp, the machine will sometimes have the same ip showing in vsphere and other times the ip cannot be found anywhere in our split scope linked to that machine. Again, we have 4 other pools that are win 7 and on different servers that don't have any of these issues at all.
5. We created a new windows 10 pool and the issue occurs with that pool as well.
Our dhcp has plenty of ip addresses available. We have our DNS set to scavage every 8 hours (on one server in the scope). Any hints on any other places we can look? At this point, I'm willing to dismantle anything.