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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Scenario 4 - The traveling user
“When my staff roam between different offices, I want their preferred NUS to change, so that they’re still using a geographically adjacent NUS.”
The difficulty with this scenario is that a user’s logon session might be aggregated from multiple locations. They typically roam their desktop session from one site to another. But many of their applications are hosted on back-end servers that have no awareness of the current location of the user’s desktop.
Furthermore, the user might reconnect to disconnected sessions, probably hosted at their home location. If the sessions were for some reason forced to switch to an NUS in the user’s new location, their performance degrades.
For travelers who hot-desk, using the Profile streaming and Always cache settings is the best option. With a fixed machine, they still log on quickly, using Citrix streamed user profiles. Enabling Always cache loads the remainder of the profile in the background.
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 Do Not Agree to exit.