After you create and assign a URL content redirection setting, perform certain steps to verify that the setting is working properly.


Become familiar with vdmutil command-line interface options and requirements and verify that you have sufficient privileges to run the the vdmutil command. See Using the vdmutil Command-Line Utility.


  1. Log in to the Connection Server instance.
  2. Run the vdmutil command with the --readURLSetting option.

    For example:

    vdmutil --readURLSetting --urlSettingName url-filtering --authAs johndoe 
    --authDomain mydomain --authPassword secret

    The command displays detailed information about the URL content redirection setting. For example, the following command output for the url-filtering setting shows that HTTP and HTTPS URLs that contain the text google.* are redirected from the client to the local application pool named iexplore2012.

    URL Redirection setting url-filtering
       Description                                     : null
       Enabled                                         : true
       Scope of URL Redirection Setting                : LOCAL
       URL Scheme And Local Resource handler pairs
          URL Scheme                                   : http
          Handler type                                 : APPLICATION
          Handler Resource name                        : iexplore2012
          URL Scheme                                   : https
          Handler type                                 : APPLICATION
          Handler Resource name                        : iexplore2012
          No client patterns configured
  3. On a Windows client machine, open Horizon Client, connect to the Connection Server instance, click URLs that match the URL patterns configured in the setting, and verify that the URLs are redirected as expected.
  4. On the same Windows client machine, open the registry editor (regedit) and check the registry keys in the path \Computer\HKEY_CURRENT_USER\Software\Vmware. Inc.\VMware VDM\URLRedirection\.

    You should see a key for each protocol specified in the setting. You can click a protocol to see the rules associated with that protocol. For example, agentRules shows the URLs that are being redirected, brokerHostName shows the IP address or fully qualified host name of the Connection Server instance that is used when redirecting the URLs, and remoteItem shows the display name of the desktop or application pool that handles the redirected URLs.