VMware Horizon Community
ssjaronx4
Contributor
Contributor
Jump to solution

Problems with 4.6 agent and PCoIP

Hi Guys,

I am having issues connecting to my  VM internally and externally after updating the agent in the gold image.

I upgraded the servers to 4.6 a month ago and everything has been working fine. At the time I left the VM's as they were running on the 4.5 agent. I have had to do some updates to the gold image so I thought I would update the agent in the process. I removed tools, remove the agent, installed the 4.6 agent and the reinstalled the tools. I have snapshotted the VM and recomposed my test pool off of the image and now I cannot connect through PCoIP.

I can connect using RDP. The live pool running 4.5 connects internally \ externally using PCoIP. What happens when trying to connect using PCoIP is that it logs in, goes to connect and you get a black screen. A few seconds later the client dies. No errors anywhere as far as I can see.

I have opened the VM console in vShpere to the login screen and when I connect to the VM using View i can see that  client does login but then it just logs out again. Running Windows 7.

Any pointers you can provide would be appreciated.

Reply
0 Kudos
1 Solution

Accepted Solutions
eeg3
Commander
Commander
Jump to solution

We ran into this issue before. To resolve: Set the Composer Guest Agent service to disabled, reboot, uinstall the agent, reboot. It should be clear after this.

You can then install vmware tools then vmware agent fresh.

Blog: http://blog.eeg3.net

View solution in original post

Reply
0 Kudos
6 Replies
eeg3
Commander
Commander
Jump to solution

The View Agent should always be installed _after_ VMware Tools. That way it can change the system the way it wants without VMware Tools overwriting it. I'd recommend resetting up the image this way and seeing if it fixes PCoIP.

As far as setting up external PCoIP access with the new PCoIP Gateway, this is a good guide.

Blog: http://blog.eeg3.net
Reply
0 Kudos
mpryor
Commander
Commander
Jump to solution

eeg3 is correct, the current installer for tools will overwrite the display drivers with an older version which is not compatible with the pcoip server. There's a bug tracking the fix so that tools will only ever do an upgrade as the view agent does, but that obviously once fixed it doesn't cover existing tools installers bundled in ESX etc, so the best practice is to always install the view agent after installing/upgrading tools at this time.

Reply
0 Kudos
ssjaronx4
Contributor
Contributor
Jump to solution

Thanks for the information guys.  I figured that as the you have to uninstall the tools first before the agent that you would need to install them after the agent when reinstalling but was unsure which is why I specifically put my method in the original post. I'll give your suggestion a go now and see what happens.

Reply
0 Kudos
ssjaronx4
Contributor
Contributor
Jump to solution

Ok I cannot install the tools first it just wont work, the agent wont install because it cannot stop the VMWare Composer Guest agent service. For some strange reason even after the both the tools and agent are uninstalled this service sticks around and cannot be stopped? Also I noticed that if you install the agent without the tools then it doesnt try and stop the service?

I was thinking, if it is just a display driver issue cant I just install it the way I had it before and then just switch the drivers? I'm going to give that a go and see what happens.

Reply
0 Kudos
eeg3
Commander
Commander
Jump to solution

We ran into this issue before. To resolve: Set the Composer Guest Agent service to disabled, reboot, uinstall the agent, reboot. It should be clear after this.

You can then install vmware tools then vmware agent fresh.

Blog: http://blog.eeg3.net
Reply
0 Kudos
ssjaronx4
Contributor
Contributor
Jump to solution

Hi Guys,

Thanks for your help on this. Disabling the service and then doing the installation as suggested worked successfully.

Reply
0 Kudos