Using a Remote Desktop or Published Application

Horizon Client provides a familiar, personalized desktop and application environment.

Feature Support for Chrome Clients

Certain guest operating systems and remote desktop features require specific Horizon Agent versions. Use this information when planning which features to make available to your end users.

Supported Windows Virtual Desktops

Windows virtual desktops are single-session virtual machines.

This version of client software works with Windows virtual desktops that have Horizon Agent 8 version 2006 or later installed. Supported guest operating systems include Windows 7, Windows 8.x, and Windows 10, Windows Server 2008 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022 with the following limitations:

Windows 7, Windows 8.x, and Windows Server 2008 R2 virtual desktops are not supported with Horizon Agent 2006 and later.

Supported Published Desktops on RDS Hosts

RDS hosts are server computers that have Windows Remote Desktop Services and Horizon Agent installed. Multiple users can have published desktop sessions on an RDS host simultaneously. An RDS host can be either a physical machine or a virtual machine.

This version of client software works with RDS hosts that have Horizon Agent 8 version 2006 or later installed. Supported guest operating systems include Windows Server 2008 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022, with the following limitations:

Windows Server 2008 R2 RDS hosts are not supported with Horizon Agent 2006 and later.

Supported Linux Desktops

For a list of supported Linux guest operating systems and information about supported features, see the Desktops and Applications in Horizon 8 document.

Internationalization

The Horizon Client user interface and documentation are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish. You can also input characters for these languages.

Touchpad, Touchscreen, Keypad, and Mouse Gestures

Omnissa created user interaction aids to help you navigate conventional user interface elements in a remote desktop on a non-Windows device.

Note: If the client device has a touch screen, you can use different gestures depending on whether the Advanced Touch feature is activated for the client. For more information, see Client Features section.

Keyboards and Keypads

You can use the device's physical keyboard to enter input in a remote desktop or application.

If the device has a touch screen, you can use the following gestures to display the on-screen keyboard:

If Advanced Touch is activated, tap with three fingers at the same time.
If Advanced Touch is not activated, hold down three fingers at the same time.

Horizon Client also supports input from an external numeric keypad in a remote desktop. To enable the use of a numeric keypad, perform the following steps.

Note: Horizon Client supports the use of a numeric keypad in remote desktops only. Numeric keypads are not supported for remote applications.

Log out and disconnect from the remote desktop.
Click the Settings toolbar button in the upper-right corner of the desktop and application selector window.
Turn on the Use Numeric Keypad for Desktop option.
Connect to the remote desktop.
Point to the top of the remote desktop window until the menu bar appears and click to highlight and enable the Numeric Keypad button.

Clicking

As in other apps, you can tap your touchpad to click a user interface element. If the device has a touchscreen, you can touch to click a user interface element. You can also use the buttons on an external mouse, including the forward and back buttons.

Dragging

As in other apps, you can hold down the button on the touchpad or an external mouse to drag a user interface element.

If the device has a touch screen, you can use the following gestures:

If Advanced Touch is activated, hold one finger down on the user interface element and slide the finger to drag.
If Advanced Touch is not activated, hold one finger down for a long touch on the user interface element and then slide the finger to drag.

Right-clicking

The following options are available for right-clicking:

Tap with two fingers on the touchpad.
Hold down the Alt key on the keyboard and tap the touchpad with a single finger.
Use an external mouse to right-click.
If the device has a touch screen, you can use the following gestures:
- If Advanced Touch is activated, hold one finger down for a long touch and then release. Or, tap with two fingers at the same time.
- If Advanced Touch is not activated, tap with two fingers at the same time.

Scrolling and Scrollbars

The following options are available for vertical and horizontal scrolling.

Tap and hold with your thumb and then scroll down with one finger on the touchpad. You can also scroll with two fingers.
Use an external mouse to scroll.
If the device has a touch screen, you can use the following gestures:
- If Advanced Touch is activated, slide with two fingers to scroll. The content under your fingers moves in the same direction as your fingers.
- If Advanced Touch is not activated, hold down two fingers for a long touch and then slide to scroll. The content under your fingers moves in the same direction as your fingers.

Zooming In and Out

If the device has a touch screen, you can use the following gestures:

If Advanced Touch is activated, place two fingers on the screen, and pinch your fingers apart to zoom out and pinch your fingers together to zoom in
If Advanced Touch is not activated, there is no support for zooming in and out with the touch screen

