-
-
-
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!
File System Operations
Controls the copying of folders and files into the user’s environment.
Tip:
You can use dynamic tokens to extend Workspace Environment Management actions to make them more powerful.
File system operations list
A list of your existing file and folder operations. You can use Find to filter the list by name or ID against a text string.
To add a file system operation
- Use the context menu Add command.
- Enter details in the New File System Operation dialog tab, then click OK.
Fields and controls
Name. The display name of the file or folder operation, as it appears in the list.
Description. Lets you specify additional information about the resource. This field appears only in the edition or creation wizard.
Filesystem Operation State. Controls whether the file system operation is enabled or disabled. When disabled, it is not processed by the agent even if assigned to a user.
Source Path. The path to the source file or folder that is copied.
Target Path. The destination path for the source file or folder that is copied.
Note:
While using a non-domain-joined agent, WEM might not work if network share is used in Source Path or Target Path.
Overwrite Target if Existing. Controls whether the file or folder operation overwrites existing files or folders with the same names in the target location. If cleared, and a file or folder with the same name already exists at the target location, the affected files are not copied.
Run Once. By default, Workspace Environment Management runs a file system operation every time the agent refreshes. Select this option to let Workspace Environment Management run the operation only once, rather than on every refresh. This speeds up the agent refresh process, especially if you have many file system operations assigned to your users.
Action Type. Describes what type of action this file or folder action is: Copy, Delete, Move, Rename, or Symbolic Link operation. For symbolic link creation, you need to give users the SeCreateSymbolicLinkPrivilege
privilege for Windows to allow symbolic link creation.
Execution order. Determines the running order of operations, letting certain operations run before others. Operations with an execution order value of 0 (zero) run first, then those with a value of 1, then those with a value of 2, and so on.
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.