FAQ

PRODUCT AND FEATURES

DOES AWINGU OFFER VDI?

No. At Awingu, we believe VDI isn’t the best medium to work securely on any device. Our solution is build around the aggregation of applications and files. We don’t rely on a desktop or desktop experience for that matter. If you really want, you can publish a remote desktop as an application in the Awingu workspace.

DOES AWINGU RUN MY APPLICATIONS?

No, Awingu’s platform will connect to application servers, SaaS, Web aps and files. Awingu does not host/run or impact your (legacy) applications on it’s software platform. These keep running on application servers (with Terminal Server/RDS). At Awingu, we want to be as little disruptive as possible to your existing IT architecture. 

DOES AWINGU REQUIRE TO REWRITE (LEGACY) APPLICATIONS?

No. Awingu makes your legacy applications and files available in any html5 browser as is. No rewriting of the application is required. Awingu wants to be as little disruptive as possible to your existing application landscape. That enables us to get you up-and-running in no time.

DOES AWINGU ELIMINATE THE NEED OF VPN/SSL SETUP?

Yes, Awingu also uses an encrypted connection and supports multi factor authentication which makes it a secure solution. As such, you will still be using SSL, but in a user-friendly fashion. However, you won’t have hassle-full VPN setups and login procedures to work remotely.

WHAT ARE THE MINIMUM REQUIREMENTS TO RUN AWINGU?

Awingu has very light and non-disruptive requirements. The requirements are described below:

minimum requirements for Awingu

WHAT SAAS SERVICES CAN I CONNECT WITH AWINGU?

There are 3 options to connect your SaaS services with Awingu. This implies end-users will have to log in only once into their online Awingu workspace. From there, they will automatically be signed in into their SaaS services. (Note: all 3 options can be mixed)

1. Leverage Awingu as Identity provider: Awingu acts as an Identity provider. Since Awingu 3.2 it has connectors to a number of popular SaaS services. These include Microsoft Office 365, Google Apps for Work, Salesforce.com, Freshdesk, Zoho, Confluence, Jira and Dropbox. It is possible to build custom connectors on demand. The usage of these SaaS services will also be covered in the usage insights reports. Usage of our SaaS connectors is described in detail in the admin guide.

2. Leverage integration with Microsoft’s Azure AD: If you are using Microsoft Azure AD to setup Single-Sign-On with SaaS services, you will also have the SSO when opening the SaaS service via Awingu.

3. Leverage integration with Okta: If you are using Okta to setup Single-Sign-On with SaaS services, you will also have the SSO when opening the SaaS service via Awingu.

CAN AWINGU REPLACE AZURE REMOTEAPP?

On August 12th, 2016, Microsoft announced stopping it’s Azure RemoteApp service. The service will be discontinued in August 2017. Read more about the options Microsoft suggests for migrating out of RemoteApp at https://docs.microsoft.com/en-us/azure/remoteapp/remoteapp-migrationoptions. While the communication mentions a partnership with Citrix for a replacing service, Awingu can offer a perfect alternative already today.

Try Awingu with two free concurrent users on Azure Marketplace (here) or, request a free trial account here.

On top of being available right now, Awingu also offers a richer solution compared to Azure RemoteApp. The table below gives a good summary view:

Awingu vs. RemoteApp

HOW IS AWINGU DIFFERENT FROM MICROSOFT RDS?

“How is Awingu different from Microsoft  RDS” (‘Remote Desktop Protocol’,  former ‘Terminal Server’) is one of the most frequent questions we get. Remote Desktop Services (RDS) is a Microsoft Windows service which extends desktop and application deployments to any device. It is a building block in Awingu solution. (Yes, that means you need a Microsoft RDS CAL in case you want to publish (classic) Windows applications into Awingu.)

The following table gives a short summary of how Awingu adds value on top of RDS.

Awingu vs RDS

WHAT ARE THE COSTS TO RUN A WORKSPACE IN AWINGU?

Very often we get the question “what is my total cost” for running Awingu? The answer, as you’d expect is: “It depends”.

