AppsAnywhere Cloud Deployment Guide
Introduction
Welcome to your Deployment Guide for AppsAnywhere.
The aim of this document is to gather the details that AppsAnywhere will need to configure a new AppsAnywhere instance.
This article only applies to AppsAnywhere Cloud deployments.
Contacting AppsAnywhere
If at any stage you cannot find the information you need or have any questions, please reach out via GuideCX or AppsAnywhere Support.
Our dedicated team are also available to help you throughout this process and we can arrange further support calls as needed.
Prerequisites
To complete onboarding, the following information will be required.
Network File Share
A simple network share is required for application delivery to managed devices.
If the share is hosted in Azure, please ensure the share is created and access granted according to https://docs.microsoft.com/en-us/azure/storage/files/storage-files-quick-create-use-windows.
See the following for more information:
Network File Share Checklist
Please update the table with the file share path.
Usage | Network Location | Sizing |
Precache files | \\filestore.uni.edu\AppsAnywhere\Precache | 100GB |
Confirm:
Item | Details | Completed |
Permissions | Granted for the required users and groups | |
Storage | 100GB allocated |
The network file share will be used to configure a precache location for How to Configure and Use Pre-caching on Managed Devices once applications have been deployed through AppsAnywhere.
Identity Provider (IDP) Configuration
A SAML identity provider will be used to provide authenticated access and single sign on (SSO) to the AppsAnywhere instance.
IDP Checklist
The following information is required to perform the initial first stage configuration:
Property | Value |
IDP Metadata URL or XML file | e.g. https://login.microsoftonline.com/xxxxxxxxx/federationmetadata/2007-06/federationmetadata.xml |
Authentication will be completed later in the project once AppsAnywhere is online by following:
SAML Attribute Provisioning information
SAML attributes retrieved when a user authenticates form the basis of the filtering process used to display which relevant applications have been provisioned to the user. This information is used by AppsAnywhere to know which attribute from the SAML response should be used to retrieve group membership(s)
Attribute checklist
To create and configure user access, SAML user and group attribute names are required:
Property | Attribute | Expected Value/Format |
User | e.g. http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name | e.g. user@domain |
Group | e.g. http://schemas.microsoft.com/ws/2008/06/identity/claims/groups | e.g. xxxxxxxx-8025-xxxx-a342-xxxxxxxx6fde |
This information will be used to configure mapping once AppsAnywhere is online by following:
AppsAnywhere directory user
For the AppsAnywhere team to install, administer and access AppsAnywhere, a directory account is needed.
Username | appsanywhere |
Usage |
|
Password Policy |
|
Directory user checklist
Item | Details | Completed |
Credentials | Provided securely |
Administrative User accounts
To manage the applications and delivery methods within AppsAnywhere, privileged user accounts will be created for each person requiring access.
Details of the available roles are available on https://docs.appsanywhere.com/appsanywhere/user-roles-and-permissions.
Account checklist
Provide the user account information and required role(s):
User or Group Attribute Value | Role(s) |
|
|
|
|
|
|
Create a CNAME
To create the necessary custom domain name (DNS) entries for AppsAnywhere, please submit a request to the relevant team within your organization.
The following are required for AppsAnywhere configuration:
DNS Entry | Usage | |
|---|---|---|
| 1 | appsanywhere.uni.edu | AppsAnywhere URL for end user access |
| 2 | paging1.uni.edu | Paging service URL for application delivery |
| 3 | paging2.uni.edu | Paging service URL for application delivery |
A member of the AppsAnywhere team will provide the URLs that needs to be redirected as part of the AppsAnywhere Customer Journey | Installation.
CNAME checklist
Please provide the DNS entries (where ‘uni.edu’ is the organization’s domain name e.g. 'appsanywhere.edu'):
| 1 | e.g. appsanywhere.uni.edu |
| 2 | e.g. paging1.uni.edu |
| 3 | e.g. paging2.uni.edu |
SSL Certificate
To provide the AppsAnywhere team with the SSL certificate required for the AppsAnywhere URL, follow https://docs.appsanywhere.com/appsanywhere/ssl-certificates and contact the relevant team within your organization.
SSL Certificate Checklist
Update the table with the download location of the certificate .pfx file.
URL |
https://download.uni.edu/appsanywheressl.pfx |
Please confirm:
Item | Details | Completed |
Password | Provided securely |
This certificate should be used for the service provider sections of SAML 2.0 Common | Service Provider Settings during the AppsAnywhere Customer Journey | Configuration stage.
Handover to AppsAnywhere
Please review the details to ensure all information has been provided to the AppsAnywhere team.
Next steps
Provide the details securely and directly in GuideCX.
Mark the GuideCX Task as Done
Once AppsAnywhere is ready for handover, a member of the AppsAnywhere team will be in touch.
Kind Regards
AppsAnywhere Implementations