The DPI Synchronization feature ensures that the DPI setting in a remote desktop or published application matches the client system's DPI setting.

Like the Display Scaling feature, the DPI Synchronization feature can improve the readability of text and icons on high-DPI displays. Unlike the Display Scaling feature, which increases the size of fonts and images and can make them blurry, the DPI Synchronization feature increases the size of fonts and images, keeping them sharp. For this reason, the DPI Synchronization feature is generally preferred for an optimal user experience.

If DPI synchronization is disabled, display scaling is used. The Display Scaling feature scales the remote desktop or published application appropriately.

The DPI Synchronization agent group policy setting determines whether the DPI Synchronization feature is enabled. The feature is enabled by default.

Behavior of DPI Synchronization

The default DPI synchronization behavior depends on the Horizon Agent version that is installed in the agent machine.

Beginning with Horizon Agent 2012, the client's per-monitor DPI setting is synchronized to the agent and changes take effect immediately during a remote session by default. This feature is controlled by the DPI Synchronization Per Monitor agent group policy setting. The DPI Synchronization Per Monitor feature is supported by default for virtual desktops and physical desktops. It is not supported for published desktops.

With earlier Horizon Agent versions, the client supports synchronization only to the system DPI setting. DPI Synchronization happens during the initial connection, and Display Scaling works in case of reconnection, if necessary. When DPI Synchronization works and the client system's DPI setting matches the remote desktop's DPI setting, Display Scaling cannot take effect, even if you select the Allow Display Scaling option in the user interface. Windows does not allow users to change the system-level DPI setting for the current user session, and DPI synchronization occurs only when they log in and start a remote session. If users change the DPI setting during a remote session, they must log out and log in again to make the remote desktop's DPI setting match the client system's new DPI setting.

The agent DPI setting is located in the Windows registry at Computer\HKEY_CURRENT_USER\Control Panel\Desktop: logPixels.
Note: The system DPI setting might not be the same as the main monitor's DPI setting. For example, if you close the main monitor and the system switches to an external display that has a different DPI setting than the main monitor, the system DPI setting is still the same as the DPI setting of the previously closed main monitor.

This version of the client does not support the DPI Synchronization Per Connection agent group policy setting, which is provided with Horizon Agent versions 7.8 through 2006.

For more information about the DPI synchronization group policy settings, see the Configuring Remote Desktop Features in Horizon document for your Horizon Agent version.

Supported Guest Operating Systems for Virtual Desktops

For virtual desktops, the DPI Synchronization feature is supported on the following guest operating systems:
  • 32-bit or 64-bit Windows 7
  • 32-bit or 64-bit Windows 8.x
  • 32-bit or 64-bit Windows 10
  • 32-bit or 64-bit Windows 11
  • Windows Server 2008 R2 configured as a desktop
  • Windows Server 2012 R2 configured as a desktop
  • Windows Server 2016 configured as a desktop
  • Windows Server 2019 configured as a desktop
  • Windows Server 2022 configured as a desktop
Note: For Windows server machines that are configured as a desktop, the DPI Synchronization Per Monitor feature is not supported.

Supported RDS Hosts for Published Desktops and Published Applications

For published desktops and published applications, the DPI Synchronization feature is supported on the following RDS hosts:
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019
Note: For RDS hosts, the DPI Synchronization Per Monitor feature is not supported. This limitation does not apply to published applications that run on desktop pools with the VM Hosted Applications feature.