Installation guide

6962970 – Windows Client Device Uses Multiple CALs

Solution: Update to the latest version of PCSC-Lite on the client device.

3.1.8. 6962970 – Windows Client Device Uses Multiple CALs

Problem: A Windows client device is allocated multiple client access licences (CALs). A CAL is incorrectly

allocated each time a Windows application is started.

Cause: A known issue if the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing key or

any of its subkeys are missing from the Windows registry on a client device. This issue affects Microsoft

Windows 7 platforms.

Solution: Recreate the missing keys, by starting the Remote Desktop Connection with administrator

privileges. See Microsoft Knowledge Base article 187614 for more details.

3.1.9. 6970615 – SecurID Authentication Fails for X Applications

Problem: SecurID authentication for X applications fails when using the RSA Authentication Agent for

PAM. The issue is seen with X applications that are configured to use telnet as the Connection Method.

Cause: A known issue when using the RSA Authentication Agent for PAM.

Solution: Configure the X application object to use SSH as the Connection Method.

3.1.10. 7004887 – Print to File Fails for Windows Client Devices

Problem: When users select the Print to File menu option in a Windows application displayed through

SGD, the print job remains on hold in the print queue on the client device. The issue is seen on Windows

Vista and Windows 7 client devices.

Cause: A known issue with some versions of Windows.

Solution: A workaround for Windows Vista is described in Microsoft Knowledge Base article 2022748.

3.1.11. 12300549 – Home Directory Name is Unreadable For Some Client

Locales

Problem: When using client drive mapping in SGD, the name of the user's home directory may include

unreadable characters. By default, a user's home directory is mapped to a drive called "My Home".

The issue has been seen on non-Windows client devices configured with a non-English client locale, such

as ja_JP.UTF-8.

Cause: A known issue for some client locales.

Solution: No known solution at present.

3.1.12. 13068287 – 16-bit Color OpenGL Application Issues

Problem: OpenGL applications, such as three-dimensional graphics programs, do not start or do not

display correctly when published through SGD. The issue is seen when the X application object is

configured with a 16-bit Color Depth setting.

Cause: A known issue when displaying OpenGL applications using 16-bit color.

Solution: The workaround is to display the application using a 24-bit Color Depth setting.