Unicon documentation migration is in progress. You might find some broken links or experience minor issues in the documentation. We are working on resolving these issues.
X
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!
Optimizing with handshake
During each start-up the devices contact their Scout Server and check for new configuration data and application definition data. If they can’t access the Scout Server, they retry to connect and synchronize according to their handshake configuration.
Activating new configuration data might require a restart of the client. Then the user is informed and has the chance to suppress restarting.
Handshake parameters can be set in the terminal.ini file of the client by using the Advanced file entries feature. For further information, see Advanced file entries.
Handshake can be configured for the entire organization or for a particular OU or device.
The values shown in the figure above are examples and can be modified. By default, handshake is not configured.
The ScoutHandshake section provides the following configurable parameters:
| Parameter | Description |
|---|---|
| MaxRetries | Number of connection attempts. The value 0 deactivates handshake. |
| RetryTimer | Period of time in seconds until next connection attempt (start value). After each attempt, the interval is doubled (+/- random value). Example: Having defined 8 connection retries and a RetryTimer start value of 5 seconds, the 8th connection attempt is carried out after about 21 minutes. |
| PermanentRetriesAfterDays | Number of days (maximum) from the last successful connection until next connection attempt. Ensures that after n days latest the configuration data of device and [Scout Server] is compared. Can be combined with MaxRetries and RetryTimer. |
| WaitUser | Waiting time before client restarts to give the user the chance to close applications or log off. |
| CanCancel | Defines if the user is allowed to suppress a client restart (true\false). |
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.