Citrix DaaS

Create non-domain-joined catalogs

October 24, 2024

Contributed by:

This article describes how to create non-domain-joined catalogs using Citrix DaaS.

For information on requirements, limitations, and considerations, see Non-domain-joined.

Before you create the machine catalog, you need the following:

New resource location
- Navigate to the Citrix Cloud admin UI > upper left hamburger menu > Resource Locations.
- Click + Resource Location.
- Enter a name for the new resource location and click Save.
Create a hosting connection. See Create and manage connections section for details.

Using Citrix DaaS, you can create catalogs based on workgroups for non-domain-joined machines. Creating non-domain-joined machines depends on how the account identity pool is created. The account identity pool is the mechanism used by MCS to create and track machine names during catalog provisioning.

You can create non-domain-joined catalogs by using Studio or PowerShell.

Use Studio

The following information is a supplement to the guidance in Create machine catalogs. To create non-domain-joined catalogs, follow the general guidance in that article, minding the details specific to non-domain-joined catalogs.

In the catalog creation wizard:

On the Machine Identities page, select Non-domain-joined. The created machines are not joined to any domain.

Note:

The Non-domain-joined identity type requires version 1811 or later of the VDA as the minimum functional level for the catalog. To make it available, update the minimum functional level if necessary.

Use PowerShell

The following are PowerShell steps equivalent to operations in Studio.

You can create an identity pool for non-domain-joined catalogs using the Remote PowerShell SDK.

Use the PowerShell parameters, WorkgroupMachine and IdentityType to create an identity pool for non-domain-joined catalogs. The parameters eliminate the need to specify all AD-specific parameters including domain administrator credentials:

New-AcctIdentityPool -AllowUnicode -IdentityType "Workgroup" -WorkgroupMachine -IdentityPoolName "NonDomainJoinedCatalog" -NamingScheme "NDJ-VM-##" -NamingSchemeType "Numeric" -Scope @() -ZoneUid "81291221-d2f2-49d2-ab12-bae5bbd0df05"
<!--NeedCopy-->

All other commands used to create non-domain-joined catalogs are the same as for the traditional on-premises Active Directory joined catalogs.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Create non-domain-joined catalogs

October 24, 2024

Contributed by:

October 24, 2024

Contributed by:

Create non-domain-joined catalogs

Use Studio

Use PowerShell

In this article