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!
Enable UWP app roaming (preview)
With the Enable UWP apps roaming policy, you can let UWP (Universal Windows Platform) apps roam with users. As a result, users can access the same UWP apps from different devices.
Note:
- This policy is compatible only with Windows 10 and is incompatible with other Windows versions or Windows Server versions.
- The Replicate user store policy doesn’t support VHDX disk replication for UWP apps.
How it works
When the Enable UWP apps roaming policy is enabled, Profile Management operates as follows:
- When a user starts the installation of a UWP app, Profile Management monitors the installation process.
- If it’s the initial installation of the app in your environment, Profile Management creates a VHDX disk in the
{User_Store_File_Share_Path}\AppStore\
folder (referred to as UWP app container) and stores the app (except personal settings) in that disk. For subsequent installation of the same app, Profile Management doesn’t create an additional VHDX disk. Thus, each UWP app has a single VHDX disk within the UWP app container. - Upon user logon to a machine, VHDX disks of the UWP apps installed by the user are attached. Upon user logoff, those disks are detached.
Important:
UWP app roaming applies only to UWP apps installed using per-user packages after the policy is enabled. In other words, if the policy is enabled after an app is installed, the app won’t benefit from roaming until it’s reinstalled using a per-user package.
All users share UWP VHDX disks.
Enable the UWP app roaming policy using a GPO
Detailed steps are as follows:
- Open the Group Policy Management Editor.
- Access Policies > Administrative Templates: Policy definitions (ADMX files) > Citrix Components > Profile Management > Advanced settings.
- Double-click the UWP apps roaming policy.
- In the policy window that appears, select Enabled, and then click OK.
- To provide a better logon and logoff experience for UWP roaming, enable the Accelerate folder mirroring policy as follows:
- Access Policies > Administrative Templates: Policy definitions (ADMX files) > Citrix Components > Profile Management > File system > Synchronization.
- Double-click the Accelerate folder mirroring policy.
- In the policy window that appears, select Enabled, and then click OK.
The configuration precedence is as follows:
- If this setting isn’t configured using a GPO, Studio, or Workspace Experience Management (WEM), the value from the .ini file is used.
- If this setting isn’t configured anywhere, this feature is disabled.
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.