Jump to content


Photo

XenDesktop 7.6 FP3 3 VDA - Keyboard Issue with Mac Receivers

Started by Sacha Thomet , 01 October 2015 - 04:34 AM
19 replies to this topic

Best Answer Sacha Thomet , 01 December 2015 - 02:23 PM

My Issue is solved by remove vda, delete all vda things out of C:\Program Files and C:\Program Files (x86), cleaning the regsitry and reinstall the VDA 7.6 FP3

Sacha Thomet CTP Member

Sacha Thomet
  • 212 posts

Posted 01 October 2015 - 04:34 AM

I've updated yesterday my Win7 XenDesktop's with the FP3 of the VDA. Now I have the Issue that I cannot use my keyboard from OSX Clients (Receiver 12). Does anyone have the same experience or can confirm that it's working fine with Win7, Mac and VDA 7.6 FP3.

 

With Win10 VDA 7.6 FP3 all is ok, also when I come from Windows Clients alls works fine. 



Dustin Norman Citrix Employees

Dustin Norman
  • 352 posts

Posted 01 October 2015 - 03:17 PM

Hi Sacha,

 

Does the keyboard not work at all or are there some specific keys that aren't working? What locale is your keyboard set to on the server? And on the Mac?

 

Thanks,

Dustin



Sacha Thomet CTP Member

Sacha Thomet
  • 212 posts

Posted 01 October 2015 - 03:35 PM

No it's not working at all - with old VDA no Issue. It's not with XenApp, It's on XenDesktop, Win7 - no Server. 



Ryan Chauvin Members

Ryan Chauvin
  • 3 posts

Posted 01 October 2015 - 04:07 PM

Sacha,

I installed FP3 VDA in my environment last night and I'm not seeing any keyboard issues on Mac. However, I'm using XenApp (Server 2008 R2 and Server 2012 R2)

 

Cheers,

Ryan



Dustin Norman Citrix Employees

Dustin Norman
  • 352 posts

Posted 01 October 2015 - 04:12 PM

Thanks. By server, I meant XenDesktop. What are the keyboard locales set to in the VDA and on the Mac? Also, what OS X version? Can you enable Full Session Logging in the Receiver Advanced preferences, repro the issue (connect and trying typing a bunch) and then post the logs here? The logs files will be in ~/Library/Logs/Citrix Receiver.

 

Thanks,

Dustin



Sacha Thomet CTP Member

Sacha Thomet
  • 212 posts

Posted 01 October 2015 - 05:03 PM

Thanks for your input Ryan. I tried with Yosemite, today upgraded to el capitan. All should be set to swiss german, but need to double-check. 

 

I will post the log after the next test, currently I have rolled back to Win7 with the 7.6 FP2. 



Ryan Chauvin Members

Ryan Chauvin
  • 3 posts

Posted 01 October 2015 - 05:54 PM

Sacha,

I installed FP3 VDA in my environment last night and I'm not seeing any keyboard issues on Mac. However, I'm using XenApp (Server 2008 R2 and Server 2012 R2)

 

Cheers,

Ryan



Sacha Thomet CTP Member

Sacha Thomet
  • 212 posts

Posted 02 October 2015 - 06:24 AM

Dustin I have now the Logfiles, I've testet with Mac System Language German and English - but Keyboard always Swiss German. The System Locale on German (Switzerland). Can I send you the Logfiles via email? 



Dustin Norman Citrix Employees

Dustin Norman
  • 352 posts

Posted 02 October 2015 - 12:12 PM

Sure. I'll PM you my email address.



Mark DePalma Members
  • #10

Mark DePalma
  • 26 posts

Posted 20 October 2015 - 02:16 AM

I've updated yesterday my Win7 XenDesktop's with the FP3 of the VDA. Now I have the Issue that I cannot use my keyboard from OSX Clients (Receiver 12). Does anyone have the same experience or can confirm that it's working fine with Win7, Mac and VDA 7.6 FP3.

 

With Win10 VDA 7.6 FP3 all is ok, also when I come from Windows Clients alls works fine. 

 

Did you figure this out? I just setup a Remote PC Access site with and I am having the same issue with VDA 7.6 FP3/Win7 and HTML5/Android/iOS Receiver. They connect fine, but cannot pass any keyboard input.



Sacha Thomet CTP Member
  • #11

Sacha Thomet
  • 212 posts

Posted 20 October 2015 - 05:49 PM

No unfortunately not. 



Konrad Ruess Members
  • #12

Konrad Ruess
  • 2,925 posts

Posted 05 November 2015 - 03:21 PM

Hi, got the same problems:

 

VDA 7.6.300 on Win7 Pro

Citrix Receiver 13.2.0hpa1 on HP ThinPro 5.2 Linux

 

--> keyboard not functioning at all

 

Accessing the same VDA from either Windows with Receiver 4.3.100 or Ubuntu 14.04 with Receiver 13.2.1 works.

 

Also, VDA 7.5 was working fine with the very same client setup.

 

BfN, Konrad



Sacha Thomet CTP Member
  • #13

Sacha Thomet
  • 212 posts

Posted 11 November 2015 - 06:02 AM

I just tested with newest Receiver for Mac OSX 12.1 and the Issue still exists. 



NB World Members
  • #14

NB World
  • 7 posts

Posted 17 November 2015 - 08:32 PM

Any update to this topic?



Sacha Thomet CTP Member
  • #15

Sacha Thomet
  • 212 posts

Posted 24 November 2015 - 07:01 PM

Unfortunately not :-(



NB World Members
  • #16

NB World
  • 7 posts

Posted 24 November 2015 - 10:19 PM

In my environment this is happening only on mackbooks not desktop macs. 



Sacha Thomet CTP Member
  • #17

Sacha Thomet
  • 212 posts

Posted 01 December 2015 - 09:45 AM

That's maybe the same: https://discussions.citrix.com/topic/372023-xendesktop-76-fp3-vda-keyboard-issues/ I'll try to uninstall the vda completly and install 7.6 fp3 again. 



Sacha Thomet CTP Member
  • #18

Sacha Thomet
  • 212 posts

Posted 01 December 2015 - 02:23 PM

My Issue is solved by remove vda, delete all vda things out of C:\Program Files and C:\Program Files (x86), cleaning the regsitry and reinstall the VDA 7.6 FP3


Best Answer

NB World Members
  • #19

NB World
  • 7 posts

Posted 02 December 2015 - 08:29 PM

That is no viable, when I have 1000+ pc's that have 5.6 already on it.  I need a solution I can automate.



Mark DePalma Members
  • #20

Mark DePalma
  • 26 posts

Posted 02 December 2015 - 08:36 PM

That is no viable, when I have 1000+ pc's that have 5.6 already on it.  I need a solution I can automate.

 

Performing a proper uninstallation of 5.6 should suffice as long as you haven't already tried to install 7.6 on top of 5.6. I created a script that searches for 5.6 installations using MSI/WMI COM and uninstalls the components. I added this to a larger deployment template that handles the reboots between tasks. I have been upgrading my endpoints that way.