-
-
-
Create catalogs of different join types
-
Create non-domain-joined catalogs
-
-
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!
Create non-domain-joined catalogs
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 or 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.
Share
Share
In this article
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 I DO NOT AGREE to exit.