Window Resizing

To use the touchpad to resize a window, touch and hold one finger at the corner or side of the window and drag to resize.

If the device has an external mouse, place your pointer on the edge of the window and drag the border of the window to make it wider or narrower.

If the device has a touch screen, place one finger at the corner or side of the window and drag to resize.

Sound, Music, and Video

If you have turned on the sound for your device, you can play audio in a remote desktop.

Adjusting the Sound in Remote Desktops and Published Applications

By default, sound playback is enabled for remote desktops and published applications. An administrator can set a policy to turn off sound playback. Some limitations apply to sound playback in remote desktops and published applications.

To turn up the volume, use the sound control on the client system, not the sound control in the remote desktop.
Occasionally, the sound might go out of sync with the video.
In conditions of heavy network traffic, or if the browser is performing many tasks, sound quality might be reduced.

Using Remote Desktops

You can use the top menu bar in a remote desktop window to perform common tasks in a remote desktop.

To open the top menu bar in a remote desktop, move your mouse to the top of the remote desktop window until the top menu bar appears.
To use the Ctrl+Alt+Delete keyboard shortcut inside a remote desktop, click the Send Ctrl+Alt+Delete to the to current work area button in the top menu bar.
To enter full-screen mode, click the Fullscreen button in the top menu bar. To exit full-screen mode, click the Quit fullscreen button in the top menu bar.
To redirect USB devices to the remote desktop, click the USB Device Redirection button in the top menu bar.
To exit multi-monitor mode, click the Quit multimon button in the top menu bar.
To disconnect from a remote desktop, click the Disconnect button in the top menu bar, or click the X (Close) button in the upper-right corner of the remote desktop window.
To view information about Horizon Client, click the About button in the top menu bar.

To switch to another open remote desktop, click that remote desktop window. You can also browse through all the open remote desktops (including local and published applications) on the client device by pressing Alt+Tab. To focus on a selected remote desktop, release the Alt key.

For information about logging off from a remote desktop, see Log Out or Disconnect section. For information about restarting a remote desktop, see How Do I Restart a Remote Desktop in the Horizon Client section. For information about resetting a remote desktop, see Reset Remote Desktops or Published Applicationssection.

Using Published Applications

Horizon Client provides navigation aids to help you use published applications.

To maximize and minimize a published application, click the Maximize and Minimize buttons in the same way that you do in any application.
To restore a minimized published application, click its shelf icon on the client device or select the published application session and click the Restore button in the Session Management Center window. In Kiosk mode, you must use the Session Management Center to restore a minimized published application. For more information, see Using Published Applications in Kiosk Mode section.
To reset a published application, see Reset Remote Desktops or Published Applications section.

To switch to another open published application, click the published application window. You can also browse through all open published applications (including local applications and remote desktops) on the client device by pressing Alt+Tab. To focus on a selected published application, release the Alt key.

Copying and Pasting Text and Images

By default, you can copy and paste plain text and HTML-format rich text from the client device to a remote desktop or published application.

You can also copy and paste plain text and HTML-format rich text from a remote desktop or published application to the client device if an administrator activates this feature.

An administrator can configure the copy and paste feature so that copy and paste operations are allowed only from the client device to a remote desktop or published application, or only from a remote desktop or published application to the client device, or both, or neither.

When you copy and paste images and rich text, the following restrictions apply.

If the clipboard source is a Google app, such as Google Docs, you can copy and paste images only when the client device can access the Google website.
If you copy an image and rich text (or plain text) together from the client device, and the destination is an application that supports only rich text, such as WordPad, the image is discarded and only the text is copied and pasted. If the destination application supports HTML/XML-format rich text, such as Microsoft Word, this restriction does not apply.
An administrator can use group policies to restrict clipboard formats during copy and paste operations. The clipboard format filter policies for Microsoft Office Chart and Smart Art data and Microsoft Text Effects data are not supported. For information about clipboard format filter policies, see the Horizon Remote Desktop Features and GPOs document.

The clipboard can accommodate a maximum of 1 MB of data for all types of copy and paste operations. If the plain text and rich text data together use less than maximum clipboard size, the formatted text is pasted. Often the rich text cannot be truncated, so that if the text and formatting use more than the maximum clipboard size amount, the rich text is discarded, and plain text is pasted. If you are unable to paste all the formatted text you selected in one operation, you might need to copy and paste smaller amounts in each operation.

