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!
Replicate user stores
With the Replicate user stores policy, you can replicate the user store to multiple paths on each user logon and logoff. Doing so provides profile redundancy and guarantees a high level of availability for user profiles.
-
During user logon, Profile Management operates as follows:
- Attempts to connect to the primary user store (specified in
path to user store
) to fetch the user profile to the local computer. - If the primary store is unavailable, Profile Management sequentially attempts to connect to a replicated user store (specified in
Paths to replicate a user store
) until it connects to an accessible one. It then fetches the user profile from the accessible store. - When the previously unavailable store becomes accessible, Profile Management synchronizes it with the other stores to ensure data consistency.
- Attempts to connect to the primary user store (specified in
-
During user logoff, Profile Management writes the local profile back to both the primary and replicated user stores.
Note:
- This feature is available for both file-based and container-based profile solutions.
- Replicated profile containers provide profile redundancy for user logons but not for in-session failover.
- Enabling the policy increases system I/O and might prolong logoffs.
To configure the Replicate user stores policy using Group Policy, complete the following steps:
-
Open the Group Policy Management Editor.
-
Access Computer Configuration > Administrative Templates > Citrix Components > Profile Management > Advanced settings, and then double-click the Replicate user stores policy.
-
Set the policy to Enabled.
-
Click Show next to Paths to replicate a user store, and then enter the paths in the Value fields.
If the profile container is enabled for part of the user profile, you can replicate container-based profiles and file-based profiles to different locations. To do so, enter the path in this form:
<path to the replicated file-based profiles>|<path to the replicated container-based profiles>
. For example:\\path_a|\\path_b
indicates that Profile Management replicates file-based profiles to\\path_a
and container-based profiles to\\path_b
. -
Click OK and OK again.
Note:
To synchronize files and folders modified during a session to the user store, enable the Enable active write-back policy.
For your changes to take effect, run the gpupdate /force command from the command prompt on the machine where Profile Management is installed. Log off from all sessions and then log back on.
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.