VMware Horizon Community
DaveP87
Contributor
Contributor

Stuck @ Waiting for Agent

I've deployed a few new VDI's that have been sitting at Waiting for Agent.  Reboot did not resolve.  I followed the KB articles can confirmed I can telnet in both directions and DNS resolves correctly.  I've reinstalled tools and agent as well.  I'm pretty stumped as to where to go next.  Anywhere else to look?

Thanks

Reply
0 Kudos
7 Replies
mittim12
Immortal
Immortal

Did you reboot the desktop or the connection broker?    Awhile back I had the same scenario and I ended up rebooting my CB and the agents started reporting successfully.     It was a one off occurrence so I didn't bother troubleshooting it any further.   

Reply
0 Kudos
DaveP87
Contributor
Contributor

Just the desktop.  I'm trying to avoid restarting the broker, but it is somewhat comforting to hear it has a resolved a similar issue for others.  Thanks!

Anyone have any other thoughts that don't involve restarting the broker?

Reply
0 Kudos
Pooran98
Enthusiast
Enthusiast

Another thought is to make sure the agent on the VMs matches connection server version.

Reply
0 Kudos
DaveP87
Contributor
Contributor

They are the same version.

Reply
0 Kudos
mpryor
Commander
Commander

There are two high-level things that would block the VMs from becoming available:

1. Unable to reconfigure the VM in vCenter, this should be obvious as you'll see errors in the vSphere client

2. Unable to communicate with the broker from within the guest, this can be tested by running the support tool on the desktop VM: VMware KB: Collecting diagnostic information for VMware Horizon View 5.x

Reply
0 Kudos
DaveP87
Contributor
Contributor

Thanks for the Input.  I haven't seen any issues configuring and the only error I find with the support tool is that the Broker config fields in the registry are blank on the VDI in question, which is something I already knew.

At this point, I think I'm going to schedule a reboot and hope that gets things moving.

Thanks all!

Reply
0 Kudos
mpryor
Commander
Commander

"is that the Broker config fields in the registry are blank"

This suggests the configuration isn't being picked up from the VMX container which points towards the first issue, that configuration information is not being pushed to the VM - if you look in the .vmx file for the VM, does it contain configuration data in the machine.id field? Can you share the support bundle from a VM?

Reply
0 Kudos