-
What's new
-
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!
What’s new
What’s new in 2206
This release includes the following new features and addresses issues to improve the user experience:
Process hierarchy control
This release introduces the process hierarchy control feature. The feature lets you control whether certain child processes can be started through their parent processes. You create a rule by defining parent processes and then designating an allow list or a block list for their child processes. You then assign the rule on a per user or per user group basis. The following rule types are available:
- Path. Applies the rule to an executable according to the executable file path.
- Publisher. Applies the rule according to publisher information.
- Hash. Applies the rule to identical executables as specified.
For the feature to work, you need to use the AppInfoViewer tool on each agent machine to enable the feature. Every time you use the tool to enable or disable the feature, a machine restart is required. For more information, see Process Hierarchy Control.
Enhancements to memory management
This release includes enhancements to the memory management feature. The feature now provides you with two extra options to perform memory management:
- Do Not Optimize When Total Available Memory Exceeds (MB). This option lets you specify a threshold below which WEM optimizes memory usage for idle applications.
- Enable Memory Usage Limit for Specific Processes. This option lets you limit the memory usage of processes by setting upper limits for the memory they can consume.
For more information, see Memory Management.
Administration console
The user interface of the administration console has changed:
- A new node, Process Hierarchy Control, is now available in Security. The node contains a tab that lets you control whether certain child processes can be started through their parent processes.
- An option, Do Not Optimize When Total Available Memory Exceeds, is now available in System Optimization > Memory Management > Memory Management. The option lets you specify a threshold limit below which Workspace Environment Management optimizes memory usage for idle applications.
- A new tab, Memory Usage Limit, is now available in System Optimization > Memory Management. The tab lets you configure memory usage limits for specific processes.
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.