Configuring Omnissa Horizon Client for End Users

Configuring Horizon Client for end users can involve setting options for client data sharing, the Media Optimization for Microsoft Teams feature, and the delay of audio playback.

Configure Login and Logout from Horizon Client for Chrome

When a user logs into the Horizon Client on a trusted environment, the user might not want to switch frequently between the Horizon Client and the browser or enter their username and password repeatedly. When a user logs in on a shared device, the user expects all login traces to be cleared when the user exits the Horizon Client.

In certain scenarios, a user might not prefer to cache any user information. In such cases, a user can select private mode so that the Horizon Client does not cache any user information. When the user exits the client, the client opens the browser and requests the user to log out from the corresponding identity provider (IDP). If a user does not select private mode, the client will cache the refresh_token and user information in the Horizon client.

On a shared device, the user can directly open native web browser, and authenticate to login to the device. The user information and the password will not be cached. However, few users might want to use private mode as the default login mode. In this mode, the user must enter the username and password in the IDP login page and the user is redirected to the logout page upon disconnection from the server.

To enable private mode on your device, login to your Chrome client, click the Settings tab and select the Take me to the IdP signout page when disconnect option. When Take me to the IdP signout page when disconnect option is enabled, you will be redirected to the Identity provider's page upon closing the Horizon client.

Configure Omnissa Horizon 8 Client Data Sharing With the CEIP

If an administrator has opted to participate in the Omnissa Customer Experience Improvement Program (CEIP), Omnissa collects and receives anonymous data from client systems through Omnissa Horizon Connection Server. You can configure whether to share this client data with Horizon Connection Server.

For information about configuring Horizon 8 to join the CEIP, see the Horizon 8 Administration document.

Client Data Collected for the CEIP

Description	Field name	Is This Field Made Anonymous?	Example Value
Company that produced the application	<client_vendor>	No	Omnissa
Product name	<client_product>	No	Horizon Client for Chrome
Client product version	<client_version>	No	2012-8.1.0-xxxxxxxx
Client binary architecture	<client_arch>	No	Browser
Native architecture of the browser	<browser_arch>	No	ChromeOS
Browser user agent string	<browser_user_agent>	No	Chrome/3.0.1750
Browser's internal version string	<browser_version>	No	3.0.1750 (for Chrome)
Browser's core implementation	<browser_core>	No	Chrome
Whether the browser is running on a handheld device	<browser_is_handheld>	No	true

Procedure

1. Click Settings (gear icon) on the Horizon web portal page.
2. Toggle the Allow data sharing option to on or off.

Configure Media Optimization for Microsoft Teams in Horizon Client for Chrome

This topic describes how to configure the Media Optimization for Microsoft Teams feature. This feature redirects media processing of audio calls, video calls, and desktop shares to be handled by the client machine instead of the agent machine.

For detailed information about the Media Optimization for Microsoft Teams feature, see the "Media Optimization for Microsoft Teams" section in the Horizon Remote Desktop Features and GPOs document.

The feature is enabled by default in Horizon Client for Chrome. However, if the client device is managed by an enterprise policy, the enterprise policy takes precedence over the Horizon Client setting. For example, if the Enable Media Optimization for Microsoft Teams option is enabled in Horizon Client but your enterprise policy does not allow media redirection to the client device, the Media Optimization for Microsoft Teams feature does not take effect.

Prerequisites

If the client device is managed by an enterprise policy, verify that the enterprise policy allows media redirection to the client device. To do this, look in the client JSON configuration file and verify that the enableMediaStream setting is set to true (the default value). For more information, see Client Features section.

Procedure

1. Click the Settings toolbar button in the upper-right corner of the desktop and application selector window.
2. To enable or turn off the Media Optimization for Microsoft Teams feature, turn on or turn off the Enable Media Optimization for Microsoft Teams option.
3. If you have enabled Media Optimization for Microsoft Teams, specify whether to allow screen-sharing capabilities in Microsoft Teams.
   • To allow screen-sharing capabilities, turn on the Enable screen sharing for Microsoft Teams virtualization option. Screen shares will be redirected to the client machine for media processing.
   • To block screen-sharing capabilities, turn off the Enable screen sharing for Microsoft Teams virtualization option. Screen-sharing controls will be unavailable in Microsoft Teams.

