You might want to use agent-to-client redirection to conserve resources, or as an added security layer. If employees watch videos in a remote desktop or published application, for example, you might redirect those URLs to the client machine so that no extra load is put on the data center. For employees that work outside the company network, you might want all URLs that point to external locations outside the company network to open on an employee's own client machine for security purposes.
For example, you can configure rules so that any URLs that do not point to the company network are redirected to open on the client machine. In this example, you might use the following settings, which include regular expressions:
- For Agent Rules: .*.mycompany.com
This rule redirects any URL that contains the text mycompany.com to be opened on the specified remote desktop or published application (agent).
- For Client Rules: .*
This rule redirects all URLs to the client, to be opened with the default client browser.
The URL Content Redirection feature uses the following process to apply client and agent rules:
- When a user clicks a link in a published application or remote desktop, the client rules are checked first.
- If the URL matches a client rule, the agent rules are checked next.
- If a conflict exists between the agent and client rules, the link opens locally. In this example, the URL opens on the agent machine.
- If no conflicts exist, the URL is redirected to the client.
In this example, the client and agent rules conflict because URLs that include mycompany.com are a subset of all URLs. Because of this conflict, URLs that include mycompany.com open locally. If you click a link that includes mycompany.com in the URL while in a remote desktop, the URL opens in that remote desktop. If you click a link that includes mycompany.com in the URL from a client system, the URL opens on the client.