# Multi-Site Scenario

This scenario is suited for environments where published resources are distributed between two or more physical locations. Different administrators can administer a Parallels RAS farm containing multiple sites.

<figure><img src="https://content.gitbook.com/content/jRndoUJVjRrmCN0WR7H6/blobs/O3Zn97kWwCAB7HfSi2KU/multi-sitescenario.png" alt=""><figcaption></figcaption></figure>

Each site consists of at least a RAS Connection Broker, RAS Secure Gateway (or multiple Secure Gateways), and agents installed on RD Session Host or VDI servers, or Windows PCs.

{% hint style="info" %}
**Note:** To add high availability for HALB, a second appliance can be deployed in each site.
{% endhint %}

If the resource set is similar, end users can use both sites via a single RAS connection. The following settings should be used as RAS connection properties in Parallels Client:

## **LAN users of Site1**

* Primary connection: local Primary Secure Gateway.
* Secondary connections:
  * Local Secondary Secure Gateway.
  * HALB VS IP address of Site2.

## **LAN users of Site2**

* Primary connection – local Primary Secure Gateway
* Secondary connections:
  * Local Secondary Secure Gateway
  * HALB VS IP address of Site1

## **WAN users**

* Primary connection - HALB VS IP address of Site1
* Secondary connections - HALB VS IP address of Site2

RAS connection settings can be configured either centrally (via Client Policy in the Parallels RAS Console) or manually.

## **Installation Notes**

RAS Connection Broker is installed using the Parallels RAS installer (standard installation).

HALB is installed as a ready-to-use virtual appliance and configured in HALB VS properties.

All other components are push-installed from the RAS console.