Overview

This article provides instructions on how to install and configure a Parallels RAS RD Session Host (RDSH) server, so it can be used to dynamically launch and deliver Cloudpaged applications via AppsAnywhere.

It is assumed that the RDSH server has already been configured as part of the Parallels RAS Farm and they have access to AppsAnywhere to run Cloudpaged applications.

Refer to the Add an RD Session Host section of the RAS Administrators Guide if servers need adding to the Farm.

The steps in this article apply to Windows Server 2008 R2 and later. 

Note

  • Addition, removal and management of the RDSH servers within the RAS farm is completed by customers

  • AppsAnywhere client deployment and upgrades on the RDSH servers are the customer's responsibility

  • AppsAnywhere Support cannot install and manage the clients or RDSH servers for customers

Installing the Client and Player

The latest AppsAnywhere Client and Cloudpaging Player installers can be obtained from Latest Releases.

NOTE: If the intention is for users to have access to OneDrive for file saving, then the AppsAnywhere OneDrive Launcher will also need to be installed. 

Managed Deployment

It is recommended that you use a managed deployment method such as Group Policy or SCCM to perform the installation of the AppsAnywhere Client and Cloudpaging Player. This will allow you to easily carry out future updates on an RDSH server(s).

You can do this by following Deploying AppsAnywhere Client.

Manual Deployment

Alternatively you can download the AppsAnywhere Client and perform a manual installation by logging on to the Parallels RAS RDSH server and accessing AppsAnywhere.

If performing a manual installation, simply step through the installer selecting all of the default options.

Assuming that AppsAnywhere is configured to pre-deploy Cloudpaging Player, this will be installed the first time the AppsAnywhere Client starts, straight after the installation.

Otherwise, you will also need to download and install Cloudpaging Player manually.

Publishing the AppsAnywhere Launcher(s) in Parallels RAS

In order for the AppsAnywhere Client to receive instructions the AppsAnywhereLauncher.exe must be added as a published resource within the Parallels RAS Farm/Site.

NOTE: This only needs to be completed during initial setup.

Launch the Parallels Remote Access Server Console and select the Publishing option from the left-hand tree.  Right click on the Publishing Resources entry and select Add. Alternatively click the Add... button at the bottom of the window.

On the Select Item Type dialog select Application and click Next.

On the Select Server Type dialog select RD Session Hosts and click Next.

On the Select Application Type dialog select Single Application and click Next.

On the Publish From dialog select the relevant RDSH Server(s) or Server Groups and click Next.

Click the ... button next to the Target field and browser to the AppsAnywhereLauncher.exe file.  This EXE is located in the AppsAnywhere Client installation directory "\Program Files\Software2\AppsAnywhere\". 

Once complete, click Finish.

Each application published within Parallels RAS is assigned an ID number.  You need to make a note of this number as it will be required when publishing applications within AppsAnywhere for use on this Parallels RAS RDSH server. In this example the AppsAnywhereLauncher.exe published application has an ID of 13.  E.g :-

Once the AppsAnywhere client is published and you have a note of the Application ID, the Parallels RAS system is configured to dynamically receive and deliver Cloudpaged applications via AppsAnywhere.

If the the intention is for users to have access to OneDrive for file saving, then the AppsAnywhere OneDrive Launcher will also need to be published in the same way.