VMware View Desktops not connecting
We're running a VMware View 5.2 environment. Hopefully we'll have it upgraded yet this year.
We have always had a small issue with problem desktops and mostly they take care of themselves. The usual message associated with them is an Agent Unreachable.
What we're starting to see is more desktops just showing an error and we drill down on the error it says: "No network communication between the View Agent and Connection Server. Please verify that the virtual desktop can ping the Connection Server via the FQDN."
If I go and look at the virtual desktop itself in the vSphere manager, it shows that it has a bogus 169.x.x.x IP and when I go to the console for that desktop, it shows the NIC as disconnected with a Windows message of cable unplugged. So the error message is correct that the agent can't talk to the connection server.
I have checked the NICs on the hosts and they are all fine. While I have a handful in this state, I also have several hundred that are working just fine. I've also checked the DHCP server the there are more than enough IP addresses to hand out and there are no errors on the server. Usually if I remove them and let them rebuild they rebuild OK... although that's not 100% true' occasionally they will come back from the rebuild in that state.
Anyone have a thought on what might be happening?
We have always had a small issue with problem desktops and mostly they take care of themselves. The usual message associated with them is an Agent Unreachable.
What we're starting to see is more desktops just showing an error and we drill down on the error it says: "No network communication between the View Agent and Connection Server. Please verify that the virtual desktop can ping the Connection Server via the FQDN."
If I go and look at the virtual desktop itself in the vSphere manager, it shows that it has a bogus 169.x.x.x IP and when I go to the console for that desktop, it shows the NIC as disconnected with a Windows message of cable unplugged. So the error message is correct that the agent can't talk to the connection server.
I have checked the NICs on the hosts and they are all fine. While I have a handful in this state, I also have several hundred that are working just fine. I've also checked the DHCP server the there are more than enough IP addresses to hand out and there are no errors on the server. Usually if I remove them and let them rebuild they rebuild OK... although that's not 100% true' occasionally they will come back from the rebuild in that state.
Anyone have a thought on what might be happening?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
but this is happening across at least three separate pools so I doubt that it's a pool issue
might not be the pool itself; could be the golden image it is using
ASKER
each pool has it's own master
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found solution myself, but gave some points because the solution given seemed like a very reasonable approach.
ASKER
I am looking at my desktops right now and, although I am running less now than in the heat of the day, I have none showing the error from lack of network connectivity.