When a user connects to Parallels RAS from Parallels Client, they are presented with published resources (applications, desktops, documents, etc). The user selects a resource and launches it. The system load-balances user requests automatically and launches the resource from a least-loaded host. The user is then presented with the resource seamlessly via RDP protocol
The Parallels RAS building blocks are (see the previous section for a detailed explanation):
Farm
Site
Agents
The first server added to a farm creates a new site and becomes the primary RAS Connection Broker in that site. The server also becomes the farm’s Licensing Server handling device connection licenses. Every Connection Broker in the farm (when more than one exists) keeps a synchronized copy of the Parallels RAS configuration database. When the administrator makes any changes to the Parallels RAS configuration in the Parallels RAS console, the changes are replicated to all other Connection Brokers.
The following diagram illustrates a Parallels RAS installation with two sites (Site 1 and Site 2), each consisting of a primary Connection Broker (Primary CB), RAS Secure Gateway (SG), RD Session Host (RDS host 1), a second RD Session Host (RDS host 2), VDI (Virtual Desktop Infrastructure) server, and a Windows PC.
Adding more RAS Connection Brokers and RAS Secure Gateways adds redundancy to the system. HALB Virtual Server (VS) is a virtual representation of the HALB appliances (optional component), which can be added to load balance application traffic.
Note: Resources (RD Session Host, Remote PCs, VDI hosts) that are members of one site cannot be shared with other sites. For example, the RDS host 1 server is a member of Site 1, which means that it cannot be accessed by users who are connecting through a Secure Gateway and a Connection Broker located in Site 2.
