-
-
Manage non-domain-joined machines
-
-
Automatically back up configuration sets using WEM APIs and Windows PowerShell
-
Manage DaaS-provisioned non-domain-joined machines using WEM
-
Protect Citrix Workspace environments using process hierarchy control
-
Troubleshoot VDA registration and session launch issues using scripted tasks
-
Use Windows events as triggers to detect VDA registration issues
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!
Manage non-domain-joined machines
You can use Workspace Environment Management (WEM) to manage non-domain-joined machines in Citrix DaaS Standard for Azure (formerly Citrix Virtual Apps and Desktops Standard for Azure) deployments.
This feature enables you to assign policies and settings to non-domain-joined machines as you do with domain-joined machines.
A general workflow to get started with managing non-domain-joined machines is as follows:
-
In Azure, prepare a master image that has a Citrix VDA and a WEM agent.
-
Import that image from Azure for use with catalog creation. For more information, see Master images.
Important:
- For this feature to work, you must use WEM agent version 2103.2.0.1 or later. Download the WEM agent from the WEM service’s Utilities tab.
- For this feature to work, you must select Skip Configuration when installing the agent.
- By design, the agent running on the virtual machine that is used to create the image cannot connect to the WEM service.
-
In Citrix DaaS Standard for Azure, create a non-domain-joined catalog. For more information, see Create catalogs.
-
In the legacy console, add non-domain-joined machines to a WEM configuration set.
-
Go to the Administration Console > Active Directory Objects > Machines tab, click the down arrow next to Add Object, and then select Add Non-Domain-Joined Computers.
-
In the Add-Non-Domain-Joined Computers window, select one or more non-domain-joined machines that you want to add to the configuration set. The list displays only non-domain-joined machines that have not yet been added to any configuration sets.
-
Click Add to add the selected machines and to exit the Add-Non-Domain-Joined Computers window.
-
-
Optionally, verify that those machines are registered with the WEM service. To do that, navigate to the Administration Console > Administration > Agents > Statistics tab, double-click a machine you added and then confirm registration information in the Agent Information window.
Important:
Non-domain-joined agent machines automatically register with the WEM service and are added to the default configuration set.
After adding non-domain-joined machines to the WEM service, you can assign policies and settings to those machines as you do with domain-joined machines. However, when you assign policies and settings in the case of non-domain-joined machines, you have only the Everyone assignment option.
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.