Get started 编辑

This article summarizes the setup tasks for delivering desktops and apps using Citrix Daas Standard for Azure (formerly Citrix Virtual Apps and Desktops Standard for Azure service). We recommend that you review each procedure before actually doing it, so you know what to expect.

For Remote PC Access setup tasks, see Remote PC Access.

Important:

To ensure that you get important information about Citrix Cloud and the Citrix services you subscribe to, make sure you can receive all email notifications. For example, Citrix sends monthly informational notification emails detailing your Azure consumption (usage).

In the upper right corner of the Citrix Cloud console, expand the menu to the right of the customer name and OrgID fields. Select Account Settings. On the My Profile tab, select all entries in the Email Notifications section.

Setup task summary

The following sections of this article guide you through setup tasks:

1. Prepare for setup.
2. Set up a deployment, following the guidance in one of:
   • Quick proof of concept deployment
   • Production deployment
3. Provide the workspace URL to your users.

Prepare

• If you aren’t familiar with catalogs, images, network connections, or Azure subscriptions, review the introductory concepts and terminology information.
• Read the security overview to learn and understand what you (the customer) and Citrix are responsible for.
• If you don’t already have a Citrix Cloud account that can be used for this service, get one, and then sign up for the service.
• Review the system requirements.
• Review the setup steps: proof of concept or production.

Set up a quick proof of concept deployment

This procedure requires a Citrix Managed Azure subscription.

1. Create a catalog using quick create.
2. Add your users to the Managed Azure AD.
3. Add your users to the catalog.
4. Notify your users of the Workspace URL.

Set up a production deployment

1. If you’re using your own Active Directory or Azure Active Directory to authenticate users, connect and set that method in Citrix Cloud.
2. If you’re using domain-joined machines, verify that you have valid DNS server entries.
3. If you’re using your own Azure subscription (instead of a Citrix Managed Azure subscription), import your Azure subscription.
4. Create or import an image. Although you can use one of the Citrix prepared images as-is in a catalog, they’re intended primarily for proof of concept deployments.
5. If you’re using a Citrix Managed Azure subscription, and want your users to be able to access items in your network (such as file servers), set up an Azure VNet peering or Citrix SD-WAN connection.
6. Create a catalog using custom create.
7. If you’re creating a catalog of multi-session machines, add apps to the catalog, if needed.
8. If you’re using the Citrix Managed Azure AD to authenticate your users, add users to the directory.
9. Add users to the catalog.
10. Notify your users of the Workspace URL.

After you set up the deployment, use the Monitor dashboard in Citrix DaaS for Azure to see desktop usage, sessions, and machines.

System requirements

For all deployments:

• Citrix Cloud: This service is delivered through the Citrix Cloud and requires a Citrix Cloud account to complete the onboarding process. For details, see Get a Citrix Cloud account.
• Windows licensing: Ensure that you are properly licensed for Remote Desktop Services to run either Windows Server workloads or Azure Virtual Desktop Licensing for Windows 10.

If you’re using a Citrix Managed Azure subscription:

• Azure subscriptions when using Azure VNet peering (optional): If you plan to access resources (such as AD and other file shares) in your own Azure network using Azure VNet peer connections, you must have an Azure subscription.
• Joining VDAs to Azure Active Directory (optional): To join VDAs to a domain using Active Directory Group Policy, you must be an administrator with permission to perform that action in Active Directory. For details, see Customer responsibility.

Configuring connections to your corporate on-premises network has extra requirements.

• Any connection (Azure VNet peering or SD-WAN): Requirements for all connections.
• Azure VNet peering connections: VNet peering requirements and preparation.
• SD-WAN connections: SD-WAN connection requirements and preparation.

If you want to use your own Azure images when creating a catalog, those images must meet certain requirements before you import them to Citrix DaaS for Azure.

Additional information:

• Internet connectivity requirements: System and connectivity requirements.
• Resource limits in a service deployment: Limits.

Supported operating systems

When using a Citrix Managed Azure subscription:

• Windows 7 (VDA must be 7.15 LTSR with latest Cumulative Update)
• Windows 10 single-session
• Windows 10 multi-session
• Windows Server 2012 R2
• Windows Server 2016
• Windows Server 2019
• Windows Server 2022 (requires minimum VDA 2106)
• Red Hat Enterprise Linux and Ubuntu

When using a customer-managed Azure subscription:

• Windows 7 (VDA must be 7.15 LTSR with latest Cumulative Update)
• Windows 10 Enterprise single-session
• Windows 10 Enterprise Virtual Desktop multi-session
• Windows Server 2008 R2
• Windows Server 2012 R2
• Windows Server 2016
• Windows Server 2019
• Windows Server 2022 (requires minimum VDA 2106)
• Red Hat Enterprise Linux and Ubuntu

Workspace URL

After you create catalogs and assign users, notify users where to find their desktops and apps: the Workspace URL. The Workspace URL is the same for all catalogs and users.

From the Manage > Azure Quick Deploy dashboard, view the URL by expanding User Access & Authentication on the right.

You can change the first part of the Workspace URL in Citrix Cloud. For instructions, see Customize the workspace URL.

Get help

Review the Troubleshoot article.

If you still have problems with the service, open a ticket by following the instructions in How to Get Help and Support.