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!
Configure active write-back
By default, Profile Management writes changes that are made to the local user profile back to the user store when a user logs off. If a user starts a second session before logging off the first, local profile changes made in the first session aren’t available in the second.
To improve profile consistency across concurrent sessions, you can enable the active write-back feature. With this feature, Profile Management writes local profile changes back to the user store during a session, rather than waiting until users log off.
Overview
Profile Management provides the Active write-back policy and two extension policies as follows:
-
Active write-back. Has Profile Management write changes made to the local profile files and folders back to the user store. By default, Profile Management performs active write-back every five minutes.
-
Active write back registry. Use it along with the Active write-back policy. Has Profile Management write changes made to the local registry entries back to the user profile.
-
Active write back on session lock and disconnection. Use it along with the Active write-back policy. Has Profile Management perform active write-back only when a session is locked or disconnected, instead of every five minutes.
Enable active write-back
To enable active write-back using a GPO, follow these steps:
- Open the Group Policy Management Editor.
- Access Policies > Administrative Templates: Policy definitions (ADMX files) > Citrix Components > Profile Management.
- Double-click Active write back.
- In the policy window that appears, select Enabled, and then click OK. By default, active write-back occurs every five minutes.
- To enable active write-back for registry entries, follow these steps:
- Double-click Active write back registry.
- In the policy window that appears, select Enabled, and then click OK.
- To have Profile Management perform active write-back only when a session is locked or disconnected, follow these steps:
- Double-click Active write back on session lock and disconnection.
- In the policy window that appears, select Enabled, and then click OK.
Note:
As a best practice, we recommend that you enable the Active write back on session lock and disconnection policy.
The configuration precedence for an active write-back policy is as follows:
- If the setting isn’t configured using a GPO, Studio, or Workspace Environment Management (WEM), the value from the .ini file is used.
- If the setting isn’t configured anywhere, Profile Management configures it dynamically.
For your changes to take effect, run the gpupdate /force
command from the command prompt as documented at https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/gpupdate.
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.