Skip to main content
Skip table of contents

Configuring Parallels RAS RDSH Servers for use with AppsAnywhere


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. 

  • 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.


Regardless of the deployment mechanism, the InstitutionIdmust be set in registry on each RDSH server in:


  • Type = REG_SZ

  • Value = InstitutionId

The InstitutionId value is displayed in AppsAnywhere Admin > Help > About or in the AppsAnywhere Client Log.

Managed Deployment

It is recommended to follow Deploying AppsAnywhere Client and use the Fully Managed Update Process method such as Group Policy or SCCM to perform the installation of the AppsAnywhere Client and Cloudpaging Player.

Manual Deployment

Alternatively perform a manual installation by logging onto each Parallels RAS RDSH server and running the installers.

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, which depends on the version:

  • AppsAnywhere Client 1.x: "\Program Files\Software2\AppsAnywhere\"

  • AppsAnywhere Client 2.x: "\Program Files\AppsAnywhere\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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.