CloudBursting XenApp / XenDesktop in Azure 1/2

· 5 min read
CloudBursting XenApp / XenDesktop in Azure 1/2

Being able to extend your existing infrastructure to a cloud provider is a great option if you need more power for a specific period. In a previous blog (XenApp on Azure, is it really that easy ?) I show you how to have a fully existing infrastructure, fully hosted in Azure, in few click and very quick. But, this is a random infrastructure, nothing to do with your existing one and nearly impossible to adapt it and link it to be able to use it like it was a part of your company environment.

In Studio (XenApp / XenDesktop administrator console)  it is possible to create an Hosting link to Microsoft Azure. So here is how to proceed using the GUI in Studio. I will use Windows 10 Enterprise vhd I preconfigured in Azure with a VDA installed. Keep in mind that would be the same with a XenApp server 2008R2 / 2012R2 or 2016.

First in Studio, go to the Configuration node and the Hosting, right click and chose Add Connection and Resources :

The wizard is opening and the setup is pretty straight forward, create a new connexion by chosing Microsoft Azure the click on Next

Enter you Azure Subscription ID and give a name to this connection, click on Create new…

The a web pop-up should appear, you need to use the account linked to your Azure Subscription ID, click on Connect

I had few issue having this pop-up displaying, there is a time-out who can occur and throw an exception in the wizard, you just need to try again.

Once everything has been verified, a green check appear with Connected, then you can click on Next

The Azure Region need to be chosen, the click on Next

Give a name for these Resources and click on Next

The Summary is displaying before making the final change and save it to XenApp / XenDesktop database, Click on Finish

Now you can see a new Hosting Connection and Resources added to it.

Now this is done, it means in Studio, we can use this Hosting connection and create a Machine Catalog (MCS).

Go in Studio and right click on Machin Catalog to create a new one :

The wizard is opening, first windows is the introduction to catalog creation, you can skip it and go to the next

As I chose to deploy Windows 10 Enterprise, my choice will be Desktop OS here, you can do the same with Server OS and Windows 2008R2 / 2012R2 / 2016, click Next

Machine will be powered managed and deployed using Citrix Machine Creation Services with the Resources we created at the beginning of this blog, click Next

Chose the way you want to manage your user’s desktops, click Next

Then, browse until the vhd of the VM you prepared. This is fairly easy for me as I just began to fill my Azure subscription with stuffs, but with this kind of name scheme, if you already have many, you need to go to your Azure portal and check these information on the VM properties, click Next

You need to be sure you VM is properly shutdown and the Close.

Next you need to chose the Storage and the licensing of your VMs, click Next

Chose the number of VM you wish to create, the VM type you see the best for your workload, I chose the Standard_D2_v2 :

Then click Next

Chose the Network Interface available, or the one you want to use if you have several already configured in Azure, click Next

Chose the OU where the Computer account will be created and the naming scheme, then click Next

Give a name to your Machine Catalog and you’re ready to go, click on Finish

Now the Machine creation begin. It took some time to create the 26 VMs, I found it quiet long, I would need to check what was the real time the next time I will create some VM again.

At the end, the Machine Catalog is ready with the freshly created VMs in Azure in it :


Next blog about Azure stuffs with XenDesktop and XenApp will be to create a Delivery Group and deliver these VM from Azure. I would like to go further more and define some trigger when these VMs should be fired up (DR scenario)

Also, I want to check how Citrix Smart Tools (ex Lifecycle Management) can interact with Azure on my on-prem infrastructure.