-
-
-
-
-
Get started with Quick Deploy
-
-
Migrate workloads between resource locations using Image Portability Service
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Get started with Quick Deploy
This article summarizes the setup tasks for delivering desktops and apps using the Quick Deploy interface of Citrix DaaS (formerly Citrix Virtual Apps and Desktops service). We recommend that you review each procedure before actually doing it, so you know what to expect.
To use Quick Deploy to set up a Remote PC Access deployment, see Remote PC Access.
Setup task summary
The following sections of this article guide you through setup tasks:
-
Review and complete necessary tasks in system requirements and preparation.
-
Set up a quick proof of concept deployment or a production deployment.
-
Provide the workspace URL to your users.
System requirements and preparation
-
Sign up for Citrix Cloud and Citrix DaaS.
Also, if you plan to use Citrix Managed Azure, make sure to order the Citrix Azure Consumption Fund (in addition to Citrix DaaS), either through Citrix or Azure Marketplace.
-
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. For more information, see Configure a Microsoft RDS license server.
-
If you plan to use a Citrix Managed Azure subscription, and want 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 plan to use your own Azure images when creating a catalog, those images must meet certain requirements.
-
Internet connectivity requirements: System and connectivity requirements.
-
Resource limits in a Citrix DaaS deployment: Limits.
Supported operating systems
When using Quick Deploy with a Citrix Managed Azure subscription:
- Windows 10 single-session
- Windows 10 multi-session
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Red Hat Enterprise Linux and Ubuntu
When using Quick Deploy with a customer-managed Azure subscription:
- 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
- Red Hat Enterprise Linux and Ubuntu
Set up a quick proof of concept deployment
This procedure requires a Citrix Managed Azure subscription.
- Create a catalog using quick create.
- Add your users to the Managed Azure AD.
- Add your users to the catalog.
- Notify your users of the Workspace URL.
Set up a production deployment
- If you’re using your own Active Directory or Azure Active Directory to authenticate users, connect and set that method in Citrix Cloud.
- If you’re using domain-joined machines, verify that you have valid DNS server entries.
- If you’re using your own Azure subscription (instead of a Citrix Managed Azure subscription), add your Azure subscription.
- 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.
- 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.
- Create a catalog using custom create.
- If you’re creating a catalog of multi-session machines, add apps to the catalog, if needed.
- If you’re using the Citrix Managed Azure AD to authenticate your users, add users to the directory.
- Add users to the catalog.
- Notify your users of the Workspace URL.
After you set up the deployment, use the Quick Deploy > Monitor dashboard to see desktop usage, sessions, and machines.
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.
The Workspace URL is available in two locations:
-
From Manage > Quick Deploy in Citrix DaaS, view the URL by expanding User Access & Authentication on the right.
-
From the Citrix Cloud console, select Workspace Configuration from the upper left menu. The Access tab contains the Workspace URL.
For information about customizing the Workspace URL, see Customize the Workspace URL.
After users navigate to the Workspace URL and authenticate, they can start their desktops and apps.
Get help
-
Review the Troubleshoot article.
-
If you still have problems with Citrix DaaS, open a ticket by following the instructions in How to Get Help and Support.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.