User manual

Requirements for Using URL Content Redirection
With the URL Content Redirection feature, URL content can be redirected from the client machine to a
remote desktop or application (client-to-agent redirection), or from a remote desktop or application to the
client machine (agent-to-client redirection).
For example, you can click a link in the native Microsoft Word application on the client and the link opens in
the remote Internet Explorer application, or you can click a link in the remote Internet Explorer application
and the link opens in a native browser on the client machine. Any number of protocols can be congured for
redirection, including HTTP, mailto, and callto.
The supported browsers in which you can type or click a URL and have that URL redirected are Internet
Explorer 9, 10, and 11.
N This feature does not work for links clicked from inside Windows 10 universal apps, including the
Microsoft Edge Browser.
To use agent-to-client redirection, a Horizon administrator must enable URL Content Redirection during
Horizon Agent installation. For information, see the Seing Up Virtual Desktops in Horizon 7 or Seing Up
Published Desktops and Applications in Horizon 7 documents.
A Horizon administrator must also congure seings that specify how Horizon Client redirects URL
content from the client system to a remote desktop or application, or how Horizon Agent redirects URL
content from a remote desktop or application to the client machine. For conguration information, see the
Conguring Remote Desktop Features in Horizon 7 document.
Supported Desktop Operating Systems
Administrators create virtual machines with a guest operating system and install agent software in the guest
operating system. End users can log in to these virtual machines from a client device.
For a list of the supported Windows guest operating systems, see the View Installation document.
Some Linux guest operating systems are also supported if you have View Agent 6.1.1 or later, or
Horizon Agent 7.0 or later. For information about system requirements, conguring Linux virtual machines
for use in Horizon, and a list of supported features, see Seing Up Horizon 6 for Linux Desktops or Seing Up
Horizon 7 for Linux Desktops.
Preparing Connection Server for Horizon Client
Administrators must perform specic tasks to enable end users to connect to remote desktops and
applications.
Before end users can connect to Connection Server or a security server and access a remote desktop or
application, you must congure certain pool seings and security seings:
n
If you plan to use Unied Access Gateway, congure Connection Server to work with
Unied Access Gateway. See the Deploying and Conguring Unied Access Gateway document.
Unied Access Gateway appliances fulll the same role that was previously played by only security
servers.
n
If you are using a security server, verify that you are using the latest maintenance releases of
Connection Server 5.3.x and Security Server 5.3.x or later releases. For more information, see the View
Installation document.
n
If you plan to use a secure tunnel connection for client devices and if the secure connection is
congured with a DNS host name for Connection Server or a security server, verify that the client
device can resolve this DNS name.
Chapter 1 Setup and Installation
VMware, Inc. 11