To configure DPI scaling using the Citrix Receiver Group Policy Object administrative template (administrators only) Open the Citrix Receiver Group Policy Object administrative template by running gpedit.msc. Under the Computer Configuration node, go to Administrative Templates Citrix Components Citrix Receiver DPI; Select High DPI policy. Dec 9, 2020 10:11:18 AM. Last Modified Date. Dec 9, 2020 10:11:18 AM. Article Number: 000051852. (RCViewer.exe) to control computer running a Citrix receiver, it. Jun 04, 2018 Beginning August 2018, Citrix Receiver will be replaced by Citrix Workspace app. While you can still download older versions of Citrix Receiver, new features and enhancements will be released for Citrix Workspace app. Citrix Workspace app is a new client from Citrix that works similar to Citrix Receiver and is fully backward-compatible with. The Citrix Workspace app allows for secure, unified access to all of your SaaS apps, web apps, virtual apps, files, and desktops. If your company uses Citrix, simply login with your company credentials to access all of the resources you need to be productive from anywhere. After a long trial and error, I managed to get Citrix Workspace App (formerly Receiver) working in Ubuntu and Other Linux. This guide explains 2 Ways to Install Citrix Receiver and Connect to Desktops from Ubuntu and Other Linux. Many organizations use commercial Citrix technology to provide their employees with remote connections via virtual machines.
Citrix Receiver For Macbook Pro 2020
- Open the Citrix Receiver Group Policy Object administrative template by running gpedit.msc.
- Under the Computer Configuration node, go to Administrative Templates > Citrix Components > Citrix Receiver > DPI
- Select High DPI policy.
- Change the settings as required.
- Click Apply and OK.
- From a command line, run the gpupdate /force command.
To configure DPI scaling using the graphical user interface:
| 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. |
- Right-click Citrix Receiver for Windows from the notification area.
- Select Advanced Preferences and click DPI settings. The DPI settings dialog appears.
- Change the settings as required. By default, the option Let the operating system scale the resolution is selected.
- Click Save.
- Restart the Citrix Receiver for Windows session for the changes to take effect.
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
CWA 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-hop
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”.
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.
It 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:
Citrix Receiver 2020
- The DPI matching feature is only supported for desktop sessions; seamless sessions are not supported.
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
There are three sections in this document:
Section 1: Key Citrix Receiver Updates settings for troubleshooting
Section 2: Citrix Receiver Updates Logging
Section 3: Troubleshooting Citrix Receiver Updates
Section 1: Key Citrix Receiver Updates settings for troubleshooting
You can configure Citrix Receiver Updates as follows:
- Right-click the Citrix Receiver for Windows icon in the notification area.
- Select Advanced Preferences, and click Auto Update. The Citrix Receiver Updates dialog appears.
By default, the Yes, notify me option is enabled.
If an administrator manages the user account or if an user is under a company policy, the Receiver Updates options might be set according to the administrator-specified settings.
This is the only setting for Citrix Receiver Updates that is available for an end-user modification.
Citrix Receiver Updates rollout period:
Citrix Receiver Updates rollout do not happen to all users on same day or at the same time. It depends on the delivery period and delay groups. Ideally delivery period is 30 days. So, users will get Receiver and related plug-ins updates any day between Day-01 and Day-30.
Based on the delay group settings, updates are available at the beginning, the middle, or the end of the delivery period.
The delay groups are categorized as follows:
- Fast – Update rollout happens at the beginning of delivery period.
- Medium – Update rollout happens at mid-delivery period.
- Slow – Update rollout happens at the end of delivery period.
Citrix Receiver Updates can be configured to deliver only updates marked for Long Term Support Releases (LTSR) or Current Releases (CR). The default is to accept CR updates.
These settings can be configured during Citrix Receiver for Windows installation, or using the Group Policy Object administrative template, or the StoreFront Account.
The registry location for each of these methods is:
- Install Time: HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixICA ClientAutoUpdateCommandline Policy
- GPO: HKEY_LOCAL_MACHINESOFTWARE[WOW6432Node]PoliciesCitrixICA ClientAutoUpdate
- StoreFront: HKEY_CURRENT_USERSOFTWARECitrixReceiverSRStore<some random number>Properties
The relevant registry values to examine are:
For Install Time and GPO configured settings
Value: Auto-Update-Check
possible data:
“Auto” (default) – perform auto updates,
“Manual” – updates are only fetched when the user makes a check request from the Receiver menu,
“Disabled” – no updates checks will be made.
Value : Auto-Update-LTSR-Only
possible data:
“True” – the updater will ignore any updates that are not marked as being LTSR valid,
“False” (default) - the updater will accept any updates.
Value : Auto-Update-Rollout-Priority
possible data:
'Fast” – updates will be accepted towards the beginning of the delivery period,
“Medium” – updates will be accepted towards the middle of the delivery period,
“Slow”– updates will be accepted towards the end of the delivery period.
For StoreFront Account configured settings
Value: Enable
possible data:
” True” (default) – perform auto updates,
“False” – updates are only fetched when the user makes a check request from the Receiver menu
Value : LTSROnly
possible data:
“True” – the updater will ignore any updates that are not marked as being LTSR valid
“False” (default) - the updater will accept any updates.
Value : BucketId
possible data:
'Fast” – updates will be accepted towards the beginning of the delivery period,
“Medium” – updates will be accepted towards the middle of the delivery period,
“Slow” – updates will be accepted towards the end of the delivery period.
Section 2: Citrix Receiver Updates Logging
Before you troubleshoot any issues with the Citrix Receiver Updates functionality, enable logging for Citrix Receiver Updates.
In Citrix Receiver for Windows Version 4.9, Citrix Receiver Updates logging is disabled by default.
In Citrix Receiver for Windows Version 4.8, Citrix Receiver Updates logging is enabled by default.
Citrix Receiver Updates logs can be found at /%temp%/<CitrixAutoUpdate _.log>
To enable Citrix Receiver Updates logging using the registry editor:
Launch the registry editor.
Navigate to HKEY_LOCAL_MACHINESOFTWARECITRIX.
Note: If you are an individual user, navigate to HKEY_CURRENT_USER SOFTWARECitrix.Add a new DWORD value.
On 32-bit systems:
HKEY_LOCAL_MACHINESOFTWARECitrix
Name: AutoUpdateTracingEnabled
Type: REG_DWORD
Data: 1
On 64-bit systems: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrix
Name: AutoUpdateTracingEnabled
Type: REG_DWORD
Data: 1Save and close the registry editor.
Restart the Citrix Receiver for Windows session for the changes to take effect.
Section 3: Troubleshooting Citrix Receiver Updates
Check for the requirements below as part of troubleshooting Citrix Receiver Updates.
- If you have configured an SSL intercepting outbound proxy, you must add an exception to the Receiver Citrix Receiver Updates Signature service (https://citrixupdates.cloud.com) and the download location (https://downloadplugins.citrix.com).
- If the Receiver for Windows session is running on a VDA, Citrix Receiver Updates is disabled.
- If the Receiver for Windows is running on an end-point where the Desktop Lock component is enabled, Citrix Receiver Updates is disabled.
- In Citrix Receiver for Windows Version 4.8, Citrix Receiver Updates was not functioning in a proxy setup. This issue has been addressed in Version 4.9.
- The Citrix Receiver Updates functionality is not available when a user with administrator-level privileges has installed Citrix Receiver for Windows, and an individual user(non-admin) is accessing Citrix Receiver for Windows.
Common issue #1: Software is up-to-date:
To check for updates manually, select the Check for Updates option from the Citrix Receiver for Windows icon in the notification area. When you check for updates manually and do not find any update available, it is due to one of the following reasons:
- No updates are available.
- Your account is set to a medium or slow category in the delay group. This indicates that the update rollout happens at the middle or at the end of the delivery period.
The following dialog appears when you check for updates manually and when no updates are available.
Solution:
You can check for updates at a later time or wait for the Citrix Receiver Updates notification.
Common issue #2: Issue when checking for update:
An update check can fail for various reasons. For example:
- No network connection during update check.
- Firewall settings don’t allow the connection to update server.
The following error message appears if there is an issue when checking for update.
Solution:
Ensure that your network connection is working properly. Alternatively, also verify that the firewall settings are not blocking the connection to Citrix update server.
Common issue #3: Issue when downloading the update
There is a network connection issue when checking for update or when you click the Download option.
The following error message appears if there is an issue when downloading the update.
Solution:
Ensure that your network connection is working properly.
Common issue #4: Error during installation:
During update installation, the following issues might occur:
- Not enough disk space
- During installation, if the operating system starts with any other installation, Citrix Receiver installation turns unresponsive and the update installation fails.
The following error message appears if the Receiver Update install occurs at the same time as another install on the system.
Additional Resources:
Resume auto-update for Citrix Receiver
Receiver for Mac Auto-Update Troubleshooting Guide
Citrix Receiver Auto-Update Frequently Asked Questions