Prepare Installation Non-Domain joined VDAs

This section guides you to prepare the control planes both for CVAD customers and DaaS customers, so you can later install the non‑domain joined (NDJ) Citrix VDA for macOS to connect with, then manage the VDAs in the control plane accordingly.

The workflows are quite similar between on-prem CVAD and DaaS, while the most essential step is to generate enrollment tokens from the control plane so the Non‑Domain Joined VDA can enroll and register accordingly.

NJD VDAs obliterate the need to join VDAs to Active Directory domains for VDA and user authentication: when you create a non‑domain joined VDA, we use secure public‑private key‑pairs for registering the VDA to the control planes. Thus, to join an Active Directory domain is no longer required.

Important:

Non‑domain‑joined VDAs are supported for both Citrix DaaS and CVAD.

  • You can deploy non‑domain joined VDAs in a macOS hosting provider’s environment or your on‑premises environment such as a data center or your end user’s machine for them to perform a remote access

  • Non‑domain‑joined VDA is connected to the Citrix DaaS control plane through Rendezvous V2 that do not require any Cloud Connector presence, where the corresponding policy for Rendezvous V2 shall be configured; to launch the VDA, besides Workspace configured by the DaaS control plane, you can also launch the VDA from StoreFront or/and NetScaler with Cloud Connector point to the Cloud Tenant; for more information, please refer to Citrix DaaS install and configure overview.

Prepare Installation Non-Domain joined VDAs

In this article