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!
Load management policy settings
The Load Management section contains policy settings for enabling and configuring load management between servers delivering Windows Multi-session OS machines.
For information about calculating the load evaluator index, see CTX202150.
Concurrent logon tolerance
This setting specifies the maximum number of concurrent logons a server can accept.
By default, this is set to 2.
When this setting is enabled, load balancing tries to avoid having more than the specified number of logons active on a Server VDA at the same time. However, the limit is not strictly enforced. To enforce the limit (and cause concurrent logons that exceed the specified number to fail), create the following registry key:
HKLM\Software\Citrix\DesktopServer\LogonToleranceIsHardLimit Type: DWORD Value: 1
CPU usage
This setting specifies the level of CPU usage, as a percentage, at which the server reports a full load. When enabled, the default value at which the server reports a full load is 90%.
By default, this setting is disabled and CPU usage is excluded from load calculations.
CPU usage excluded process priority
Note:
In scenarios where machines are managed by Workspace Environment Management, using this setting along with the CPU Priority settings can have unintended results. We recommend that you disable this setting if you choose to use the CPU Priority settings.
This setting specifies the priority level at which a process’ CPU usage is excluded from the CPU Usage load index.
By default, this is set to Below Normal or Low.
Disk usage
This setting specifies the disk queue length at which the server reports a 75% full load. When enabled, the default value for disk queue length is 8.
By default, this setting is disabled and disk usage is excluded from load calculations.
Maximum number of sessions
This setting specifies the maximum number of sessions a server can host. When enabled, the default setting for maximum number of sessions a server can host is 250.
By default, this setting is enabled.
Memory usage
This setting specifies the level of memory usage, as a percentage, at which the server reports a full load. When enabled, the default value at which the server reports a full load is 90%.
By default, this setting is disabled and memory usage is excluded from load calculations.
Memory usage base load
This setting specifies an approximation of the base operating system’s memory usage and defines, in MB, the memory usage below which a server is considered to have zero load.
By default, this is set to 768 MB.
Share
Share
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.