Surface Pro X Citrix Receiver

Posted on  by admin

I have a user with a new Surface Pro. The latest version of Citrix Receiver is installed from the App store. He has Windows 8 and IE 11 installed. The user logs in to our Citrix portal with no issues; he sees the apps to which he has access. When he clicks on the icon to start the app, it tries to download launch.ica and will not start the app. Nov 03, 2015 It seems Citrix does support Surface Pro 4 webcam with the newest 4.6 release, but even with the fix listed on the documentation page, I'm still unable to redirect the webcam into the session. Last edited: Dec 6, 2016. Note that applications run differently on ARM-based Windows 10 PCs such as Surface Pro X. Limitations include the following: Drivers for hardware, games and apps will only work if they're designed for a Windows 10 ARM-based PC. For more info, check with the hardware manufacturer or the organization that developed the driver.

downloadWhy can't I download this file?Note:
You can hide all or part of the Advanced Preferences sheet available from the Citrix Workspace app icon in the notification area. For more information, see Hiding the Advanced Preferences sheet.
  1. Right-click Citrix Receiver for Windows from the notification area.
  2. Select Advanced Preferences and click DPI settings. The DPI settings dialog appears.
  3. Change the settings as required. By default, the option Let the operating system scale the resolution is selected.
  4. Click Save.
  5. Restart the Citrix Receiver for Windows session for the changes to take effect.
Receiver

Use cases

There are three possible settings for DPI Scaling in the receiver, Scaled, Unscaled and Operating system Scaling. The use cases for the different settings are as follows:
Use case: Operating System Scaling (also known as DPI scaling)
OS scaling is the default and is identical in behavior to previous receiver versions. This corresponds to the UI setting “Let the operating system scale the resolution”, or the High DPI policy set to disabled. This lets Windows handle all DPI scaling. The resolution on the VDA will be scaled and based on the DPI, resulting in a smaller resolution than the client device. This works well for single monitor sessions, and is efficient when connecting to XenApp 6.5 hosts, or supported XenApp/XenDesktop VDAs configured for Legacy Graphics.
This method does not support Mixed DPI; all monitors must have the same DPI or the session will not work. Scaling can cause blurriness in the images, particularly in the case of text. This setting is recommended for users on Windows 7 endpoints if DPI matching is not possible, or those connecting to Legacy VDAs. It can also be used on Windows 10 if there is no Mixed DPI.
Enhancements to the Operating System scaling since Receiver for Windows 4.10
Citrix Workspace app (CWA) for Windows version 1808
Surface Pro X Citrix ReceiverCWA for Windows version 1808 provides improvements in graphics quality for sessions using legacy graphics mode (GDI graphics mode), when DPI Scaling is enabled on the client.
Note: The Legacy graphics mode HDX policy can be used for any currently supported Server OS VDA version that supports Windows Server 2008 R2.
The feature enhancement leverages DirectX 11-based scaling on the client where CWA for Windows version 1808 is installed. Because of this, this feature enhancement is not available for Windows 7 client endpoints; as Windows 7 does not support DirectX 11.
Graphics quality improvements will also be seen in double-hop scenarios. Refer to the list below for use cases that support this feature enhancement:
Single-hop
Client endpoint OS: Supported versions of Windows 10 with CWA for Windows installed and DPI Scaling enabled.
VDA OS: Windows Server 2008 R2.
Double-hopPro
Client endpoint OS: Supported versions of Windows 10 with CWA for Windows installed and DPI Scaling enabled.
1st hop VDA OS: Citrix support versions of Windows 10 with CWA for Windows installed and DPI Scaling enabled.
2nd hop VDA OS: Windows Server 2008 R2.
Notes:
DPI scaling functionality is supported with HDX Windows media redirection, Flash redirection and Browser content redirection features with XenApp and XenDesktop 7.16 (and higher versions).
Use case: Scaled (also known as client scaling)
The Scaled setting will scale the resolution on the VDA similarly to OS Scaling, however this setting will support mixed DPI scenarios. This corresponds to the UI setting “Yes”, or the High DPI policy set to enabled and the option for “Scale the session for high resolution” set to “Yes”. This setting works well for mixed DPI scenarios when connecting to supported XenApp & XenDesktop and Citrix Virtual Apps & Desktops VDAs. This is the only way to scale Seamless sessions with mixed DPI.
Considerations when using Scaled configuration:
  • Scaling can cause blurriness in the images, particularly in the case of text.
  • There can be poor performance when connecting to Legacy VDAs (XenApp 6.5, or supported VDAs configured for Legacy Graphics).
  • Local App Access, RTOP, and other plugins that use the window positioning API do not work with Scaling.
  • Seamless apps will “jump” between monitors in this mode to maintain correct scaling, this is by design.

This setting is recommended for users on Windows 10 endpoints connecting to currently supported VDAs. It supports mixed DPI without any additional impact on server resources.
Use case: Unscaled (includes DPI matching feature)
This corresponds to the UI setting “No”, or the High DPI policy set to enabled and the option for “Scale the session for high resolution” set to “No”.

Citrix Receiver For Surface


