To provision and deploy resources in Microsoft Azure correctly, you need the following:

• An Azure account.
• An Azure subscription.
• An Azure Active Directory global administrator account in the directory associated with your subscription. The user account must have Owner permission for the Azure subscription to use for provisioning resources.

For more information about how to set up an Azure Active Directory tenant, see How to get an Azure Active Directory tenant on the Microsoft website.

• Use the Azure Resource Manager to:
  • Deploy resources such as virtual machines, storage accounts, database, and virtual network.
  • Create and manage the resource group that is a container for resources you want to manage as a group.

XenApp Essentials supports the following web browsers:

• Google Chrome
• Internet Explorer

Users connect to their apps by logging on with Citrix Receiver. XenApp Essentials Service supports the current version of Citrix Receiver for each user device operating system.

You can download the latest version of Citrix Receiver from the Citrix website.

Citrix Cloud hosts the XenApp Essentials Service. The XenApp Essentials offers secure access to virtual Windows apps. This service is based on XenApp and XenDesktop technology. The service includes StoreFront and the NetScaler Gateway Service along with core management services.

Your app workloads run in your Azure subscription.

The following diagram shows an architectural overview of a basic XenApp Essentials Service cloud deployment:

You can also allow users to connect to your on-premises data center. Connections between the Azure cloud and your on-premise data center occur through a VPN connection. Users connect through XenApp Essentials to your license server, file servers, or Active Directory over the VPN connection.

The XenApp Essentials Service has the following known issues:

• Creating the machine catalog fails if the virtual machine size is not available for the selected region. To check the virtual machines that are available in your area, see the chart at Products available by region on the Microsoft website.
• You cannot create and publish multiple instances of the same app from the Start menu at the same time.
  For example, from the Start menu you publish Internet Explorer. Then, you want to publish a second instance of Internet Explorer that opens a specific website on startup. To do so, publish the second app by using the path for the app instead of the Start menu.
• XenApp Essentials Service supports linking a subscription by using an Azure Active Directory user account. XenApp Essentials does not support Live.com authenticated accounts.
• Users cannot start an application if there is an existing Remote Desktop Protocol (RDP) session on the VDA. This behavior only happens if the RDP session starts when no other users are logged on to the VDA.
• You cannot enter a license server address longer than server.domain.subdomain.
• If you perform multiple sequential updates to capacity management, there is a possibility that the updated settings will not properly propagate to the VDAs.

Perform the following tasks in Microsoft Azure before setting up the connection in Citrix Cloud:

1. Create an Azure subscription.
2. Create a user in Azure Active Directory who is a global administrator for the subscription.

After you create your Azure account, you can prepare your Azure subscription.

When you prepare your Azure subscription, you configure the following:

• Create a resource group and provide the following details:
  • Resource Group name
  • Subscription name
  • Location
• Create a virtual network in the resource group and provide a name for the network. You can leave all other default settings.
• Create a when you create the master image.
  Note: A premium storage account is not supported.
• Use an existing or create a domain controller. If you create a domain controller, do the following:
  • Use the A3 Standard or any other size Windows Server 2012 R2 virtual in the Resource Group and virtual network. This virtual machine becomes the domain controller. If you plan to create multiple domain controllers, create an availability set and put all the domain controllers in this set.
  • Assign a private static IP address to the network adapter of the virtual machine. You can assign the address in the Azure portal. For more information, see Configure private IP addresses for a virtual machine using the Azure portal on the Microsoft documentation website.
  • [Optional] Attach a new data disk to the virtual machine to store the Active Directory users and Groups and any Active Directory logs. For more information, see How to attach a data disk to a Windows virtual machine in the Azure portal. When you attach the disk, select all the default options to complete the wizard.
  • Add the domain controller virtual machines private IP address to the virtual network DNS server. For more information, see Manage DNS servers used by a virtual network (Classic) using the Azure portal (Classic).
  • Add a public DNS server in addition to the Microsoft DNS server. Use the IP address 168.63.129.16 for the second DNS server.
  • Add the Active Directory Domain Services role to the domain controller virtual machine. When this step is complete, promote the domain controller virtual machine to a domain controller and DNS.
  • Create a forest and add some Active Directory users. For more information, see Install a new Active Directory forest on an Azure virtual network.

