-
-
-
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!
Registry Entries
Controls the creation of registry entries.
Tip:
You can use dynamic tokens to extend Workspace Environment Management actions to make them more powerful.
Registry value list
A list of your existing registry entries. You can use Find to filter the list by name or ID against a text string.
To add a registry entry
- Use the context menu Add command.
- Enter details in the New Registry Value dialog tabs, then click OK.
Fields and controls
Name. The display name of the registry entry, as it appears in the registry entry list.
Description. This field is only shown in the edition/creation wizard and allows you to specify additional information about the resource.
Registry Value State. Toggles whether the registry entry is enabled or disabled. When disabled, it will not be processed by the agent even if assigned to a user.
Target Path. The registry location in which the registry entry will be created. Workspace Environment Management can only create Current User registry entries, so you do not need to preface your value with %ComputerName%\HKEY_CURRENT_USER – this is done automatically.
Target Name. The name of your registry value as it appears in the registry (for example, NoNtSecurity).
Target Type. The type of registry entry that will be created.
Target Value. The value of the registry entry once created (for example, 0 or C:\Program Files)
Run Once. By default, Workspace Environment Management creates registry entries every time the agent refreshes. Select this check box to make Workspace Environment Management create the registry entry only once - on the first refresh - rather than on every refresh. This speeds up the agent refresh process, especially if you have many registry entries assigned to your users.
Action Type. Describes what type of action this resource is.
Import registry files
You can convert your registry file into registry entries for assignment. This feature has the following limitations:
-
It supports only registry values under
HKEY_CURRENT_USER
. With the registry entries feature, you can assign only registry settings underHKEY_CURRENT_USER
. -
It does not support registry values of the
REG_BINARY
andREG_MULTI_SZ
types.
To avoid the limitations, we recommend that you import your registry files to WEM by using the Import Registry File option in Group Policy Settings. For more information, see Import Group Policy settings from registry files.
To import a registry file, do the following:
-
Use Upload to upload the registry file you want to import. The file appears in the default folder in Citrix Cloud.
-
Go to Legacy Console > Actions > Registry Entries.
-
In the ribbon, click Import Registry File.
-
In the Import from Registry File window, select the desired registry file from the list. You can also start typing the file name and then click Find to locate it.
-
Click Scan to start scanning the registry file. After the scan completes successfully, a list of registry settings appears.
-
Select the registry settings that you want to import and then click Import Selected to start the import process.
-
Click OK to exit.
Fields and controls
Registry File Name. Populates automatically after you navigate to a .reg file and click Open. The .reg file contains registry settings you want to import into WEM. The .reg file must be generated from a clean environment to which only the registry settings you want to import are applied.
Scan. Scans the .reg file and then displays a list of registry settings that the file contains.
Registry Values List. Lists all registry values that the .reg file you want to import contains.
Enable Imported Items. If disabled, newly imported registry keys are disabled by default.
Prefix Imported Item Names. If selected, adds a prefix to the name of all registry items imported through this wizard (for example, “XP ONLY” or “finance”). Doing so makes it easier to identify and organize your registry entries.
Note:
The wizard cannot import registry entries with the same names. If your .reg file contains more than one registry entry that has the same name (as displayed in the Registry Values List), select one of those entries for import. If you want to import the others, rename them.
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.