This setting should not cause any blurriness due to scaling because the full-unscaled resolution of all monitors is sent to the session.
Enabling the unscaled setting will create sessions with higher resolution (as compared to scaled sessions), which can impact server performance and scalability, as well as increased bandwidth usage over the HDX connection. For this reason, customers will need to decide whether configuring for unscaled or scaled is more suited to their needs.
This setting is recommended for desktop sessions requiring the best image quality, where the additional server resource usage is acceptable.
Unscaled with DPI matching
The desktop session will launch with a DPI value that matches the DPI value of the endpoint monitor on which the session displays. This will result in text, icon and other object sizes in the desktop session matching that of the endpoint’s monitor.
ProIt is also possible for users to change the endpoint monitor’s DPI value mid-session, which will correspondingly change the desktop session’s DPI value to match. Doing so will also change the desktop session’s display resolution.
Requirements:
  • Endpoint: Windows 7 or Windows 10 with minimum Citrix Workspace app for Windows 1811 installed.
  • VDA: Windows 10 with minimum VDA version 1811 installed.

Limitations:
  • The DPI matching feature is only supported for desktop sessions; seamless sessions are not supported.

Download Citrix Receiver 4.8

Unscaled without DPI matching
When DPI matching is not possible, the unscaled setting will still mean the full resolution is sent but without DPI matching. This can result in small text and icons in apps and desktop sessions.
The DPI can still be set within the VDA after session launch, resulting in the desired text and icon sizes, though this is not possible on RDS desktops, or seamless applications.
Requirements:
  • Endpoint: Windows 7 or Windows 10 with minimum Receiver for Windows 4.10 installed (4.11 recommended to resolve some display issues).
  • VDA: Currently supported VDA versions on supported Windows Server OS and Desktop OS versions.

Limitations:
  • Even with one of the High DPI settings enabled, a slight blur has been observed in the desktop viewer UI.
  • In a session, when you change the DPI settings and relaunch it, the size of the session window might not be appropriate. As a workaround, resize the session window.

Additional Resources

A list containing the majority of Citrix Workspace app for Windows (formerly Receiver for Windows) support articles collated to make this page a one stop place for you to search for and find information regarding any issues you have with the product and its related dependencies.

Surface Pro X Review

The page is updated daily with new support articles and information. Articles will change from time and if information here is outdated or incorrect please let me know using the comments. Links may also expire or change so if you find broken links, please again let me know. For each issue, known product versions affected are recorded however that does not mean product versions that aren’t listed are not affected.

There is a search box that you can use if looking for a specific fault. For example if you have an error code or error message, use that to perform a search. You can also use your browsers search feature which will perform a search against the whole page based on the words you enter.

Receiver for Windows / Workspace app for Windows:


Surface Pro 7

wdt_IDBrief Description of IssueBrief Description of FixApplicable Product Versions Affected (if known)Link to supplemental Support Article(s)
1Resources with names ending with the published desktop name do not show up in Receiver.This is by design. Avoid using a suffix of the currently published desktop name.https://support.citrix.com/article/CTX227113
2When running Receiver with non-elevated permissions, you are unable to launch desktops or applications.Make sure you have full permissions to 'HKCUSOFTWARECitrix'. If the user account does not, delete the Citrix key and then restart Receiver. The key should be recreated with the appropriate permissions.https://support.citrix.com/article/CTX226530
3Upon launching a published desktop you receive error 'The specified module could not be found'.From a trace 'AxWfIcaLib.dll' was missing. .NET 4.6.2 was reinstalled and the user's profile was recreated.Citrix Receiver for Windows 4.8.https://support.citrix.com/article/CTX226437
4On first logon SelfService.exe crashes with message 'Self-Service Plug-in exited unexpectedly'. On second logon, it works.The desktop folder is missing from the default user's profile. Once added, Self Service works.https://support.citrix.com/article/CTX215296
5The authentication window shows periodically even when Receiver is not opened.Create registry strings to suppress Self Service refresh.https://support.citrix.com/article/CTX213755
6The Shift + F4 hotkey sequency may not function as expected after installing Receiver for Windows 4.7.Receiver for Windows 4.7 adds functionality for IME which is configured by default to use the Shift + F4 hotkey. You must change your custom hotkey to a different combination by editing the client machine registry.Citrix Receiver for Windows 4.7.https://support.citrix.com/article/CTX223049
7When using a Surface Pro and attempting to span a Remote PC session, the Surface Pro screen looks OK but the second monitor has issues such as the resolution being wrong and black bars appearing along the top and sides of screen.Receiver for Windows is not a DPI aware application so depends on the Windows OS to scale the application as appropriate to the client's DPI settings. Set DPI scaling to 100% on both monitors and on the Surface Pro.https://support.citrix.com/article/CTX216648
8Receiver might fail to perform the scan function with error message 'Your operation is cancelled'.Upgrade to Receiver for Windows 4.7.Citrix Receiver for Windows 4.5 and 4.6.https://support.citrix.com/article/CTX222885
9wfica32.exe crashes when launching certain resources.wfica32.exe crashes with a divide by-zero exception when the cursor position is set in the Desktop Viewer window. To overcome this, delete keys under HKCUSoftwareCitrixXenDesktopDesktopViewer.
10When users double-hop, wfica32.exe consumes a high amount of CPU.Create a SlowHPCPolling registry key with a value between 2-500ms. It is required that you test the value in your environment to determine which value works best. It is recommended to start with 16ms but if you notice performance issues then you can increase or decrease the value. By default Receiver for Windows polls certain libraries and drivers every 2ms, which will ultimately consume more CPU on the VDA.https://support.citrix.com/article/CTX206788