Azure Quick Deploy
The Azure Quick Deploy feature is deprecated, but will remain available for a short time. Instead, use the new Quick Deploy feature now by selecting Manage > Quick Deploy.
In the Citrix Virtual Apps and Desktops service, if your resource location uses Azure Resource Manager machines to deliver applications and published desktops, you can choose a deployment method:
- Full Configuration: The Full Configuration option uses the Studio management console, which guides you through creating a machine catalog and then creating a delivery group. This deployment method offers advanced configuration features. This method can be used for any supported host type.
- Azure Quick Deploy: The Azure Quick Deploy option provides a simpler interface that offers faster deployment of apps and desktops. This deployment method offers basic configuration, without advanced features. This method is valid only when using Azure Resource Manager as your host.
Azure Quick Deploy offers a quick way to set up a proof of concept environment or to get started with Citrix Virtual Apps and Desktops service when using Azure Resource Manager.
If you are familiar with using Studio to deploy catalogs (either in on-premises Citrix Virtual Apps and Desktops, or Citrix Virtual Apps and Desktops service Full Configuration), there are some differences.
- Azure Quick Deploy uses different terminology: you create a catalog. In Full Configuration (Studio), you create a machine catalog.
- Azure Quick Deploy automatically creates server VMs and installs two Cloud Connectors in your resource location. In Full Configuration, these are separate steps you must complete before creating a catalog.
- Azure Quick Deploy does not use delivery groups. In Azure Quick Deploy, you configure all the deployment items in the catalog: the catalog, machines, applications, desktops, and subscribers. (A delivery group is automatically created for each Azure Quick Deploy catalog (using the same name as the catalog), but that action occurs behind the scenes. There is no required customer administrator action.)
- The Azure Quick Deploy interface has a different layout and style. There is more on-screen guidance.
The following graphic and table compare the deployment methods.
|Feature||Azure Quick Deploy||Full Configuration|
|Deploy||Deploy to Azure||Yes||Yes|
|Deploy to Amazon Web Services and Google Cloud||No||Yes|
|Deploy to on-premises hypervisors||No||Yes|
|Deliver||Deliver Windows apps||Yes||Yes|
|Deliver multi-session OS desktops||Yes||Yes|
|Deliver Linux apps/desktops||No||Yes|
|Deliver single-session OS desktops||No||Yes|
|User experience||Remote PC Access||No||Yes|
|Simplified user experience||Yes||No|
If you are familiar with Citrix Virtual Apps Essentials service, the Azure Quick Deploy interface is similar. It is easy to use, especially if you’re not familiar with Studio.
The deployment methods are not mutually exclusive. You can use one method to create some resources, and then use the other method to create more resources. However, where you edit a catalog can have effects; see Editing Azure Quick Deploy catalogs.
Catalogs that are created using Azure Quick Deploy are visible in both the Azure Quick Deploy display and in Studio.
Machine catalogs that are created originally in Studio are not visible in the Azure Quick Deploy display.
- Azure Quick Deploy is available only when using Azure Resource Manager as your host. It is not available with any other host types.
- Azure Quick Deploy is available only in the Citrix Virtual Apps and Desktops service and the Citrix Virtual Apps service. It is not offered in the Citrix Virtual Desktops service.
- Azure Quick Deploy delivers Windows multi-session OS machines. You cannot use it to deploy single-session OS machines.
- You must be a full administrator to see both deployment options. If you are not a full admin, you won’t see the Azure Quick Deploy option, and will automatically use Full Configuration.
- See the Important note in editing Azure Quick Deploy catalogs.
Citrix Gateway consideration
If you use your own Citrix Gateway, it must have access to the VNET specified in the catalog creation wizard. A VPN can provide that access.
Alternatively, the Citrix Gateway Service works automatically with Azure Quick Deploy catalogs.
Editing Azure Quick Deploy catalogs
After you deploy a catalog using Azure Quick Deploy, it appears in the Quick Deploy Catalogs category on the Manage > Catalogs screen. You can use the ellipsis menu on a catalog’s row to select the following actions:
- Add or remove apps
- Add or remove subscribers
- Change capacity
- Select a different master image
- Delete the catalog
You can also use Studio to edit a catalog deployed with Azure Quick Deploy. However, if you use Studio to change that catalog or its corresponding delivery group, you will no longer be able to edit that catalog from the Azure Quick Deploy interface (Manage > Catalogs). The catalog will still be listed in Manage > Catalogs, but it can no longer be managed or deleted there.
Use Azure Quick Deploy
The Azure Quick Deploy sequence is essentially the same as the Citrix Virtual Apps Essentials service deployment interface.
Most of the guidance is available in the Citrix Virtual Apps Essentials service article. (In that article, disregard information about how to buy and cancel the service.)
Begin in the Create a catalog section, substituting the following procedure for step 2.
Click Catalogs (if it’s not already selected). Select Manage > Azure Quick Deploy. Click Create a Catalog.
Follow the procedures for creating a catalog.
Follow the procedures for publishing apps and assigning subscribers for a catalog.
When you’ve successfully completed those steps, share the Workspace URL with your subscribers. For more information, see Launch applications and desktops.