Article ID: 2795607
This article describes an expected interaction between Microsoft Store Apps and Side Loaded Modern Apps with Roaming User Profiles (RUP). Enterprise Administrators will need to take these behaviors into account when deploying Windows 8 when using Roaming User Profiles are used.
Issue 1 Windows Store Apps are not available if the Group Policy "Delete cached copies of roaming profiles" is enabled
A user logs on and notices that the only tiles that appear on the Start Screen are the Desktop, IE and Store. Using the Store application to install additional applications also fails.
This behavior is by design. The default behavior of Windows 8 clients with Roaming User Profiles that have the Group Policy (GP) "Delete cached copies of roaming profiles" applied to them is to only display the Desktop, IE and Store tiles on the start screen.
Users with roaming profiles subject to the "delete cached copies of roaming profiles" policy can install modern applications if the "allow deployment operations in specified profiles" policy is enabled. This GP is located in Computer Configuration\Policies\Administrative Templates\Windows Components\App Package Deployment".
When considering whether allowing the use of a Modern app in a scenario that uses RUP and "Delete cached copies of roaming profiles" it is important to differentiate between Windows Store app installed via the Windows Store and Modern apps that are sideloaded by an administrator. Windows Store Apps can only be purchased and installed via the Store and are maintained or patched via the Store. Sideloaded apps are installed by an administrator and are also maintained by an administrator. No contact with the Store is needed for sideloaded applications.
Microsoft does not recommend using Windows Store applications with RUP that also have the GP "Delete cached copies of roaming profiles" applied to them for the following reasons:
If no Windows store applications are required for LOB requirements, then the default behavior when using RUP and having "Delete Cached copies of roaming profiles" set can be left in place. In addition, the Windows Store should also be blocked via GP to prevent users from attempting to install applications only to have the installation fail at the end. The GP for this is "Turn off access to the store" located in "Computer Configuration\Policies\Administrative Templates\System\Internet Communication Management\Internet Communication settings"
Sideloaded Modern Apps
If your deployment includes side-loaded Modern applications, a customized image should be created that removes all Windows Store apps, customizes the Start Screen tiles and has the LOB application provisioned (i.e. preinstalled). In this situation the Administrator can then enable both the "Delete cached copy of roaming profiles".
For information regarding deploying images with customized Start Screens and sideloading Modern apps see the following links:
Issue 2 Modern Apps do not roam with Roaming User profiles.
This behavior is by design. The user is either logging into a terminal server farm and is not logging into the same Terminal Server as the previous logon , or the user is logging into a different workstation than the workstation where the Windows Store app was installed.
Windows Store Applications are installed to the c:\users\<userName>\AppData\Local\* directories. The AppData\Local directory, as the path implies, is not part of the of the users profile that roams.
This behavior is consistent with RUP and standard Windows desktop applications. RUP makes no provision to roam applications.
If users with roaming profiles are allowed to use and install apps, Store, side-loaded and desktop applications must be installed on each device the user may login to.
An administrator will also need to consider the following points:
For more information on Windows Store Apps follow this link http://msdn.microsoft.com/en-us/library/windows/apps/hh974576.aspx
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2795607 - Last Review: January 11, 2013 - Revision: 4.0
Contact us for more help