How to configure Gateway Redirection Policy

0 users found this article helpful

Scenario

It's required to change Parallels Client > Primary Connection for users connecting to all or specific gateway(s).

Policy requirements and description

Redirection policy must be enabled ONLY with Policy Criteria due to the known issue

It's designed specifically for changing Primary Connection properties in order to change the primary connection point for users from one Gateway to another.

For the scenario of switching from one particular Gateway (GW1) to another (GW2), There must be 2 policies created: one with Gateway Redirection for e.g. GW1 and one without it for GW2. Policy Criteria defines which policy should work at which Gateway.

Gateway Redirection will change the existing Primary Connection from GW1 to GW2 for users who are connecting to GW1.

Once changed to GW2, it will immediately try to connect and get a published resources list. At this point, the second policy should work for GW2 in order to make sure that Gateway Redirection will not be applied anymore.

Configuration

- Create Policy for GW1 add required Users or Groups and enable Criteria:

- Configure Criteria for GW1 policy:

- Configure Gateway Redirection:

- Configure another Policy for GW2:

- Configure Criteria for GW2 Policy:

- Make sure that for GW2 Policy, Gateway Redirection is disabled:

Scenarios that should be avoided

Client connects to GW1 Policy applies and redirects to GW1 This will cause policy apply loop.

Client connects to GW1 GW1 Policy applies and redirects connection to GW2 Client connects to GW2 GW2 Policy applies and redirects to GW1 this will result in loop.

In both cases, loop will re-apply policies 10 times and then Parallels Client will produce error.

Was this article helpful?

Tell us how we can improve it.