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.

Basics

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.