Deploy XenDesktop/XenDesktop POC to Microsoft Azure with Lifecycle Management

Marcel Otto's picture

In the following Article, I would like to provide a "step-by-step" Installation Guide for a Lifecycle Management Blueprint in Citrix Workspace Cloud.

Some useful Information first:


What is Lifecycle Management?

  • Citrix Workspace Cloud provides 4 Services:
  • Application and Desktops (as you can guess, that is XenApp/XenDesktop)
  • Mobility Management (XenMobile)
  • Secure Documents (Sharefile)
  • Lifecycle Management (LCM) 

LCM is used as a platform to deploy and configure the lifecycle of Citrix applications on Hypervisors, as well as public and private Cloud platforms.

LCM platform contains a workflow automation engine (Orchestration), Monitoring and Brokering capabilities.

Deploying Blueprints is a feature in Citrix Lifecycle Management.


What is a Blueprint?

A Blueprint is a template that contains information about a deployment workflow.
A Blueprint may contain Software machine configurations or platform components.


Citrix offers some pre-configured Blueprints in a Blueprint catalog.

LCM also provides a Blueprint Designer, that allows to view or customize Blueprints, add scripts and create your own Blueprints.

Before we start to log into Workspace Cloud, let’s perform some preparation in Azure.

Prepare Azure Environment

1.1 Create Azure Subscription
1.2 Create Azure Network
1.3 Create Azure Cloud Service
1.4 Create Azure Storage

1.1 Creating Azure Subscription

If you don’t have one, you can create a Subscription in Azure. Microsoft gives you some  funds you can start with.

In case you have already got one proceed with Step 2.

Once you have created your subscription, you can log in to:



Bevor we start deploying our POC, we have to prepare Storage, Network and Cloud Service in Azure.

Create Azure Network

Create Azure Cloud Service

Create Azure Storage

Prepare Lifecycle Management

2.1 Add Ressource Location
2.2 Add Blueprint
2.3 Deploy Blueprint

Log in to

Once you have logged in, you will see all services that are available.

Deploying Blueprints is a functionality within Lifecycle Management.


Add Ressource Location

Depending on your business needs you can choose a Resource Location to deploy your Blueprint to.

That location may be a public or private cloud, a branch office, or a data center.
As you can see, I have already deployed a Blueprint to Hyper-V Server and another one to the Elastic Compute Cloud (EC2). 

Let me show you, how to add your Azure Subscription as a Resource Location to Workspace Cloud:

Please type in a name that describes your Account.

To upload your certificate, please be sure, that you are already signed in to azure.

If you have already signed in, a pop-up window showing your subscription file opens up.


Add Blueprint

Now choose "XenApp and XenDesktop Proof of Concept" and add it to your library.

Design & Deploy

Once we have added the Blueprint it shows up in the library called “Design & Deploy”. Here we find  the Blueprint Designer which allows to create our deployment.

We can also create new Blueprints and scripts, as well as view and edit the existing Blueprint with all the scripts that are delivered.

Before we start with our deployment let’s have a look at the details the Blueprint comes with:

Click "View"

In fact, the most interesting part of the Blueprint is the workflow process.

As you can see the whole orchestration is displayed.

If you want you can even get into all the nice details.

For example, the deployment script for the XenDesktop Installation:

Citrix does not hide important information about the deployment scripts. That’s awesome!

Let‘s quit the Designer 


Deploy Blueprint

Click "Deploy" to start deploying the Blueprint.

Start the deployment setup.

Choose a name for the Deployment.
Leave "Deployment profile" empty.
As mentioned above you start configuring your deployment profile in the next steps.
If you want, you can eventually save it for future deployments.

Choose your Resource Location

Take notice of all the recommendations and prerequisites.

We have to configure each VM individually.

If you want to use your own Template, choose it here.
If you need information on preparing a VM Template, have a look here:
If you have already added a Template, but you can’t see it here, please make sure you have added it to the Gallery earlier:
For my POC I decided to use the Images provided by Azure Gallery

I use the preconfigured Name and Machine recommendations and choose Azure Cloud Service and Azure Storage we have created earlier.

Enter username and password you want to use for the administrator account.

Now we are provided with a summary to review our configuration.

Repeat the steps for the Delivery Controller and the VDA.
I use the same admin account for all the servers.

Now all my machines are ready to go.

Enter all details and please take notice of the "Administrator Account" Help- Description.
As described I use my administrator Account created earlier.

Now save your deployment settings.

Review your settings again and deploy your POC to Azure.

Monitor the progress of your deployment.

In my case the whole process took about 3 and a half hours

After the break we make sure all instances are created successfully.


Test Deployment

Now, let’s check if we can work with our POC:
Log in to the Delivery Controller and open Citrix Studio.
There is a Machine Catalog with one machine allocated.

And there is a Delivery Group – Delivery Type “Desktops”.

There is a store as well.

Let’s confirm our Desktop can be launched successfully.
To do so, I log on to my VDA, launch IE and browse to my WebStore.

Et Voila!
You have successfully deployed your POC

Have fun and stay tuned with Workspace Cloud!

Hi Marcel,
Hi Marcel, interessehalber, läuft das auch mit ARM oder nur ASM?
Vancouver Real Estate House
thanks for this awesome post
Add new comment
By submitting this form, you accept the Mollom privacy policy.