Configure Audio Play Delay Control

You might be able to improve the delay of audio playback from remote desktops by configuring the delay control option in Horizon Client.

Procedure

1. Connect to a server.

2. Click the Settings toolbar button in the upper-right corner of the desktop and application selector window and scroll down to the Delay Control setting.

3. From the Audio Play drop-down menu, select an audio play delay option.

   Auto	Audio play delay control is active only when a virtual microphone is used inside a remote desktop. This option is the default setting.
   Disable	No audio play delay control is implemented. Audio quality is best with a large delay when the network is unstable.
   Enabled	Enables audio play delay control. This setting introduces an audio quality decrease when the network is unstable. This setting might be useful when playing video. You might not want to enable this setting when playing music.

Configure Browser Redirection

With Browser Redirection, when an end user opens a website in a Chrome or Microsoft Edge (Chromium) browser in a remote desktop, the web page is rendered on the client system instead of the agent system, and it is displayed as an overlay on the remote browser's viewport. The viewport is the portion of the browser window that contains the content of the web page.

System Requirements for Browser Redirection

To support the Browser Redirection feature, the remote desktops on which you install the agent software must meet certain requirements.

Remote desktops

• Horizon Agent 7.10 or later must be installed on the virtual desktop or RDS host for published desktops. See the topics about installing Horizon Agent in the Desktops and Applications in Horizon 8 document.

• The Omnissa Browser Redirection agent-side group policy settings must be configured on the Active Directory server. See the topics about configuring Browser Redirection in the Horizon Remote Desktop Features and GPOs document.

• The Chrome browser or Microsoft Edge (Chromium) browser must be installed.

• The Horizon Browser Redirection extension must be installed in the browser. See the topics about configuring Browser Redirection in the Horizon Remote Desktop Features and GPOs document.

Display protocol for the remote session

• Omnissa Horizon Blast

Configuring Browser Redirection on the Client

You can configure Browser Redirection on the client system using the Settings window of Horizon Client.

Note: For enrolled Chrome devices, you can also use the Google Admin console to configure certain Browser Redirection settings. See Client Features section.

1. In Horizon Client, click the Settings toolbar button in the upper-right corner of the desktop and application selector window.

2. In the Settings window, configure the Browser Redirection settings.

   a. Ensure that you set the toggle for the Browser Redirection feature to the on position.

   By default, the Browser Redirection feature is turned on but you can turn it off if needed.

   b. Specify whether the remote browser can access the client system's camera and microphone.

   By default, access to the camera and microphone is turned off.

   Note: If you do not see the options to configure camera and microphone permissions, an administrator might have hidden these options on the enrolled Chrome device. For more information, see Client Features section.

   c. Specify whether to display a permissions message for camera and microphone access during client sessions.

   By default, the permissions message displays once per Horizon Client session, the first time that a page requiring audio or video input is redirected. In the message, users can choose from the following options.

   • To permit the remote browser to access the client system's camera and microphone for redirected pages, click Allow. This setting remains in effect for the current Horizon Client session and takes priority over the setting configured in step 2b.

   • To block the remote browser from accessing the client system's camera and microphone for redirected pages, click Deny. This setting remains in effect for the current Horizon Client session and takes priority over the setting configured in step 2b.

   • To stop displaying this permissions message, select Do not show this dialog again. The permissions setting specified by the user (Allow or Deny) remains in effect for the current session and all future Horizon Client sessions.

   Note: If an administrator has turned on the Geolocation Redirection feature, Horizon Client also displays a permissions message for geolocation when a redirected page attempts to access geolocation information.

Limitations of the Browser Redirection Feature

The Browser Redirection feature has the following limitations for Chrome clients.

• Multiple-monitor displays are not supported.
• Redirection from published applications is not supported.