This guide provides a quick look at how to configure the Parallels Remote Application Server Web Portal following a successful installation.
The Remote Application Server Web Portal allows users to connect to published resources through a web interface.
When a client connects, user credentials are provided and authenticated, and a list of published resources are made available.
A locally installed Parallels RDP Client is still required. That said, the Remote Application Server Web Portal attempts to detect whether the client is installed. If detection fails, a download link is presented to the user so that the client is downloaded.
The Remote Application Server Portal is available in a separate installation package. The following requirements need to be met in order to successfully deploy it:
- For a list of Supported Server Operating Systems see here
- Microsoft .NET Framework II/III
- ASP.NET role
- IIS6 or IIS7
- Existing RAS Farm
Supported Client Operating Systems and Browsers
Automatic Client Detection and Installation
Make sure all Windows programs are closed before you begin the installation.
Run the Remote Application Server Web Portal setup program by double-clicking on the RASWebPortal.msi or RASWebPortal-x64.msi file on the IIS machine that will be used as your access point to the published applications from the Web Portal.
We recommend that you do not install the Remote Application Server Portal on an Active Directory machine.
A welcome dialog box will appear. Close other Windows programs and click Next. Proceed to run through the installation wizard, noting the following information:
- The Secure Client Gateway is installed on port 80 by default and is configured to forward HTTP requests to the local host, on port 81. Therefore, Clients will still be able to access the Web Portal from port 80. You can choose to install the Web Service on any other port, and also use an existing port used by other web sites.
- IIS7 caches dynamic content as well as static content.
Configuring the Remote Application Server Portal
The Remote Application Server Portal provides two different login interfaces.
As a normal user, one can login with the following URL:
As an administrative user, one can login with the following URL:
As an administrator, one would need to login using the admin portal, using the admin URL outlined above.
An administrator can log in using credentials with administrative rights on the IIS machine.
Once logged in, the following settings are made available to the administrator:
- Farm Settings
- General Settings
The first step for successful configuration of the Remote Application Server Web Portal is to configure the farm users will be connecting to. This is done in Farm Settings by specifying the name of the farm users will connect to:
Once the farm has been added, the user is presented with a number of options as per below:
Note: During setup in most cases administrators provide the internal hostname or IP address of the ClientSecureGateway. This will work only for internal users since the Remote Application Server Portal passes on the gateway information directly to the clients.
If the Remote Application Server Portal is available online and an external user tries to connect and launch a published resource, if they cannot resolve and connect over the internal hostname provided, the connection will fail.
As a result, it is important to make the ClientSecureGateway users are connecting through available online and to configure the option to Override 2X Secure Client Gateway IP/Host. This will pass connectivity details that can be used by external uses.
Accessing the Remote Application Server Web Portal as a user
A user can login to the RAS Portal using the following address format: http://localhost/2XWebPortal/login.aspx
Upon successful login, users will be able to select resources and launch them directly from the browser.
Upon launching a resource, the Remote Application Server Portal will pass connection information to the locally installed Parallels Client, which will in return initiate the connection to access the published resource.