We’ve redesigned the browser cache to improve the performance, flexibility, reliability, and scalability of Internet Explorer and the apps that rely on the Windows Internet (WinINet) cache. Our new database design stops multiple clients from simultaneously accessing and using cached information, while also providing a higher level of data integrity.
You won’t notice any changes to the management of your roaming profile data if you use our new database implementation in conjunction with the roaming user profile guidelines. This means that IE data that’s stored in the
AppData\Roaming user profile folder is still be uploaded to your normal profile storage location after a user successfully logs off.
Cookies in a roaming profile can only be set by Internet Explorer for the desktop, with Enhanced Protected Mode turned off. Cookies set by the immersive version of IE or by Windows Store apps, can’t be part of a roaming profile. For more information about persistent cookies and roaming, see Persistent cookies are not roamed in Internet Explorer.
To get the best results while using roaming profiles, we strongly recommend the following:
Create a separate roaming repository for each domain account that uses roaming.
Restrict roaming user profiles so they work on only one computer at a time. Using a single roaming profile on multiple computers isn’t supported (via console or Remote Desktop) and can cause unpredictable results, including cookie loss.
Allow all computers that let users sign-on with a roaming profile have identical IE cookie policies and settings.
Make sure to delete the user’s local roaming profile at sign off for any computer using user profile roaming. You can do this by turning on the Delete cached copies of roaming profiles Group Policy Object.