If you prefer to use Azure Active Directory Domain Services instead of a domain controller, use the following guidelines. Citrix recommends reviewing the Active Directory Domain Services Documentation on the Microsoft website.

• Create an Azure Active Directory and give it a unique name.
• Create a classic virtual network to enable Domain Services.
  When you create the classic virtual network, choose an IP address range that is different from the one you use with the XenApp and XenDesktop Service. You need two IP addresses and can use the /24 range.
• Enable the Azure Active Directory Domain Services by switching to the classic portal. Navigate to the Active Directory node and open the new Azure Active Directory domain.
• Enable the domain services for the directory.
  When you complete this step, the DNS name and virtual network appear automatically. Ensure that the values are correct.
  When you save the settings, it can take 30 minutes to an hour to set up Domain Services.
• When provisioning Domain Services is complete, a new section titled IP ADDRESS appears. Refresh the page until you see two IP addresses.
• Add a subnet IP address for the Azure virtual network.
• Update the DNS settings for the Azure virtual network.
  Edit the properties on the virtual network. Ensure that you enter both IP addresses created in a previous step.
• Create an administrative group in the new Azure Active Directory domain. Use the following guidelines:
  • Create the group with the name AAD DC Administrators. The group must have this name.
  • Configure the DNS settings before adding users and groups.
  • Add members after creating the group.
• Create a Resource Manager virtual network. Ensure that the deployment model you use is set to Resource Manager. Locate the Resource Manager virtual network in the same region as the classic virtual network.
• Peer the Resource Manager virtual network to the classic virtual network. Peering connects the two virtual networks to the same region in Azure. After peering the networks, the two networks appear as a single virtual network. When you peer the two networks, ensure that you select the classic virtual network.
• Add DNS servers to the Resource Manager virtual network. When you configure the DNS servers, type the IP address of the Azure Active Directory Services. Ensure that you type both IP addresses that appear in the Domain Services section on the Configure tab of your directory.

You can use one of the following two images in your deployment:

• Your own master image with your applications installed.
• A Citrix-prepared image.

When you prepare the master image, the Virtual Delivery Agent (VDA) installs on the image automatically. The VDA software enables the following:

• Registers the machine with the XenApp Essentials Service.
• Establishes and manages the connection between the machine and the user device.
• Verifies that a Citrix license is available for the user or session.
• Applies any configured policies for the session.
• Communicates session information to the XenApp and XenDesktop Service through the broker agent included in the VDA.

VDAs are available for Windows server and desktop operating systems. VDAs for Windows Server operating systems allow multiple users to connect to the server at one time.

For more information, see Configure VDAs.

You create the master image by using the Azure Resource Manager. When you prepare your master image, the steps you must take in the Azure portal are:

1. Log on to the Azure portal.
2. Create a Windows Server 2012 R2 or Windows 2016 server virtual machine.
   You can also use existing server virtual machines. When you use existing machines, you can use the resource group, virtual network, and storage account associated with the machine. The storage account is where you create the virtual hard disk (VHD).
   Note: Create the VDA template with standard (non SSD) storage. Also, do not join the VDA to a domain.
3. Connect to the virtual machine after you create it and when it is running.
   Important: Do not run Sysprep on the image.
4. Install the applications on the virtual machine. The apps are available to your users when they log on with Citrix Receiver.
5. Download the server OS VDA on the virtual machine from the XenApp and XenDesktop Service download page.
6. Install the VDA on the virtual machine. When prompted for the Delivery Controller address, select Let MCS configure.
7. Skip the installation of Citrix Receiver and App-V. Use the default settings for the remainder of the configuration steps.
8. Restart the VDA and complete the VDA installation steps by following the instructions on the page.
9. Test starting the applications to ensure that the configuration is correct.
10. Shut down the virtual machine.

When you create the virtual machine, the VHD is created in the storage account you specified. When you upload the master image, you must specify the storage account location in the XenApp Essentials console.

