Configure Gateway Redirection

Redirection options allow you to move your existing users from one RAS Secure Client Gateway to another gateway within the same farm, or you can even redirect users to a gateway in a different farm.

Note: When setting gateway redirection, make sure that the gateway criteria (the Criteria node) does not conflict with it. Read the Gateway criteria subsection at the end of this section for the explanation.

To configure redirection options:

1. Select the Redirection node in the left pane of the Policy Properties dialog.
2. In the right pane, specify the new connection properties, including:
   • Gateway address
   • Connection mode
   • Port number
   • Alternative address

When this policy is applied to user devices, the following will happen:

• Parallels Client connection settings are automatically updated on each device.
• Parallels Client tests the new connection. If succeeded, the current connection policies are removed and new policies are added.
• If Parallels Client cannot connect to Parallels RAS using new settings, the application list will not be shown and an error message will be displayed saying that the redirection policy has failed to apply. The user will be advised to contact the system administrator.

Gateway criteria

If a policy has both Redirection and Criteria settings enabled and configured, a situation may occur when the policy is applied in an infinite loop on the client side, which will result in an error. Consider the following possible scenarios when this may happen:

• Parallels Client connects to gateway "A" and applies a policy, which redirects it back to gateway "A". This will continue to loop until Parallels Client gives up and displays an error to the user, which will say, "Failed to apply redirection policy....".
• Parallels Client connects to gateway "A" and applies policy "P1", which redirects it to gateway "B". As expected, Parallels Client connects to gateway "B" and applies policy "P2", which redirects it back to gateway "A" where it all began. This will will also continue to loop until Parallels Client gives up and displays the same error message as described above.

Once again, this may only happen if the Criteria node is enabled and specified gateways conflict with each other. To avoid it, make sure that the Gateway criteria option on the Criteria pane is set to if Client is connected to one of the following gateways and that the same policy is not applied again when Parallels Client is redirected to a new gateway.