-
How Profile Management works
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!
How Profile Management works
Profile Management addresses user profile deficiencies in environments where simultaneous domain logons by the same user introduce complexities and consistency issues to the profile. For example, if a user starts sessions to two different virtual resources based on a roaming profile, the profile of the session that terminates last overrides the profile of the first session. This problem, known as “last write wins,” discards any personalization settings that the user makes in the first session.
You can tackle the problem by using separate profiles for each resource silo. However, this approach results in increased administration overhead and storage capacity requirements. Another drawback is that users experience different settings depending on the resource silo they access.
Profile Management optimizes profiles in an easy and reliable way. At interim stages and at logoff, registry changes and the files and folders in the profile are saved to the user store for each user. If, as is common, a file exists, it is overwritten if it has an earlier time stamp.
At logon, users’ registry entries and files are copied from the user store. If a locally cached profile exists, the two sets are synchronized. As a result, all settings for all applications and silos are available during the session. And it is no longer necessary to maintain a separate user profile for each silo. Citrix streamed user profiles can further enhance logon times.
Profile Management helps to safeguard application settings for mobile users who experience network disruption (if the offline profiles features are configured) and users who access resources from different operating systems (if the cross-platform settings feature is configured).
Note: Profile Management processes domain user logons not local accounts.
For a more detailed overview of Profile Management, search the Profile Management blog on the Citrix Blogs home page.
Where network-based profiles are employed, consider adopting Profile Management in your organization. You might be able to implement other solutions such as mandatory or roaming profiles, and maintain them with standard knowledge of Microsoft Windows. However, unless your deployment is restricted (for example, a call center where user customization is limited so mandatory profiles are appropriate), Profile Management might be preferred.
Citrix recommends using folder redirection so that user-specific data is saved separately from the profile.
The home-folder and template paths must be configured only with the network location.
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.