In the Citrix Cloud, you link your XenApp Essentials Service to your Azure subscription.

To link your Azure subscription

1. Log on to the Citrix Cloud for XenApp Essentials Service.
2. On the Manage tab, click Subscriptions.
3. Click +Add Subscription.
   The Azure portal opens.
4. Log on to your Azure subscription by using your global administrator Azure credentials.
5. Click Accept to allow XenApp Essentials Service to access your Azure account.
   XenApp Essentials service enumerates the subscriptions available in your account.
6. Select the subscription you want to use and then click Link.
   Return to the XenApp Essentials Console to see the subscription in a linked state.

After you link your Azure subscription to XenApp Essentials, upload your master image.

To upload the master image

1. Log on to the Citrix Cloud for the XenApp Essentials Service.
2. On the Manage tab, click Master Images.
3. Click Add Image.
   The Add an image page opens.
4. Specify the location of the VHD by selecting the following:
   1. Subscription
   2. Resource group
   3. Storage account
   4. VHD location
   5. Region
   6. Name for the master image.
5. Click Save.
   When you save the image, XenApp Essentials Service verifies the master image.
   After verification, the image appears on the Master Images > My Images page.

A catalog is similar to collections in Azure Remote App. A Citrix XenApp Essentials Service catalog lists apps and resources that you can share with users on any device.

XenApp Essentials Service catalog uses a simpler approach to the combination of a machine catalog and a Delivery Group.

When you add a catalog, you configure the following:

• Create a name for the catalog.
• Link your Azure subscription to the catalog.
• Join the catalog to the domain.
• Choose a master image.
• Select the capacity and manage the cost of the apps.

Before you start creating your catalog, ensure that you have your Azure Active Directory credentials and your subscription ID available.

To create a catalog

1. Log on to citrix.cloud.com.
2. Select the XenApp and XenDesktop Service.
3. On the Manage tab, click Catalogs, and then click +Catalog.
4. On the Add a Catalog page, in Pick a Name, type the name of the catalog, select Domain Joined, and then click Save.
5. In Link your Azure subscription, provide your Azure subscription details. You can use a subscription you created previously or link a new Azure subscription. To use an existing subscription, do the following:
   1. In Subscription Name, select the subscription from the list.
   2. In Resource Group (Region), select the resource group to which the Azure subscription belongs. Use the resource group you created when you prepared your Azure subscription. XenApp Essentials Service creates Cloud Connectors in the resource group.
   3. In Virtual Network, select the virtual network to which the Azure subscription belongs.
      The virtual network is the same one you configured when you prepared your Azure subscription. Ensure that the virtual network can reach your domain controller by using the DNS entries
   4. In Subnet, select the subnet to which the Azure subscription belongs and then click Save.
6. Under Join local domain, enter the following:
   1. In Fully Qualified Domain Name, type your organizations domain name.
   2. In Organizational Unit, type the OU to which users belong.
      For example, OU=Essentials,DC=citrix,DC=com.
      Note: Adding the OU is an optional step.
   3. In Service Account Name, type the account that by using permissions to join a machine to a domain and create machine accounts.
   4. In Password and Confirm Password, type the password and then click Save.
7. In Choose master image, do one of the following:
   1. Select Link an existing image and then do the following:
      1. In Image Name, select the image.
      2. Click Save.
   2. Select Import a new image and then do the following:
      1. In Subscription, choose the subscription.
      2. In Resource Group, choose the group.
      3. In Storage Account, choose the account
      4. In VHD, choose the location of the virtual hard disk.
      5. In Image Name, provide a name for the master image and then click Save.
8. In Select Capacity and Manage Cost, do the following:
   1. In Pick compute, select a worker role.
      The worker role defines the resources used. When you specify a worker role, XenApp Essentials Service determines the correct load per instance for you. You can use one of the options in the list or create your own custom option. The session count is used as a scale metric.
   2. In Select scale settings, do the following:
      1. Set the minimum number of running instances. XenApp Essentials Service ensures that the minimum of virtual machines are powered on all the time.
      2. Set the maximum number of running instances. XenApp Essentials Service does not go beyond this number of virtual machines.
      3. [Optional] If you want a different number of virtual machines running during peak times, select I want to set a schedule for peak time. Then, specify the following:
      • Days of the week for the peak time
      • Start and end times for each day
      • Time zone
      • Minimum number of running instances