Logging Copy and Paste Activity

When an administrator activates the clipboard audit feature, Horizon Agent records information about copy and paste activity in an event log in the agent machine. The clipboard audit feature is deactivated by default.

To activate the clipboard audit feature, you must configure the Configure clipboard audit group policy setting.

You can optionally configure the Whether block clipboard redirection to client side when client doesn't support audit group policy setting to specify whether to block clipboard redirection to clients that do not support the clipboard audit feature.

For more information about the group policy settings for clipboard redirection, see the Horizon Remote Desktop Features and GPOs document.

The event log where information about copy and paste activity is recorded is named Horizon RX Audit. To view the event log in the agent machine, use the Windows event viewer. To view the event log from a centralized location, configure VMware Log Insight or Windows Event Collector. For information about Log Insight, see the VMware by Broadcom documentation. For information about Windows Event Collector, see the Microsoft documentation.

Transferring Files Between the Client and a Remote Desktop or Published Application

You can transfer files from the client device to a remote desktop or published application. You might also be able to transfer files from a remote desktop or published application to the client system.

To upload a file, drag the file from the client system to the remote desktop or published application window. When the upload is finished, the file appears in the C:\Users\username\Documents folder.

To download a file, select the file in the remote desktop or published application by pressing Ctrl+C. After you confirm the file transfer, the file appears in the Downloads directory on the client device.

An administrator can configure the ability to allow, disallow, or allow in one direction only, the transfer of files by modifying the Configure file transfer group policy setting for Blast. The default is to only transfer files from the client system to a remote desktop or published application.

The Configure file transfer group policy setting has the following values.

If the Disabled both upload and download value is selected, you cannot transfer files in either direction.
If the Enabled file upload only value is selected (the default setting), you can only transfer files from the client system to a remote desktop or published application.
If the Enabled file download only value is selected, you can only transfer files from a remote desktop or published application to the client system.

If the Configure clipboard redirection group policy setting is turned off from the server to the client, file download is also deactivated.

For more information about these group policy settings, see the Horizon Remote Desktop Features and GPOs document.

This feature has the following limitations.

You can download files up to 500 MB and upload files up to 2 GB.
You cannot download or upload folders or files that have a size of zero.
If a file transfer is in progress in a remote session and you open a connection to a second remote session, and if a security warning appears, if you ignore the warning and continue to connect to the second remote session, the file transfer in the first session stops.

Set File Association

You can associate Chrome Native Client apps with file types.

To display available apps in the Horizon Chrome Client:

Launch the broker to get information on available apps.
Right-click a local file and select Horizon Client for Chrome.

All available apps are displayed.

To set an app as the default app, click the circle next to it. The circle turns blue. The next time you open this file type, the select app menu is skipped and the file is opened with the selected app.

To change or deactivate the default app, navigate to the server list page and click Change next to Change default app to open local file. Then select the appropriate option.

To hide apps in the File Association menu, turn off this feature on the Settings page.

With the client drive redirection feature, you can share folders or drives on the local client system with remote desktops and published applications.

Shared drives can include mapped drives and USB storage devices.

The client drive redirection feature has the following limitations.

The feature cannot be configured using the Windows registry key settings ForcedByAdmin, default shares, and permissions.
The TCP and UDP side channels are not supported. If the agent machine is configured to use either of these side channels, you cannot use the client drive redirection feature.
Dynamic Environment Manager policies are not supported.
Network recovery is not supported. You cannot use client drive redirection after network reconnection unless you disconnect the session and connect again.
You can use the client drive redirection feature with only one remote session at a time. Multiple remote sessions are not supported.
You cannot change properties for shared folders or files in the remote desktop.

Prerequisites

To share folders and drives with a remote desktop or published application, an administrator must enable the client drive redirection feature. This task involves installing Horizon Agent and enabling the agent Client Drive Redirection option. It can also include setting policies to control the client drive redirection behavior. For more information, see the Horizon Remote Desktop Features and GPOs document.

Procedure

Click the Settings toolbar button in the upper-right corner of the desktop and application selector window and turn on the Enable Folder Sharing option in the Settings window.
To select a specific folder or drive to share, click Select, click Add, browse to and select the folder or drive, and click OK.

You can add multiple folders and drives, but you can select only one item at a time. You can remove a folder or drive by clicking the X next to its name in the Folder Sharing dialog box.
To save the settings, click OK.

