View can not connect to agent with PCoIP

[kmk12]

We can connect to VM's with RDP, but PCoIP does not work. The client starts to connect to the agent, the screen left black and then the client exits

The firewall should not be the issue, client and agent can communicate due to the logs and wireshark.

Any idea is welcome here.

Our setup:

ESX 4.1

VCENTER 4.1

VManager 4.0.1 (up to date)

VIEW 4.0.1 (up to date)

[mittim12]

Is this through a security server? PCOIP does not work when trying to tunnel through a security server. If it isn't through a security server can you provide the OS of the VDI machine.

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

[kmk12]

No security server.

Which is the VDI machine?

ESX 4.1 (Linux / Standard installation) x64

VCENTER 4.1 ( Windows 2008 R2) x64

VManager 4.0.1 (Windows 2003) x32

VIEW 4.0.1 (WIndows XP Prof.) -> Agent (Windows XP Prof.) x32 both

All actual patched

Michael

[mittim12]

Have a look at this KB article. Are you running any type of legal caption at logon?

http://kb.vmware.com/kb/1018158

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

[EGarbuzov]

Do you increase video RAM in your VMs?

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1024611&sl...

[kmk12]

Yes, the caption is the name of the running VM

Yes, i had about 19 MB first. I increased to 50 MB after iread the post, but it does not resolve the problem. It starts, but the screen left black and then view exits.

[mittim12]

Sorry, I linked the wrong KB in my reply. This is the one I meant to add, http://kb.vmware.com/kb/1016753. There is a known issue with captions and a work around is found in option 5 of the link.

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

[kmk12]

I removed the keys from the registry, but the problem stays the same.

I played around with different video ram settings, but in vain.

The windows display setting at the vm shows two monitors, one active, the other inactive. Something to do with it?

[eeg3]

Have you tried logging in via PCoIP then opening up the VM through the vSphere Client and see if anything weird looks like it is occurring, like it still getting stuck at the Caption? Perhaps it didn't actually go away.

[kmk12]

Yes, sorry that i didnt mention it earlier.

At the vcenter vm console everything looks fine and after the view client exits the desktop at the console remains open.

[crmstevew]

I am seeing the same issue. When the view client is connected to a PCoIP Pool, the client window opens with a black screen for about 20 seconds and then the client window goes away. Checking the status inside View Manager shows a disconnected session. Opening the Desktop-VM's console from vSphere shows a locked session of the user's account.

I did some testing once the PCoIP disconnected session was there. I changed the pool protocol in View Manager to RDP. once changed, the View client is able to connect and render the desktop. If I disconnect the RDP session (still logged into the Desktop-VM), change the protocol back to PCoIP, I get the black screen followed by the client window closing. This scenario is very consistent.

The only thing in the desktop-VM's event logs that looks interesting is that the client name is null under PCoIP and the client hostname is listed under RDP. But the "CONNECTED" and "DISCONNECTED" events are present for PCoIP, so the Desktop-VM just thinks this is a normal disconnect from the client.

My Environment:

vSphere 4.0 U1

VMware View 4

Desktop-VM's - Windows XP Pro

Connection Broker VM's - Windows Server 2003

Client - Windows Vista laptop; Windows Server 2003 VM on the same ESXi Host

Network/Host environment - Everything pushed to a single ESXi host to make sure there are not network/firewall issues

Thanks.

[DDunaway · Accepted solution]

I believe this may be your issue.

when updating ESX to 4.0 update2 my PCoIP broke.

there is a patched 4.0.1 agent that must be installed on the VMs.

VMware KB 1022830 KB1022830

[crmstevew]

Replacing the View Agent with the patched one mentioned resolved my issue. Now, for the orignal poster. Did this resolve your issue??

THANKS DDunaway!

[mittim12]

The patch was designed for the 4.0 update 2 tools issue and he is running 4.1 so it may not help him. Certainly worth a try though.

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

[CareFusionServe]

Known bug/problem

vmware-view-4.0.1-269620 agent, client, and connection server - build dated Aug 6 - helps (but didn't fully resolve)

We still have documented problems (open VMware case) with the new builds when switching between protocols. though in our latest iteration, the result was a lack of the GINA/logon screen for about 2 minutes, then works okay (ie - finally can log back in to VM).

Work-around - if you log in with RDP, reboot the VM, then you can connect via PCoIP fine (so basically an agent issue, there are other 4.0.x agent issues as well)

[kmk12]

We updated to 4.5 and the problem disapears.

At the agent logfile:

09/10/2010, 14:55:28.553> LVL:1 RC: 0 MGMT_SYS :SESSION_ACTIVE: UNRECOGNIZED EVENT: 0x100 (MGMT_SESS)!

That seems to be the problem. I guess, that an update to 4.0.1-269620 would also resolve the issue but Composer 2.0 does not work with Windows 2008 R2 so the update came very handy to resolve two issues at once.

Thank you for being so helpful!

[CareFusionServe]

We have an open case with vmware and are at 269620 and its not resolved. An upgrade to 4.5 which was just released days ago will not be an option for a lot of environments, but ours is very small so we will research the process. Any info on your upgrade would be really helpful.

[kmk12]

We will have a very small rollout also. Just 20 VM.

Almost one and a half wekk ago I installed:

ESX 4.1

vSphere IM 4.1

viclient-all 4.1.0 258902 (not important because we still had problems with our 10zig thin clients (wince and linux))

viewagent 4.0.1 233023

view connectionserver 4.0.1 233023

That setup did not work with PCoIP, ViewComposer was also an issue.

Today i upgraded:

ViewComposer 2.5 - 291081

ViewConnectionserver 4.5.0 - 293049

Viewclientwithlocalemode 4.5.0 - 293049

ViewAgent-4.5.0 293049

ViewClient-4.5.0 293049 (not important, because it works with the thin clients from 10zig)

And tada .. no more problems with PCoIP, but hassle with the DBServer Setup of View Manager 4.5. You are forced to use a db now for the event log.Not pretty to be forced.

I hope i could help and you can resolve your issues soon.

Michael

[nnmansoori]

hi

I applied the path and it worked for Windows XP, but not for Windows 7 till I upgraded view agent to view 4.5 and PCoIP worked for Windows 7 too.

[steverding]

It looks like there is a simular problem in view4.5 also. I had the problem with our view 4.1 environment and could fix it with the fix from KB 1022830.

Today i updated to view4.5 and the black screen-disconnect bug is there again. I can connect with RDP, but no cigar with PCoIP.