9. In Set idle or disconnected session time-out, set the time for when the session ends.
   User sessions end automatically if the session remains idle or is disconnected for the specified time period. Shorter time-out values allow unused VDAs to power off and save costs.
10. Click Save.

After you configure your catalog, click Start Deployment to start catalog creation. This step can take 1-2 hours. If you specified many virtual machines, creating the catalog can take a longer time.

When the previous step is complete, you can publish apps and assign users and user groups. You need at least one published application and one user assigned to complete creating the catalog.

To update or add applications, update the virtual machine that you used to create the catalogs master image.

To update the master image

1. Power on the master image virtual machine.
   Powering on the virtual machine does not affect the master image installed in Microsoft Azure.
2. Install any updates or applications to the virtual machine.
3. After installation, shut down the virtual machine.
4. In the XenApp Essentials Service console, add the new image that includes the path to the virtual machines VHD image.

To update a catalog

1. On the Manage tab, click Catalogs.
2. Click the ellipsis in the catalog that you want to update, and then click Update Catalog Image.
3. Select either Link an existing image or Import a new image. Enter the information that is appropriate for your choice.
4. In Time until automatic log-off, choose the amount of time before the session ends.
   When you start the update of the master image, users can continue to work in XenApp Essentials until the processing is complete. Then, users receive a warning message to save their work and close applications. After closing all active sessions on the VDA, the update finishes on that VDA. Then, if users do not log off in the amount of time given, the session closes automatically.
5. Click Update to start updating the master image.

After configuring your catalog, you can publish apps for your users. The image you installed includes apps that you can publish.

To publish apps

1. Log on to the Citrix Cloud for the XenApp Essentials Service.
2. On the Manage tab, click Catalogs.
3. Click the ellipsis in the catalog for which you want to publish apps.
4. Click Manage Publishing.
5. On the Apps tab, click Publish Apps.
6. In the Publish Apps for <catalog name> page, select the apps for publishing.
7. When done, click Publish.
   The Apps tab appears by using the list of published apps.

After you publish apps, you can add users and groups.

1. Log on to the Citrix Cloud for XenApp Essentials Service.
2. On the Manage tab, click Catalogs.
3. Click the ellipsis in the catalog for which you want to add users.
4. Click Manage Users.
5. On the Users tab, click +Add Users.
6. In the Assign Users for <catalog name> page, in Domain, choose the domain.
7. In the search box, type the name of the user or user group.
8. Repeat step 7 until you’ve added all users and groups.
9. Click Assign Users.
   The Users tab appears by using the list of published apps.

The XenApp Essentials Service in Citrix Cloud hosts a StoreFront site for each customer. After you create the catalog, the StoreFront site is created automatically. The StoreFront URL appears under the catalog details. Hosting StoreFront in the cloud means that you do not have to deploy or maintain StoreFront. Citrix keeps StoreFront current in the cloud.

To allow users secure access to their published apps, XenApp Essentials Service uses NetScaler Gateway Service. This service does not need any configuration by you. Each user is limited to 1-GB outbound data transfer per month. You can purchase a 25 GB add-on from the Azure Marketplace. The charge for the add-on is on a monthly basis.

To monitor the overall performance of the Citrix XenApp Essentials Service for Azure, do the following:

1. Navigate to the XenApp and XenDesktop Service.
2. Click the Monitor tab.
3. Click the Catalog that you want to monitor.
   You can view information on sessions, logon duration, in addition to other information.
4. You can choose a session and do the following tasks:
   1. Disconnect the session.
   2. Log off from the session.
   3. Send a message

You can click each session to view extra details about the session such as processes, applications running, and more.

If you have problems with XenApp Essentials Service, open a ticket by following instructions in How to Get Help and Support.

XenApp feature comparison