keyboard input error in Citrix when using IOS Receiver with IPAD

-

Environment

Customer environment: Enterprise with multiple Servers on Windows 2016 and Citrix XenApp 7.13

Problem 

In a provisioned customer environment in France we had the Problem, that when a Desktop was open with Ipad over Citrix Receiver for IOS the user had the problem that the keyboard layout was wrong. So for example you typed AZERTY you always get QYERTW.
The user saw FRA in Systray and Word was also configured for french. None the less they get the problem.

Solution

After a few up and downgrades from Citrix Receiver and VDA versions, we set following registry key which solved our :


  1. To enable the feature, toggle on the feature by using registry editor regedit on the VDA.
  2. Under HKEY_LOCAL_MACHINE/SOFTWARE/Citrix, create the CtxKlMap key.
  3. Set the DWORD value of EnableKlMap = 1
  4. Reboot your VDA and test.

The problem occured because the service CtxKIMapHost.exe wasn't there.
As soon as you see the the service running in your session, you know the fix worked.
The error is fixed in VDA 7.16 and according to our supporttechnician also for 7.15. Why we get the error in 7.15 couldn't been resolved


Comments

Post a Comment

Popular posts from this blog

Export a list of all XenApp 7.x published applications via Powershell

-
Image
If you want to export a list of all published applications used in your environment you can do this with PowerShell. First add the Citrix PowerShell snapin: asnp Citrix.* Then run the Command which will export a TXT File which contains the Published Name and the Application Name. This can be extended to almost anything you need. More parameters you'll find in the Citrix Developer Documentation: https://developer-docs.citrix.com/projects/delivery-controller-sdk/en/7.17/Broker/Get-BrokerApplication/ MaxRecordCount 300 extends the output to 300 objects. The default value is 250. If you have more then 250 Applications you need this value.  Get-Brokerapplication -MaxRecordCount 300 | Select-Object PublishedName,ApplicationName | fl >c:\application.txt Then you'll find the TXT file in your specified output folder: It will be displayed like this:
Read more

Implementing Single Sign On with NetScaler and Kerberos Constrained Delegation (KCD)

-
Image
I wrote a manual how you can realize a Single Sign on Solution with Kerberos KCD and NetScaler. It's possible to restrict the user delegation to certain services/protocols on a server. You'll need this if NetScaler is not knowing the user password. If it knows the user password you can realize the SSO with Kerberos Impersonation. This will be an extra post. Let's start with creating a KCD account. 1. Create KCD Accounts Create KCD Account in AD Password never expires should be chosen 1.1    Enable the delegation tab for this user You can activate it with setspn ( It is available if you have the Active Directory Domain Services (AD DS) server role installed) Needs to be run from an elevated command prompt setspn -A host/KCDTest@simon.ns simon\KCDTest 1.2 Choose the delegation option Here you need to chose "Trust this user for delegation to specified services only" and also "use any authentication protocol".
Read more

How to: Create a Client Certificate for LDAPS with OpenSSL

-
Image
Today I will introduce you my new article on how to create a client certificate with OpenSSL so that you can use it for LDAPS You need to create two files in your new folder which we will need later on (I prefer notepad++ for the creation of my files): 1             1.  Your request.inf file 2             2.  Your v3ext.txt file 1.     Request.inf (save as .inf with notepad++) [Version]  Signature="$Windows NT$"  [NewRequest]  Subject = "CN= your-active-diretory.fqdn” f.ex : “simonAD.testinfo.com” (enter the FQDN of your AD Server)  KeySpec = 1  KeyLength = 2048 (enter the key length with fits your need. Some say you need to take at leas 2048 to make LDAPS work)  Exportable = TRUE  MachineKeySet = TRUE  SMIME = FALSE  PrivateKeyArchive = FALSE  UserProtected = FALSE  UseExistingKeySet = FALSE  ProviderName = "Microsoft RSA SChannel Cryptographic Provider"  ProviderType = 12  RequestType = PKCS10  KeyUsage = 0
Read more