Citrix Virtual Apps and Desktops service

Quick Deploy

Introduction

Quick Deploy offers a quick way to get started with the Citrix Virtual Apps and Desktops service.

In the Citrix Virtual Apps and Desktops service, the Manage tab offers two types of deployment methods:

  • Full Configuration: The Full Configuration method uses the Studio console, which guides you through creating a machine catalog and then creating a Delivery Group. This deployment method offers advanced configuration features, and can be used for any supported host type.
  • Quick Deploy: The Quick Deploy method provides a simpler interface that offers faster deployment of apps and desktops, or Remote PC Access. This deployment method offers basic configuration, without advanced features.

    Quick Deploy is valid for:

    • Creating Remote PC Access catalogs for existing machines.
    • Provisioning virtual machines and catalogs for delivering desktops and apps in Microsoft Azure.

Differences between Quick Deploy and Full Deployment

The following table compares the deployment methods.

  Feature Quick Deploy Full Configuration
Deploy Deploy using Azure Yes Yes
  Deploy using other cloud services No Yes
  Deploy using on-premises hypervisors No Yes
  Citrix-managed images available Yes No
Deliver Deliver Windows apps and desktops Yes Yes
  Deliver Linux apps and desktops Yes Yes
User experience Remote PC Access Yes Yes
  Simplified user experience Yes No

If you are familiar with using Full Deployment (Studio) to create and manage catalogs, Quick Deploy has the following differences.

  • Different terminology.
    • In Quick Deploy, you create a catalog.
    • In Full Configuration, you create a machine catalog. In practice, it is often referred to as simply catalog.
  • Resource location and Cloud Connectors.
    • Quick Deploy automatically creates a resource location containing two Cloud Connectors when you create your first catalog.
    • In Full Configuration, creating a resource location and adding Cloud Connectors are separate steps that you must complete before creating a catalog.
  • Images used to create catalogs.
    • Quick Deploy offers several Citrix-managed images of Windows machines. You can use these images to create catalogs. You can also use these images to create new images and then customize them to suit your unique deployment needs. You can also import images from Azure.
    • In Full Configuration, customization of images is done through Azure (or through another supported host you’re using). Citrix-managed images are not available.
  • Catalog displays:
    • Catalogs that are created using Quick Deploy are visible in both the Quick Deploy display and in Full Configuration (Studio).
    • Catalogs that are created in Full Configuration (Studio) are not visible in the Quick Deploy display.
  • Delivery Groups and Application Groups.
    • Quick Deploy does not use Delivery Groups. In Quick Deploy, you configure all the deployment items in the catalog: machines, applications, desktops, and users (subscribers).

    A Delivery Group is automatically created for each Quick Deploy catalog (using the same name as the catalog), but that action occurs behind the scenes. You, as the administrator, don’t need to do anything to create the Delivery Group. The Delivery Group appears only in the Full Configuration (Studio) interface, not in the Quick Deploy display.

    • In Full Configuration, you create a Delivery Group and indicate which machines it contains. Optionally, you also specify applications, desktops, and users. You can also create Application Groups.
  • Layout and user interface.
    • The Quick Deploy interface has a different layout and style from the Full Configuration. There is more on-screen guidance.

The interfaces are not mutually exclusive. You can use Quick Deploy to create some catalogs, and then use Full Configuration to create other catalogs.

Important:

You can use Full Configuration (Studio) to edit a catalog created with Quick Deploy. However, if you use Full Configuration to change that catalog or its corresponding Delivery Group, you will no longer be able to edit that catalog in the Quick Deploy interface. The catalog will appear in Manage > Quick Deploy, but it cannot be managed or deleted in that interface. You must use the Full Deployment (Studio) interface to make any further changes to that catalog.

If you are familiar with the Citrix Virtual Apps and Desktops Standard for Azure service (formerly Citrix Managed Desktops), the Quick Deploy interface in the Virtual Apps and Desktops service is essentially identical for equivalent features (such as catalog creation, image building and importing). The Quick Deploy interface is easy to use, especially if you’re not familiar with Studio.

Quick Deploy in the Citrix Virtual Apps and Desktops service is not the same as the Quick Create feature in the Citrix Virtual Apps and Desktops Standard for Azure service. Also, the Virtual Apps and Desktops service does not support the Citrix Virtual Apps and Desktops Standard for Azure service features such as Citrix-managed subscriptions, network connections, and non-domain-joined machines.

Replacement of earlier Azure Quick Deploy interface

Quick Deploy replaces the earlier interface named Azure Quick Deploy.

  • If you did not use Azure Quick Deploy to create a catalog, it does not appear as a Manage menu option.
  • If you previously used Azure Quick Deploy, a message recommends you start using the new Quick Deploy. Although you can choose to continue using the earlier interface, it will be removed in a future release.

    The Quick Deploy display includes all of the catalogs you created using Azure Quick Deploy.

    If you started creating a catalog in Azure Quick Deploy, but did not finish it, that catalog will appear in the Quick Deploy catalog list. The only available action in Quick Deploy is to delete it.

Requirements

  • When provisioning VMs to deliver desktops and apps, Quick Deploy is available only when using Microsoft Azure as your host. It is not available with any other cloud host types, services, or hypervisors.
  • Quick Deploy is available only in the Citrix Virtual Apps and Desktops service, Premium and Advanced editions.
  • You must have a Citrix Cloud account and a subscription to the Virtual Apps and Desktops service.
  • You must have a Microsoft Azure account and at least one subscription.
  • You must have appropriate permission in the Virtual Apps and Desktops service to see the Manage tab. For details, see Delegated administration.

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.

The Citrix Gateway Service works automatically with Quick Deploy catalogs.

Configuration summary

Complete the following procedures to use Quick Deploy.

Note:

Features available in the Quick Deploy interface use the management layout and workflows from the Citrix Virtual Apps and Desktops Standard for Azure service (formerly Citrix Managed Desktops).

The configuration summary in this section contains links to Citrix Virtual Apps and Desktops Standard for Azure service articles for procedural details. In those linked articles, ignore information about Citrix-managed subscriptions, Citrix-managed Active Directory, network connections, and the quick create method for creating catalogs.

The following guidance applies to using Quick Deploy for machines that deliver desktops and apps. To set up a Remote PC Access deployment using Quick Deploy, follow the guidance in Remote PC Access.

  1. Sign in to Citrix Cloud and then select My Services > Virtual Apps and Desktops in the upper left menu.
  2. Select Manage > Quick Deploy.
  3. Use the link on the Quick Deploy welcome page to add at least one of your Azure subscriptions to the service. Follow the guidance in Add your Azure subscription.
  4. When creating a catalog, you can use one of the Citrix-managed images. Or, you can create and customize a new image or import an image from Azure. If you want to build or import an image, complete that task before creating a catalog.
  5. Use the link on the Quick Deploy welcome page to create a catalog. (In the linked article, ignore information about network connection and region.)

    If this is the first catalog, Quick Deploy automatically creates a resource location and two Cloud Connectors when the catalog is created.

  6. Add users to the catalog.
  7. After you create a catalog and add users to it, notify users where to find their desktops and apps: the Workspace URL. The Workspace URL is the same for all catalogs and users.

    On the Quick Deploy dashboard, view the URL by expanding User Access and Authentication on the right. For information about configuring workspaces for users, see Configure workspaces.

Management from the Quick Deploy interface

Important:

If you want to continue using the Quick Deploy interface to manage the catalogs you created there, do not use Full Configuration (Studio) to edit those catalogs or the delivery groups that are automatically created.

You can use the Quick Deploy interface to: