7.0

Feature Limitations
The behavior of this feature might have the following unexpected results:
n
If the URL opens a country-specific page based on the locale, the locale page that is opened is
determined by the source of the link. For example, if the remote desktop (agent source) resides in a data
center in Japan and the user's 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 get created after redirection. For example, say a
user clicks a link on the client machine and the URL is redirected to a remote desktop (agent). If the user
creates a favorite for that page, the favorite gets created on the agent. The next time the user opens the
browser on the client machine, the user might expect to find the favorite on the client machine, but the
favorite was stored on the agent (remote desktop).
n
Files that users download are downloaded to the machine whose browser was used to open the URL.
For example, say a user clicks a link on the client machine, and the URL is redirected to a remote
desktop. If the link was for downloading a file, or if the link is for a Web page where the user
downloads a file, the file is downloaded to the remote desktop rather than the client machine.
The URL Content Redirection feature does not work in the following circumstances:
n
Shortened URLs such as https://goo.gl/abc can be redirected based on filtering rules, but the filtering
mechanism does not look at the original un-shortened URL. For example, if you have a rule that
redirects URLs containing acme.com, an original URL such as http://www.acme.com/some-really-long-
path, and a shortened URL of the original URL such as https://goo.gl/xyz, the original URL is
redirected but not the shortened URL.
Workaround: Create rules to block or redirect URLs from the Web sites most often used for shortening
URLs.
n
Embedded HTML pages will bypass URL redirection. For example, say a user goes to a URL that does
not match a URL redirection rule. If page contains an embedded HTML page (an iFrame or inline
frame) whose URL does match a redirection rule, the URL redirection rule does not work. The rule
works only on the top-level URL.
n
URL Content Redirection does not work in situations where Internet Explorer plug-ins are disabled, for
example, when the user switches to InPrivate Browsing in Internet Explorer. (People use private
browsing so that Web pages and files downloaded from Web pages will not be logged in to the
browsing and download history on their computer.) This limitation arises because the URL Redirection
feature requires a certain Internet Explorer plug-in to be enabled, and private browsing disables these
plug-ins.
Workaround: Use the GPO setting to prevent users from disabling plug-ins. These settings include the
following: "Do not allow users to enable or disable add-ons" and "Automatically enable newly installed
add-ons." In the Group Policy Management Editor, these settings can be found under Computer
Configuration > Administrative Templates > Windows Components > Internet Explorer.
Workaround specifically for Internet Explorer: Use the GPO setting to disable InPrivate mode. This
setting is called "Turn off InPrivate Browsing." In the Group Policy Management Editor, these settings
can be found under Computer Configuration > Administrative Templates > Windows Components >
Internet Explorer > Privacy.
These two workarounds are recommended best practices and can prevent issues with redirection that
situations other than private browsing can cause.
Setting Up Desktop and Application Pools in View
178 VMware, Inc.