It depends on so many factors: Are you deploying in a public cloud? On-premise? Do you want a fully redundant platform or not? What software are you running? Where are your operations based? How many users will run on Awingu? It`s impossible to map out all of the possible scenarios. However, at a higher level, we can bring the cost of Awingu down to the following building blocks. The costs are purely indicative and will depend on your specific context. They should only be used as a high-level guideline.

Total cost of Awingu* named user licenses vs. concurrent user licenses? http://www.awingu.com/what-is-the-pricing-per-concurrent-user/

WHAT ARE THE OPTIONS TO SECURELY LOGIN TO AWINGU?

Awingu provides multiple ways to securely authenticate with multi-factor authentication (MFA). The table below gives a summary of the different options.

 

MFA Awingu

HOW TO USE

HOW DIFFICULT IS IT TO USE AWINGU?

At Awingu, we believe in easy-of-use and simplicity. End-users surf to a URL on their browser – close to all recent browsers are tested by our teams – enter their login & password and get access to their workspace. The experience is consistent and optimized for usage across devices (e.g. laptop or tablet).

Have a look at this video to get an idea how simple it is. Or even better, take one of our trial accounts for a spin!

HOW TO DEPLOY AWINGU ON AN EXISTING CITRIX INFRASTRUCTURE?

Migrating away from an existing Citrix infrastructure to Awingu is one of our most asked questions. It’s actually a real easy 4 step process. Simple & fast. We’re describing it here below in full detail.

Note: There are a number of reasons why migrating from Citrix to Awingu is a good idea. We elaborate on this in more detail here.

Below is a picture of a typical Citrix XenApp Deployment:awingu vs citrix

Installing Awingu next to this setup can be achieved by deploying 1 (or more for load distribution or High Availability) in the Access Layer following this procedure which can be executed in less than 1 hour. 

1)     Download and setup Awingu according the regular installation guide.

Download the admin guide here

2)     Add non admin users to direct access user group

When ‘Citrix Virtual Delivery Agent’ is installed on a machine, non-administrators can no longer RDP to the machine. A new local group called Direct Access Users is created on each Virtual Delivery Agent. Add your non-administrator RDP users to this local group so they can RDP directly to the machine.

awingu vs citrix_02

– Enable non-admin RDP users to get direct RDP access –

Add here the security group for the users which should have access.

awingu vs. citirx 03

– Add security group for users with access –

3)     Enable RDP policy in Citrix studio

3.a. To be able to initiate a remote session a policy needs to be added to Citrix. Open the Citrix director and browse to the policy section. On the right top choose ‘Create Policy’

awingu vs citrix 04

– Create new policy –

3.b. In the search field search for: ‘Launching of non-published programs during client connection’ and select it.

awingu vs citirx 05

– Launching of non-published programs during client connection –

3.c. Enable this policy for all objects in this site

awingu vs citrix 06

– Enable for all objects –

3.d. Give it a meaningful name and enable the policy

awingu vs citrix 07

– Give a name and enable policy –

3.e. Set the policy priority higher

citrix vs awingu 08

– Set policy priority –

3.f. If you want to speed the policy up you can always update them manually

awingu vs citirx 09

– option: manually update policies –

4)     Optional: De-Install Citrix software from app servers

The result would be like in following picture:

awingu vs citrix 10

Please note that the Netscaler can be optionally used to loadbalance to the different Awingu appliances but any loadbalancer will do.

There is no need any more of the Citrix Control layer. The Awingu appliances have all knowledge needed to do the brokerage to the different RDS servers.

Have any questions or remarks? Please don’t hesitate and reach out to us.

INSTALLING AWINGU 'ALL-IN-ONE' ON AZURE

Introduction

The Awingu All-In-One App in the Microsoft Azure marketplace allows you not only to deploy an Awingu appliance, but also to deploy a complete Windows backend infrastructure and configure Awingu to use this backend.  The result of an Awingu All-In-One Azure marketplace solution is a pre-configured, ready-to-use Awingu environment hosted in the cloud.

This is very useful in following scenarios:

1. Greenfield projects where no existing Windows environment is available

2. Migration to the cloud

3. Testing purposes, e.g. to evaluate Awingu

Deployment

Deploying an Awingu All-In-One Azure marketplace solution is done through the Azure Portal using a wizard in 3 easy steps.

To start the wizard, search for ‘Awingu All-In-One’ on the Azure marketplace and click the ‘Create’ button.

The wizard will present you some options and questions in easy 3 steps.

Please note that Awingu All-In-One is not available in Azure Classic. 

awingu all in one 01

awingu all in one 02Basics

The first step ‘Basics‘ covers Azure settings and determines where your Awingu All-In-One environment will be deployed.

This is based on the Azure subscription and datacenter selected.  All virtual machines will be deployed in a single, newly created Resource Group.

Currently it is only possible to deploy in a new Resource Group.

Awingu Configuration

The second step ‘Awingu Configuration’ will present you with all options and questions required to deploy and configure the Awingu appliance.

Email address

Your email address to provide you with access to documentation and support. You will receive links and information on this address.

Public IP address

Public IP address on which your Awingu environment will be accessible from the internet.

DNS prefix

DNS prefix for the Awingu environment. You will be able to access your Awingu environment on {prefix}.{location}.cloudapp.azure.com.

Awingu recovery password

This password allows you to recover your Awingu environment in case of backend problems.

Awingu appliance size

Azure appliance size to use for the Awingu appliance.

Windows Backend Configuration

The third step ‘Windows Backend Configuration’ will present you with all options and questions required to deploy and configure the Windows backend servers. 

This backend will consist of 1 Active Directory server and a selectable amount of Windows application servers.  The Awingu appliance will be configured automatically to connect to these servers.

Admin username

Admin username for Awingu and Windows backend. This username will be domain administrator on the Windows backend.

Admin password

Admin password for Awingu and Windows backend.

Domain name

Windows domain name used for the Windows backend. (FQDN)

Application server count

Specify the number of application servers you want to deploy. These servers will host the Windows applications. The number of servers depends on the expected load. Servers can always be deployed later on and easily imported in Awingu.

Windows server size

Azure appliance size to use for all Windows servers

Summary

This step gives you a summary of earlier provided information for review.

If all information is correct, press OK to start deploying your Awingu All-In-One environment.

Next Steps

Congratulations! You have your Awingu All-In-One environment up-and-running!

Now you can navigate to http://{prefix}.{location}.cloudapp.azure.com and sign-in using the admin username and password provided in step 2 of the wizard.

COMMERCIAL AND PRICING

IS AWINGU ALSO A SERVICE PROVIDER?

No, Awingu is a software vendor. We do however sell our software to different types of Service Providers so they can build an offering around Awingu. Awingu is an ideal solution for Service Providers:

1. Fully multi-tenant with tenant personalization

2. Open API’s

3. Runs on any infrastructure (e.g. Azure Stack, vCloud)

4. Multi-node deployments, support for RDS farms,…

Typical Service Provider value propositions are:

1. Awingu-as-a-Service: where the SP hosts Awingu’s platform and resells to end-customers or channel partners at a price per month per user. The customer is responsible for his own applications;

2. Workplace-as-a-Service: Where the SP hosts and manages both the Awingu platform as well as other applications.

Also, we are part of cloud marketplaces such as the Microsoft Azure Marketplace.

Interested to build an offering based on Awingu’s platform? Contact us here

WHAT IS THE PRICING PER CONCURRENT USER?

Awingu sells license keys based on the number of ‘concurrent’ users. A minimum of 20 concurrent users needs to be purchased. Concurrent users can be compared to ‘bandwidth’; e.g. 20 concurrent users means that at any time 20 users can simultaneously log in into Awingu.

How many ‘named’ users does a concurrent user cover? It depends. The ratio can be as low as 1/5 when for example your company works in multiple shifts per day and employees don’t use their PC full-time. But equally, it be a 1/1 ratio when your employees are power-users and don’t work in shifts. A single employee (or user) can generate more than one concurrent user when he/she logs into Awingu from different devices at the same time, or when he/she logs into Awingu from different browsers at the same time. The number of concurrent users is not impact by the number of applications somebody opens.

Note: For Service Providers, a different pricing model is available. This is based on named users. Want more info? contact us here.

IS THE PRICE IMPACTED BY THE NUMBER OF APPLICATIONS OR FILES I CAN ACCESS?

No. You can link as many applications or files with Awingu as you wish. Our pricing is only based on the number of concurrent users.

CAN I RUN MY OWN APPLICATIONS IN THE AWINGU TRIAL?

Seeing is believing. Hence we offer a wide range of options to have your own ‘test run’ with Awingu.

Sign-up to our online trial account: You will get access to a pre-populated Awingu environment during 14 days. This demo.awingu environment runs in the Azure cloud. Here, it is not possible for you to add your own applications. Nevertheless, you`ll notice there is a wide variety of applications available to get the hang of it. Signing-up is possible via this form.

