If you have a Cloud Pod Architecture environment, you can create a global URL content redirection setting that redirects specific URLs to open on a remote desktop or published application in any pod in the pod federation.
A global URL content redirection setting is visible across the pod federation. When you create a global URL content redirection setting, you can redirect URLs to global resources, such as global desktop entitlements and global application entitlements.
You can configure any number of protocols, including HTTP, HTTPS, mailto, and callto. The callto protocol is not supported for redirection with the Chrome browser.
As a best practice, configure the same redirection settings for the HTTP and HTTPS protocols. That way, if a user types a partial URL into Internet Explorer, such as mycompany.com, and that site redirects from HTTP to HTTPS automatically, the URL Content Redirection feature works as expected. In this example, if you set a rule for HTTPS, but do not set the same redirection setting for HTTP, the partial URL that the user types is not redirected.
For complete information about configuring and managing a Cloud Pod Architecture environment, see the Administering Cloud Pod Architecture in Horizon document.
VMware recommends that you do not create more than one setting for URL content redirection.
To create a local URL content redirection setting, see Create a Local URL Content Redirection Setting.
Prerequisites
- Become familiar with vdmutil command-line interface options and requirements and verify that you have sufficient privileges to run the vdmutil command. See Using the vdmutil Command-Line Utility on a Connection Server Instance.
- Become familiar with the syntax for URLs in URL content redirection settings. See Syntax for the --agentURLPattern Option.
Procedure
Example: Configuring a Global URL Content Redirection Setting
The following example creates a global URL content redirection setting called url-filtering that redirects all client URLs that include the text http://google.* to the global application entitlement called GAE1.
vdmutil --createURLSetting --urlSettingName url-filtering --urlRedirectionScope GLOBAL --urlScheme http --entitledApplication GAE1 --agentURLPattern "http://google.*" --authAs johndoe --authDomain mydomain --authPassword secret
The following example updates the url-filtering setting to also redirect all URLs that contain the text https://google.* to the global application entitlement called GAE1.
vdmutil --updateURLSetting --urlSettingName url-filtering --urlRedirectionScope GLOBAL --urlScheme https --entitledApplication GAE1 --agentURLPattern "https://google.*" -authAs johndoe --authDomain mydomain --authPassword secretThe following example updates the url-filtering setting to redirect all URLs that contain the text "mailto://.*.mycompany.com" to the global application entitlement called GA2.
vdmutil --updateURLSetting --urlSettingName url-filtering --urlRedirectionScope GLOBAL --urlScheme mailto --entitledApplication GAE2 --agentURLPattern "mailto://.*.mycompany.com" --authAs johndoe --authDomain mydomain --authPassword secret
What to do next
Assign the URL content redirection setting to a user or group. See Assign a URL Content Redirection Setting to a User or Group.