The folder sharing settings apply to all remote desktops and published applications.

Results

In a remote desktop, a network location appears for each folder and drive that you shared. For example, if you shared a folder named test1, the test1(Z:) network location might appear in the remote desktop. A device also appears for each shared folder and drive. The device name format is folder on Horizon, for example, test1 on Horizon.

In a published application, you can select File > Open or File > Save As, if applicable, and navigate to the shared folder or drive.

Use Multiple Sessions of a Published Application From Different Client Devices

When an administrator has activated multi-session mode for a published application, you can use multiple sessions of the same published application when you log in to the server from different client devices.

For example, if you open a published application in multi-session mode on client A, and then open the same published application on client B, the published application remains open on client A and a new session of the published application opens on client B. By comparison, when multi-session mode is deactivated (single-session mode), the published application session on client A disconnects and reconnects on client B.

The multi-session mode feature has the following limitations.

Multi-session mode does not work for applications that do not support multiple instances.
If the application session is disconnected while you are using a published application in multi-session mode, you are logged off automatically and any unsaved data is lost.

Prerequisites

An administrator must activate multi-session mode for the application pool. End users cannot modify the multi-session mode for a published application unless an administrator allows it. See Desktops and Applications in Horizon 8.

Procedure

Connect to a server.
Click the Settings toolbar button in the upper-right corner of the desktop and application selector window, scroll down to the Multi-Launch setting, and click Set.
Select the published applications that you want to use in multi-session mode and click OK.

If an administrator has enforced multi-session mode for a published application, you cannot change this setting.

Using Published Applications in Kiosk Mode

When you are using published applications in Kiosk mode, you must use the Session Management Center to perform certain tasks.

To open the Session Management Center window, click the Settings toolbar button in the upper-right corner of the desktop and application selector window and click Open next to Session Management Center. If you have a remote desktop session open, you must close the remote desktop session before you can access the desktop and application selector window.
To restore a minimized published application in Kiosk mode, select the published application session and click the Restore button in the Session Management Center window.
To switch published applications in Kiosk mode, select the published application session and click the Restore button in the Session Management Center window.
To close the Session Management Center window in Kiosk mode, click the close (X) button in the upper-right corner of the Session Management Center window.

How to Automatically Launch a Kiosk Application on a Chrome OS Device

Users operating in Kiosk mode might have pre-configured the Chrome client as an auto-launch app with default servers and applicationId or desktopId. Such users are immediately transitioned into their selected desktop or application without interfacing with the server or desktops and applications list page. The following section describe how to automatically launch a Kiosk app on a Chrome client device.

Prerequisites

Ensure you have access to a managed Chrome OS device where the administrative controls, policies, and configurations can be centrally managed. Unmanaged Chrome OS devices or those without the proper administrative access might not support or correctly implement these policies.

Note: Ensure that the software of the Chrome OS device is regularly updated to the latest version of Chrome OS for optimal compatibility and security.

Login to your Google Admin console with an administrator account.
Navigate to Menu > Devices > Chrome > Apps & extensions > Kiosks.

Note: To apply the setting, select the top organizational unit else select a child organizational unit.
Set the chrome client app Installation policy to Installed.
Choose the Chrome client app beside the Auto-launch app.

How to Configure Kiosk Application Policies

To provide the best user experience on your Chrome OS devices, configure the enableLogoutTriggeredQuit and enableDisconnectionTriggeredQuit policies in the Chrome client to empower administrators to create an environment that mirrors the familiarity and simplicity of traditional systems, such as Windows, even on ChromeOS devices.

Using the enableLogoutTriggeredQuit and enableDisconnectionTriggeredQuit policies in the Chrome client, provides an enhanced user experience to control the behavior of the client upon logout and disconnection.

The following section describe how to configure these policies to automatically launch a Kiosk app on a Chrome client device.

Prerequisites

Note: Ensure that the software of the Chrome OS device is regularly updated to the latest version of Chrome OS for optimal compatibility and security.

Login to your Google Admin console with an administrator account.
Navigate to Menu > Devices > Chrome > Apps & extensions > Kiosks.

Note: To apply the setting, select the top organizational unit else select a child organizational unit.
Click Additional settings.
Configure the Chrome client application policies.
Click Save.

Configuring Kiosk App Policy Priorities

The enableLogoutTriggeredQuit and enableDisconnectionTriggeredQuit are Google Chrome client policies that enhance the user experience by controlling the client's behaviour after certain events.