Setup your own Awingu trial platform via the Azure Marketplace or the IBM Cloud Marketplace: Just go the marketplace and start deploying. You can benefit from the 2 built-in concurrent users in Awingu (included since Awingu 3.1). You can test the full functionality of Awingu, add your own applications, etc…For support and access to our technical guides, sign-up to partner.awingu.com. You can also use our easy installation support movies. These are publicly available on our YouTube channel.

Setup Awingu on any cloud: the latest version of Awingu can be downloaded at download.awingu.com. You can benefit from the 2 built-in concurrent users in Awingu (included since Awingu 3.1). You can test the full functionality of Awingu, add your own applications, etc…For support and access to our technical guides, sign-up to partner.awingu.com. You can also use our easy installation support movies. These are publicly available on our YouTube channel.

Have an actual Proof-Of-Concept platform setup with 20 users by one of our partners or by Awingu. This service is available as a paying service. If interested, contact us here.

HAVE A SUGGESTION YOU WOULD LIKE TO SEE IN THE NEXT AWINGU RELEASE?

SUGGEST A FEATURE
ABOUT US

Awingu develops a software to simplify enterprise mobility and liberate legacy applications.
Our software aggregates all company files and applications to one secure online workspace that can be accessed from any device or OS using any HTML5-based browser.

FOLLOW US ON SOCIAL MEDIA
EMEA HEADQUARTERS

Awingu N.V.
Ottergemsesteenweg-Zuid 808 B44
9000 Gent, Belgium
Phone: +32 9 296 40 11
Email: info@awingu.com
VAT: BE 0832 859 222

US OFFICES

Awingu Inc.,
7th floor, 1177 Ave of the Americas,
NY 10036, New York
United States
Email: info.us@awingu.com

Awingu Inc.
620 Davis Street,
CA 94111, San Francisco
United States