Roaming User Profiles redirects user profiles to a file share so that users receive the same operating system and application settings on multiple computers. The following article explains how to implement Roaming Profiles in your environnement. If you are deploying Windows 10 – 1803 (Windows 10 April 2018 update), you will notice a very strange behavior.
After enabling the Roaming Profiles on Windows 10 – 1803, not only the AppData\Roaming folder is written to the roaming profile, but also:
When you enable Roaming Profiles using Group Policy Object, a new registry key will be created in order to exclude AppData\Local and AppData\LocalLow, which is the normal behavior. Under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon, you should have the following values:
Even if this key exists on your system, AppData Local and LocalLow folders are still redirected.
Roaming User Profiles where the AppData\Local and AppData\Locallow folders are incorrectly synchronized at user logon and logoff.
To solve this issue, Microsoft has released a patch to avoid this issue. Please install the following KB: https://support.microsoft.com/en-sg/help/4340917/windows-10-update-kb4340917
If you don’t want to install the KB, you can use the following workaround:
- Create a new GPO
- And enable the following setting:
This will help to avoid the redirection.
Thanks for reading! You can follow me on Twitter @PrigentNico