at Citrix Synergy 2016, Citrix plans as sure the Microsoft company, cloud deepen and embrace mobility platforms, expansion and our long-standing partnership.
in the context of this strategy on the provision of support for Microsoft Azure Resource Manager (ARM) is now in the XenApp and XenDesktop service on Citrix Cloud available. Now you can provision, de-provision, and performance manage XenApp and XenDesktop VDAS on Microsoft Azure right of the Citrix Studio console. All you need to bring to the table, is your Azure subscription and a Golden Master VDA image - we will manage the rest for you
Today, I will give you a brief introduction to ARM and some go. Key distinctions that you need to be between Azure and Classic ARM aware if the provision on ARM to Citrix Studio.
What is ARM?
Back in 08, Microsoft's vision for Azure turned Platform Services (PaaS) specifically to create developer primarily stateless .NET applications that could scale easily and automatically down. But the amazing growth of pure play IaaS Microsoft has been forced to rethink their cloud strategy because Azure PaaS VMs were deeply rooted in the foundation of cloud services, making it difficult and for them, to the underlying computing, storage network provider for innovation. In combination with the competitive pressures of Amazon and Google, Microsoft has been forced to go back the drawing board.
The result of this exercise was an IaaS platform designed thoughtfully for the future called Azure Resource Manager . or ARM for short
Here are some key features of ARM are:
- Logical grouping of an associated set of resources (compute, network and storage) as a unit, the is called a resource group. This will contain a convenient contextual limit for use, cancellation and settlement of resources in it.
- All on Azure Resource Manager resources must first be authenticated with Azure Active Directory (AAD) of the tasks that you do.
- The ability to use templates declarative JSON to describe the resource with the provision and dependencies between them. In fact, behind the XenApp Programmes in Azure marketplace an extensible ARM template. ARM templates are also compatible with Azure Stack .
- Just like you can mark your credit card transactions, ARM allows you to use tags to easily organize resources. This makes it ideal for multi-department billing.
ARM support in Desktop Studio
There are a few important areas that you need to be aware of when the provision on ARM from Studio.
host connection type
soon you get a new host connection type from the drop-down list called Microsoft Azure see notice -. this arm is
Azure AD-based authentication
As discussed above, ARM Azure AD used for authentication. Each Azure subscription is connected to a single Azure AD tenant that governs authentication to resources within this subscription. You need a user account within that to define tenants and assign Service Administrator role for this user for the subscription. They are now considered to be prompted for authentication for the administrator to Azure AD, and once successfully authenticated, you will be offer requested a one-time permission to create a service principal whose identity XenDesktop is then actions use as VDAS perform provisioning on your name.
Master image selection
Another area where ARM is different from Azure Classic, is the way users images be treated.
create your golden master VDA front image of a in Azure Gallery Picture of Windows Server 2012 R2 as you would. But unlike Azure Classic, where you need to first take the picture, VM user would be recorded as images through the portal images in ARM. But it's also now easier. Why not come (and de-allocation) to the master VM. In the studio, navigate to the VHD, which is the OS disk that VM (we do not support provisioning machines with additional data sheets)
. Note: your base image in a memory residing in each account Azure Region -. we is in the host connection it do the hard work over specified to the target region of copying (where you will be provided your VDAS want)
, the next blog series
While this is an introductory blog post, looking forward to an upcoming multipart technical blog series that will delve into specific topics related to our ARM support as authentication, image creation, creation and updating of catalogs, troubleshooting, etc.
As always, I look forward to your comments and suggestions.
This comment has been removed by the author.
ReplyDelete