You might want to use agent-to-client redirection to conserve resources or as an added security layer. If employees are working in a remote desktop or application and they want to watch videos, for example, you might redirect those URLs to the client machine so that no extra load is put on the data center. Or for security purposes, for employees working outside the company network, you might want all URLs that point to external locations outside the company network to be opened on an employee's own client machine.
You could, for example, configure rules so that any content that is not company-related, that is, any URLs that do not point to the company network, are redirected to open on the client machine. In this case you could use the following settings, which include regular expressions:
- For agentRules: .*.mycompany.com
This rule redirects any URL that contains the text mycompany.com to be opened on the specified remote desktop or application (agent).
- For clientRules: .*
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 remote application or desktop, the client rules are checked first.
- If the URL matches a client rule, the agent rules are checked next.
- If there is a conflict between the agent rules and the client rules, the link is opened locally. In this case, the URL is opened on the agent machine.
- If there is no conflict, the URL is redirected to the client.
In the example, the client and agent rules conflict because URLs with mycompany.com are a subset of all URLs. Because of this conflict, URLs that include mycompany.com are opened locally. If you click a link that includes mycompany.com in the URL while in a remote desktop, the URL is opened on that remote desktop. If you click a link with mycompany.com in the URL in it from a client system, the URL is opened on the client.