Re: PCoIP International Keyboard Layout Synchroniz...

dga5 · ‎08-01-2013

I'm working on a Institution with 21 different languages (21 different keyboard layouts...)

When PCoIP is used, I cannot synchronize keyboard layout on the Host (XP or Win7) with the client keyboard (zero client or VMware View client).

Example : when a belgian translator with a zero client configurated with a belgian keyboard connects a VMware View host, he must have, during the session, the belgian keyboard and not the default keyboard defined as default within the master image.

We've got no problem with RDP, only with PCoIP ( Turn on PCoIP user default language synchronization is enabled and Zero client is configured with the right keyboard).

Please, don't tell me that I have to create 21 different pools, 1 per keyboard layout...

Thanks for your help

Pat

buijspa · ‎08-23-2013

Hi,

We've got the same problem with HTML access

Nobody has the same problem ?

Pat

JPCARD · ‎11-20-2013

Hi,

We have the same issue...

One stupid question: did you turned on the policy "PCoIP user default input language synchronization" ?

Regards,

C.

buijspa · ‎11-20-2013

Hi JP,

Yes we did.

We've opened a ticket at VMware an Teradici supports concerning this problem but Teradici redirect this case to VMware.

We're waiting for a solution.

I soon as we'll get a solution//answer, I'll put it here.

Regards,

Pat

JPCARD · ‎11-20-2013

Many thanks Pat,

When did you opened a ticket?

I did exactly the same than you few months ago... I provided every logs they was asking for but unfortunately they were not able to find a solution and I was to busy at this time to follow the case with more insistance.

For your information, we have recently upgraded our VMware environnement... I've done some new tests with the agent 5.2 but the issue still remains.

We are using 2 differents models of Wyse: P20 & S10.

It don't work with the P20@PCoIP but it work very well with S10@RDP. S10 model is only RDP capable.

Cheers,

Christophe

buijspa · ‎11-20-2013

Hi Christophe,

We opened the ticket few weeks ago. I sent all the asked informations and I've been contacted by VMware support team.

We're waiting but I think I'll escalate to VMware benelux team.

We've also upgraded to 5.2 : same results.

We're using Wyse P20, P25 and Samsung NC220 but the problem is still there.

There's no problem with the VMware software client@PCoIP.

I'll keep you informed.

Cheers,

Pat

JPCARD · ‎11-21-2013

Hi Pat,

What's do you mean by "There's no problem with the VMware software client@PCoIP" ?

Using VMware View Client on a standard computer?

Regards,

Christophe

buijspa · ‎11-21-2013

Hi Christophe,

yes that's it.

VMware View Client for Win7 or WinXP on a standard computer.

I've just received news from VMware benelux team : they told me that VMware and Teradici find the root cause of the problem in the logs I sent.

Best regards,

Pat

JPCARD · ‎11-22-2013

Hello,

Ok good new !

I tested with VMview Client and same thing than you. It works as well.

Many thanks for keeping me updated !

Cheers,

Christophe

buijspa · ‎11-26-2013

Hi Christophe,

Bad news - here is the answer from VMware support :

"At the moment, keyboard sync over PCOIP from thin/zero clients is not currently supported."

They wrote a kb article http://kb.vmware.com/kb/2064865 (not available at the moment I'm writing this comment)

They suggest the following workarounds :

1. using a windows client

2. Dedicated pools or desktops with a matching default in the guest o/s for the client-side keyboard.

Both of these workarounds are useless for us (21 different keyboard layouts in our Institution) but maybe interesting for you...

Cheers,

Pat

JPCARD · ‎11-26-2013

Hi Pat.

Thanks for your feedback.

It is the same for us.

None of these workarounds are concevable for us...

I just hope that VMware are going to work on a solution now as they are aware of this issue.

If you can find something new, please let me know... I will do the same.

Many thanks.

Regards,

Christophe

PCoIP International Keyboard Layout Synchronization Failed