When the enableLogoutTriggeredQuit policy is enabled, it instructs the chrome client to automatically close upon successful user logout.
When the enableDisconnectionTriggeredQuit policy is enabled, it triggers the Chrome client to quit when all active desktops and applications are disconnected.

To achieve a harmonized loop of operations, you can integrate these policies with other settings such as the default server, default desktop or application, and auto-launch kiosk app.

When a user powers on their ChromeOS device, the Chrome Client starts automatically and connects to the designated default server without any inputs.
After successful authentication, the client navigates and connects to the default desktop or application. This process removes the need for users to search with list servers, application menus, or areas which they might not be familiar.
When a user logs out or disconnects from the session, the client application shuts down. The Chrome OS immediately reboots the Chrome client and is ready for another user to login.

You apply the policies to all servers or only specific servers. See How to Configure Kiosk Application Policies section to configure the Kiosk app policies. Use the following configuration to configure the policies in common-setting that applies to all servers:

{
  "broker_list": {
    "Value": {
      "settings": {
        "common-setting": {
          "enableLogoutTriggeredQuit": true,
          "enableDisconnectionTriggeredQuit": true,
        }
      }
    }
  }
}

Use the following configuration to configure the policies for specific servers:

{
  "broker_list": {
    "Value": {
      "settings": {
        "server-list": [
          {
            "server": "[BrokerServerAddress]",
            "enableLogoutTriggeredQuit": true,
            "enableDisconnectionTriggeredQuit": true,
          }
        ]
       }
      }
    }
  }

In case of a conflict between the settings configured in common-setting and the server-list, the settings in server-list takes precedence for that specific server. Ensure to follow the hierarchy as shown in the following configuration when configuring these policies to optimize the user experience:

After you auto-launch the Kiosk app on the Chrome OS device and configure the Kiosk app policies for the Horizon Client app, edit the following configuration to set the policy priorities between common-setting and server-list.

{
  "broker_list": {
    "Value": {
      "settings": {
        "server-list": [
          {
            "server": "[BrokerServerAddress]",
            "username": "[loginUsername]",
            "default": true,
            "desktopID": "[defaultDesktopId]",
          }
        ],
        "common-setting": {
          "enableLogoutTriggeredQuit": true,
          "enableDisconnectionTriggeredQuit": true,
           }
      }
    }
  }
}

Esta página foi útil?

Using a Remote Desktop or Published Application

Feature Support for Chrome Clients

Supported Windows Virtual Desktops

Supported Published Desktops on RDS Hosts

Supported Linux Desktops

Internationalization

Touchpad, Touchscreen, Keypad, and Mouse Gestures

Keyboards and Keypads

Clicking

Dragging

Right-clicking

Scrolling and Scrollbars

Zooming In and Out

Window Resizing

Sound, Music, and Video

Adjusting the Sound in Remote Desktops and Published Applications

Using Remote Desktops

Using Published Applications

Copying and Pasting Text and Images

Logging Copy and Paste Activity

Transferring Files Between the Client and a Remote Desktop or Published Application

Set File Association

Use Multiple Sessions of a Published Application From Different Client Devices

Using Published Applications in Kiosk Mode

How to Automatically Launch a Kiosk Application on a Chrome OS Device

How to Configure Kiosk Application Policies

Configuring Kiosk App Policy Priorities

Enviar feedback sobre este tópico

Escreva a revisão

Feature Support for Chrome Clients

Supported Windows Virtual Desktops

Supported Published Desktops on RDS Hosts

Supported Linux Desktops

Internationalization

Touchpad, Touchscreen, Keypad, and Mouse Gestures

Keyboards and Keypads

Clicking

Dragging

Right-clicking

Scrolling and Scrollbars

Zooming In and Out

Window Resizing

Sound, Music, and Video

Adjusting the Sound in Remote Desktops and Published Applications

Using Remote Desktops

Using Published Applications

Copying and Pasting Text and Images

Logging Copy and Paste Activity

Transferring Files Between the Client and a Remote Desktop or Published Application

Set File Association

Share Access to Local Folders and Drives with Client Drive Redirection

Use Multiple Sessions of a Published Application From Different Client Devices

Using Published Applications in Kiosk Mode

How to Automatically Launch a Kiosk Application on a Chrome OS Device

How to Configure Kiosk Application Policies

Configuring Kiosk App Policy Priorities