Skip to main content

24 de agosto de 2026

Using the Windows Registry to Configure Horizon Windows Client

You can define default settings for Omnissa Horizon Client in the Windows Registry instead of specifying these settings on the command line. Group policy settings take precedence over Windows Registry settings, and Windows Registry settings take precedence over the command line.

Note: In a future version of Horizon Client, Windows registry settings might not be supported and group policy settings must be used.

The following table lists the registry settings for logging in to Horizon Client. These settings are located under HKEY_CURRENT_USER\Software\Omnissa\Horizon\Client\ in the registry. This location is specific to a particular user. The HKEY_LOCAL_MACHINE settings, which are described in the next table, are computer-wide settings and pertain to all local users and all domain users that have permission to log in to the computer in a Windows domain environment.

Note: To modify the registry, you must have administrator privileges to write to this key, as it contains settings that apply to all users on the computer. Use the Registry Editor (regedit) to navigate to the desired location under HKLM and right-click to create a new key. See also: How to add, modify, or delete registry subkeys and values by using a .reg file

Horizon Client Registry Settings for Credentials
Registry SettingDescription
PasswordDefault password.
UserNameDefault user name.

The following table lists the registry settings for Horizon Client that do not include login credentials. The location of these settings is HKEY_LOCAL_MACHINE\Software\Omnissa\Horizon\Client.

If a setting is not found under this path, the fallback path is HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Omnissa\Horizon\Client.

Horizon Client Registry Settings
Registry SettingDescription
DomainNameDefault NETBIOS domain name. For example, you might use mycompany rather than mycompany.com.
EnableShadeDetermines whether the menu bar (shade) at the top of the Horizon Client window is enabled. The menu bar is enabled by default, except for clients in kiosk mode. A value of false disables the menu bar. Note: This setting is applicable only when you have the display layout set to All Monitors or Fullscreen.
ServerURLURL, IP address, or FQDN of the default Omnissa Horizon Connection Server instance.
EnableSoftKeypadIf set to true and a Horizon Client window has focus, the physical keyboard, onscreen keyboard, mouse, and handwriting pad events are sent to the remote desktop or published application, even if the mouse or onscreen keyboard is outside the Horizon Client window. The default is false.

The following table shows security settings that you can add. The location of these settings is HKEY_LOCAL_MACHINE\Software\Omnissa\Horizon\Client\Security.

Security Settings
Registry SettingDescription and Valid Values
CertCheckModeCertificate checking mode. Valid values are as follows:
  • 0 implements Do not verify server identity certificates.
  • 1 implements Warn before connecting to untrusted servers.
  • 2 implements Never connect to untrusted servers.
EnableTLSv11TLSv12 Specifies whether to enable TLS v1.1 and/or TLS v1.2. Valid values are as follows:
  • true enables either TLS v1.1 or TLS v1.2 or both, depending on the configuration of the SSLCipherList setting.
  • false turns off both TLS v1.1 and TLS v1.2.
Note: SSL v2.0, SSL v3.0, and TLS v1.0 are no longer approved security protocols and are not supported.
SSLCipherList

Configures the cipher list to restrict the use of certain cryptographic algorithms and protocols before establishing an encrypted TLS 1.1 or TLS 1.2 connection. The cipher list consists of one or more cipher strings separated by colons. The cipher string is case-sensitive.


When this setting is enabled, the default value is TLSv1.1:TLSv1.2:!aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES. The default value means that TLS v1.1 and TLS v1.2 are enabled. Cipher suites will use ECDHE, ECDH and RSA with 128 or 256 bit AES, with a preference for GCM mode. SSL v2.0, SSL v3.0 and TLS v1.0 are not supported.


Configure signature algorithms specifies the signature algorithms for TLS v1.2. Enter a colon separated list of signature algorithms in order of decreasing preference, in the form of algorithm+hash. Note that algorithm and hash names are case-sensitive. For example: RSA+SHA256:ECDSA+SHA256. If this option is not set, the default value is all signature algorithms supported by the OpenSSL library.


Configure supported groups sets the supported elliptic curve groups. Enter a list of curves separated by colons. Note that curve names are case-sensitive. For example: P-256:P-384. If this option is not set and ECDHE cipher suites are provided, the default value is all signature algorithms supported by the OpenSSL library.


For a reference link of the configuration, see Omnissa KB article 85640.

The following table shows Integrated Printing settings that you can configure. The location of these settings is HKEY_LOCAL_MACHINE\Software\Omnissa\Horizon\Client\PrintRedir.

Integrated Printing Settings
Registry SettingDescription and Valid Values
EnableActualSizePrintingDetermines whether to print files from a remote desktop by scaling and fitting the file contents to the printed page size or by printing the file contents at their actual size. Valid values are as follows:
  • true prints file contents at their actual size.
  • false scales and fits file contents to the printed page size.
The default value is true.

Esta página foi útil?

Enviar feedback sobre este tópico

Este tópico foi útil?

Não inclua informações pessoais ou confidenciais.

Gerando o link…