Deploy the XenApp and XenDesktop Proof of Concept blueprint on Microsoft Azure Classic

This topic describes how to deploy the XenApp and XenDesktop Proof of Concept blueprint to a Microsoft Azure Classic resource location. 

Contents

What does this blueprint do?

When you deploy this blueprint, Smart Tools performs the following tasks:

  • Provision a domain controller and creates a domain
  • Provision machines for the XenApp and XenDesktop Delivery Controller and Server VDA and joins them to the domain
  • Install XenApp and XenDesktop and creates a database and Site
  • Provision a virtual desktop that you can access for testing purposes

Note: Although the blueprint includes the option to deploy a NetScaler Gateway, this topic covers deploying only the domain controller, Delivery Controller, and Server VDA.

Provisioned machine configurations

The blueprint includes recommended configurations for each machine that Smart Tools provisions to the deployment. The following Azure machine sizes are the default selections when you configure the VM for each machine tier in the deployment:

Operating system: Windows Server 2012 R2 Datacenter Edition (all machines)

Machine Type Azure Machine Size
Domain controller A2 (2 Core, 3.5 GB Memory)
Delivery Controller A3 (4 Core, 7 GB Memory)
Server VDA A2 (2 Core, 3.5 GB Memory)

Important: This blueprint includes conditions for deploying the components above on supported resource locations. When configuring the VMs for each machine tier, you must allow Smart Tools to provision new VMs during deployment. Using existing machines with this blueprint is not supported and will cause the deployment to fail.

Back to top

Prerequisites

In addition to your Smart Tools account, you will need an Azure account to perform the tasks described in this topic. If you don't have an Azure account, you can create one at http://azure.microsoft.com.

To perform the tasks in this topic with minimal interruption, Citrix recommends you perform the following actions in Smart Tools beforehand:

  • Add your Azure account to your Smart Tools account as a resource location. To do this, follow the steps described in Add a Microsoft Azure Classic resource location.
  • Add the XenApp and XenDesktop Proof of Concept blueprint in the Blueprint Catalog to your Smart Tools account.

Back to top

Step 1: Create a cloud service

  1. Log on to the Azure portal at https://portal.azure.com.
  2. Click Browse All, click Cloud Services, and then click Add. Enter the following information:
    • In DNS name, type the DNS name for the service.
    • In Resource group, select the resource group you want to use for the service.
    • In Location, select the region where you want to deploy the blueprint.

      clm-azure-cloud-svc-add.png
  3. Click Create and wait for Azure to finish provisioning the cloud service before proceeding to the next step.

Afterward, the Azure portal displays a notification indicating the cloud service was successfully created.

Back to top

Step 2: Deploy the XenApp and XenDesktop Proof of Concept blueprint

  1. Log on to Citrix Smart Tools. 
  2. From the menu bar, click Blueprint Catalog and add the XenApp and XenDesktop Proof of Concept blueprint to your account.
  3. Click Smart Build, point to the blueprint and click Actions > Deploy, then click Start deployment setup
  4. On the Overview page, enter a Deployment Name and then click Next.
  5. On the Resource Location page, select your Azure Classic resource location and then click Next.
  6. On the Architecture page, in Configure NetScaler, select no (default).
  7. On the Pre-deployment Checklist, click Continue
  8. On the Scale page, click Next.
  9. On the Size page, ensure Create new VMs is selected.
  10. For the Domain Controller machine tier, perform the following actions: 
    1. Select your Azure resource location to configure the VM that Smart Tools will provision. The Configure VM dialog box appears.
    2. Select the most recent Windows Server 2012 R2 Datacenter machine image listed.
    3. On the Instance Details page, select the following settings and then click Next:
      • In Machine Size, select the appropriate machine configuration. By default, the machine size listed in the Recommended Configuration box is selected.
      • In Virtual Network, select the virtual network you want to use or create a new one. To create a new virtual network, click Create virtual network and subnet and enter a Virtual Network Name and a Subnet Name. Click Create Virtual Network.

        Note: Virtual Network names must start with a letter and end with a letter, number, or underscore. Both Virtual Network and Subnet names can contain only letters, numbers, underscores, periods, and hyphens.
      • In Cloud Service, select the cloud service you created in “Step 1: Create a cloud service.” The Location associated with the service is automatically selected.
      • In Storage Account, if you have an existing Azure storage account associated with the region of your cloud service, it will be automatically selected. If you want to create a new storage account for the cloud service or you don't have an existing storage account, leave the default value Auto Generate Store Account. Autogenerated storage account names begin with "random" and are followed by a randomly generated alphanumeric string.
    4. On the Security and Network page, enter the Username and Password you want to use for the Administrator account and then click Next.

      Important: Do not use "Administrator" or "Admin" as the username for these VMs. As a security best practice, Azure requires distinct usernames for administrator accounts. 
    5. On the Summary page, leave Copy this configuration to other VM tiers selected and then click Finish. Copying the configuration enables you to quickly configure the remaining VMs with the same OS, cloud service, network, and storage settings. 
  11. On the Size page, click Next to continue the deployment.
  12. On the Configuration page, enter the following settings and then click Next:
    • In DomainName, enter a fully-qualified domain name for your proof-of-concept deployment.
    • In SafeModePassword, enter a password to allow administrators to repair Active Directory in safe mode. 
  13. (Optional) Enter a deployment profile name and then click Save to save your blueprint deployment settings. Otherwise, click Cancel.
  14. Click Deploy to deploy the XenApp and XenDesktop Proof of Concept blueprint to your Azure account.

After the deployment begins, Smart Tools displays the status of the deployment in the Deployment Details page. The Deployment Details page includes the real-time progress of each step in your blueprint. Depending on machine availability and the complexity of the blueprint, the deployment might take some time to complete, and some blueprint steps might take longer than others.

During deployment, Smart Tools sends you email notifications when each machine in the blueprint is successfully provisioned. When the deployment is finished, Smart Tools sends you a final email notification. 

Back to top

(Optional) Tear down the deployment

When you tear down your proof-of-concept deployment, Smart Tools removes the following resources from your Azure Classic resource location:

  • Domain controller, Delivery Controller, and Server VDA machines 
  • Cloud service associated with the deployment

Deployment resources that remain in your resource location are:

  • Storage accounts
  • Virtual hard disks (VHDs) associated with the storage accounts used for the deployment

For more information about initiating a teardown, see Tear down a deployment.

Remove virtual disks from storage accounts

When Smart Tools provisions new virtual machines from the blueprint, a virtual disk is created for each machine and associated with the storage account for the deployment. Before you can delete the storage account from your resource location, you must first delete these virtual disks. 

  1. Log on to the Azure management portal at http://manage.windowsazure.com.
  2. Click Virtual Machines and then click Disks. 
  3. Select the virtual disk you want to delete. The name of each virtual disk follows the convention CloudServiceName-VMName-UniqueID.
  4. Click Delete and then click Delete the associated VHD.
  5. When prompted to confirm the deletion, click Yes.

0 Comments