Parallels RAS Reference Architecture
ProductsSupportPartnersDocumentation
  • Introduction
    • Parallels RAS release history
    • What is Parallels RAS
    • Advantages of Parallels RAS Solution
    • Parallels RAS Components
    • Understanding Deployment Scenario Diagrams
    • Parallels RAS Basic Concepts
  • Deployment Scenarios
    • General Considerations
    • Parallels RAS Deployment Scenarios
      • Single Farm with One RD Session Host
      • Single Farm with Two RD Session Hosts
      • Single Farm with RD Session Host Auto Scaling
      • Single Farm with VDI Hosts
      • Single Farm with Remote PC Hosts
      • Single Farm with Mixed Hosts
      • Single Farm with Public & Private RAS Secure Gateways
      • Single Farm with Dual RAS Secure Gateways
      • High Availability with Multiple Gateways
      • High Availability with Single-hop or Double-hop DMZ
        • Single-hop DMZ (two firewalls)
        • Double-hop DMZ (three firewalls)
      • RAS on Microsoft Azure
      • Azure Virtual Desktop integration
      • Mixed Scenarios
        • Multi-Site Scenario
        • Business Continuity and Disaster Recovery
        • Secure Setup with Double-hop DMZ and Second-Level Authentication
        • SAML SSO authentication
      • Multi-Tenant Architecture
      • Management Portal
    • Client Manager and Desktop Replacement
  • Capacity Considerations
  • Deploying Parallels RAS Reporting
    • One Site with Multiple RD Session Hosts
    • Multiple Sites with Multiple RD Session Hosts and Remote SQL Server
  • Port Reference and SSL Certificates
    • Port reference
      • Parallels Client
      • Web browsers
      • HALB
      • RAS Secure Gateway
      • RAS Connection Broker
      • RAS Console
      • SSRS
      • RAS Reporting
      • RAS Web Administration Service (REST/Management Portal)
      • RAS PowerShell
      • RAS Provider Agent
      • RAS Enrollment Server
      • RAS RD Session Host Agent
      • RAS Guest Agent
      • RAS Remote PC Agent
      • Tenant Broker
      • Active Directory and Domain Services ports
    • SSL Certificates
      • Using a Third-Party Trusted Certificate Authority
      • Using Enterprise Certificate Authority
      • Assign a Certificate to a Gateway
      • Parallels Client Configuration
Powered by GitBook

Social media

  • Facebook
  • Twitter
  • LinkedIn
  • YouTube

Other Resources

  • Feedback

© 2025 Parallels International GmbH. All rights reserved.

On this page

Was this helpful?

Export as PDF
  1. Deployment Scenarios

General Considerations

Regardless of the size of a Parallels RAS installation, redundancy among core components of your setup is recommended to ensure the greatest possible uptime. For small deployments, all roles can be installed on a single server, whereas role segregation is recommended for large setups.

The physical location of a Parallels RAS farm, including RD Session Hosts and VDI hosts, must be selected based on the location of back-end resources, such as databases and file servers. This means that if a front-end application connects to a database or works with files on a file server, the RD Session Host on which it will be installed should be located close to the database (or the file server) on the intranet with fast, reliable, low latency LAN connections. For example, let's say you have a client-server application that you want to make available to your users. To do so, you will install the client part on an RD Session Host and publish it for your users. The database will continue to run on a dedicated server. To guarantee fast and reliable database access, the RD Session Hosts server and the database server must be close to each other on the local network.

PreviousDeployment ScenariosNextParallels RAS Deployment Scenarios

Last updated 9 months ago

Was this helpful?