AppsAnywhere is an app store-style platform that gives your students and staff easy access to the software they need, on and off-campus, including BYOD.

Multiple delivery methods are supported, so you can define the best way to deliver individual apps to your end-users, based on the device they are using and any app license restrictions.

This section of our documentation is designed to provide all the details you might need when preparing to deploy AppsAnywhere.


During new customer on-boarding, the AppsAnywhere team will discuss your specific requirements and provide a tailored AppsAnywhere Deployment Guide.

A Technical Call will then be arranged to answer any questions. Support is available from a dedicated consultant throughout your initial deployment.

To avoid additional effort, please do not deploy any servers or infrastructure until after you have received your Deployment Guide and discussed it with your Technical Consultant.

Infrastructure Components

A typical AppsAnywhere infrastructure will include servers and services as shown in Infrastructure Diagrams .

All AppsAnywhere and Cloudpaging infrastructure can be provisioned in the AppsAnywhere hosted solution.

Parallels RAS must be hosted on customer domain joined devices. See Parallels Remote Application Server (RAS) deployment documentation for more information.


AppsAnywhere provide AppsAnywhere servers as a virtual appliance, ready to import to your chosen hypervisor.

  • End-users will connect to your AppsAnywhere Portal to access and launch applications.

  • These servers also provide the Admin Portal where your app and system administrators can configure settings and deploy applications.

Please see the Server Requirements section for more details.

Network and Load Balancing

End-users will need to be able to connect to your AppsAnywhere Portal both on and off-site, from any location.

Unless you are configuring a single test instance, you will likely require multiple AppsAnywhere Servers for load balancing, fault tolerance, and to facilitate future upgrades.

Please see the Connectivity Requirements section for more details.


A connection to Active Directory (LDAPS) is required to verify which apps users can access, and as the initial login authentication method.

Once an LDAPS connection has been configured, additional authentication and SSO methods can also be supported.

Please see the Directory Requirements section for more details.


A Microsoft SQL database is required by AppsAnywhere to store configuration details for the applications and delivery methods, as well as usage records.

Please see the Database Requirements section for more details.

Test Machine

A domain joined machine is required for the AppsAnywhere team to test AppsAnywhere, in particular that single sign on functionality is operational. 

This can also be used as a management machine for Remote Access for AppsAnywhere Support.