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!
Migrate user store
Profile Management provides a solution to migrate your user store without losing any data. This feature can be useful in cases where you want to migrate your user store to a more scalable file server.
To migrate your user store, use the Migrate user store policy along with the Path to user store policy. The Migrate user store policy lets you specify the path to the folder where the user settings (registry changes and synchronized files) were previously saved (the user store path that you previously used).
The path can be an absolute UNC path or a path relative to the home directory. In both cases, you can use the following types of variables:
- System environment variables (enclosed in percent signs)
- Attributes of the Active Directory user object (enclosed in hash signs)
Examples:
- The folder
Windows\%ProfileVer%
stores the user settings in a subfolder calledWindows\W2K3
of the user store (if %ProfileVer% is a system environment variable that resolves to W2K3). -
\\server\share\#SAMAccountName#
stores the user settings to the UNC path\\server\share\<JohnSmith>
(if#SAMAccountName#
resolves to JohnSmith for the current user).
In the path, you can’t use user environment variables except %username%
and %userdomain%
.
If this setting is disabled, the user settings are saved in the current user store.
If this setting is not configured here, the corresponding setting from the .ini file is used.
If this setting is not configured here or in the .ini file, the user settings are saved in the current user store.
After the changes to the policy settings take effect, the user settings stored in the previous user store are migrated to the current user store specified in the Path to user store policy.
To configure the migration of the user store in Group Policy, complete the following steps:
- Open the Group Policy Management Editor.
- Under Policies > Administrative Templates: Policy definitions (ADMX files) > Citrix Components > Profile Management, double-click the Migrate user store policy.
- Select Enabled.
- In the Options pane, type the user store path that you previously used.
- Click OK.
For your changes to take effect, run the gpupdate /force
command from the command prompt. Log off from all sessions and then log on again. For details, see https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/gpupdate.
You can also choose to configure the Profile Management policies in Citrix Studio. To do so, complete the following steps:
- In the left pane of Citrix Studio, click Policies.
- In the Create Policy window, type the policy in the search box. For example, type “Migrate user store.”
- Click Select to open the Migrate user store policy.
- Select Enabled and then type the user store path that you previously used.
- Click OK.
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.