Configuring Remote Desktop Features

Using Group Policy Settings to Configure Client-to-Agent Redirection
The URL Content Redirection ADMX template le (urlRedirection-enUS.admx) contains group policy
seings that you can use to create rules that redirect URLs from the client to a remote desktop or application
(client-to-agent redirection).
N The preferred method for conguring client-to-agent redirection is to use the vdmutil command-line
interface. Because GPOs are not supported by macOS, you cannot use GPOs to congure client-to-agent
conguration if you have macOS clients.
To create a rule for client-to-agent redirection, you use the remoteItem option to specify the display name of
a remote desktop or application pool and the agentRules option to specify the URLs that should be
redirected to the remote desktop or application. You must also use the brokerHostname option to specify
the IP address or fully qualied domain name of the Connection Server host to use when redirecting the
URLs to a remote desktop or application.
For example, for security purposes you might want all HTTP URLs that point to the company network to be
opened in a remote desktop or application. In this case, you might set the agentRules option
to .*.mycompany.com.
For URL Content Redirection template le installation instructions, see “Add the URL Content Redirection
ADMX Template to a GPO,” on page 55.
URL Content Redirection Limitations
The behavior of the URL Content Redirection feature might have certain unexpected results.
n
If the URL opens a country-specic page based on the locale, the source of the link determines the locale
page that is opened. For example, if the remote desktop (agent source) resides in a data center in Japan
and the user computer resides in the U.S., if the URL is redirected from the agent to the client machine,
the page that opens on the U.S. client is the Japanese page.
n
If users create favorites from Web pages, the favorites are created after redirection. For example, if a
user clicks a link on the client machine and the URL is redirected to a remote desktop (agent), and the
user creates a favorite for that page, the favorite is created on the agent. The next time the user opens
the browser on the client machine, the user might expect to nd the favorite on the client machine, but
the favorite was stored on the remote desktop (agent source).
n
Files that users download appear on the machine where the browser was used to open the URL, for
example, when a user clicks a link on the client machine and the URL is redirected to a remote desktop.
If the link downloaded a le, or if the link is for a Web page where the user downloads a le, the le is
downloaded to the remote desktop rather than to the client machine.
n
If you install Horizon Agent and Horizon Client on the same machine, you can enable URL Content
Redirection in Horizon Agent or in Horizon Client, but not in both. On this machine, you can set up
either client-to-agent redirection or agent-to-client redirection, but not both.
Unsupported URL Content Redirection Features
The URL Content Redirection feature does not work in certain circumstances.
Shortened URLs
Shortened URLs, such as https://goo.gl/abc, can be redirected based on ltering rules, but the ltering
mechanism does not examine the original unshortened URL.
Chapter 3 Configuring URL Content Redirection
VMware, Inc. 67