Has anyone noticed (with roaming or mandatory profiles) that it is next to impossible to persist Cookies correctly in IE10 on Windows Server 2008 R2?
Previous to IE10 you could just redirect the Cookies to a network location - all good. However, when you upgrade Windows Server 2008 R2 to IE10, it looks like Microsoft decided to move from IE's old way of tracking this sort of data - index.dat files - and replace them with a proper database file called WebCacheV01.dat. I'm assuming this was done to take advantage of modern compute and simplify coding, as well as improving performance. When Internet Explorer is launched, the files under the %LocalAppData%\Microsoft\Windows\WebCache directory are locked, and these files are in use during the Internet Explorer session and for some time after Internet Explorer has exited. It looks like it's a Scheduled Task that keeps the handle open, of all things, the task in question is Task Scheduler Library > Microsoft > Windows > Wininet. However - stopping the Scheduled Task at logon and copying the files in, then restarting it, only works some of the time. Other times it seems as though dllhost.exe is actually keeping the file open too. Has anyone come across this and resolved it? Without using a local profile, it seems pretty much impossible to persist Cookies in IE10 on Server 2008 R2 - nightmare for my XenApp users, really! FWIW, in Server 2012 and Windows 8.1, it looks like the old index.dat method is now used again - talk about going back on yourselves! TIA, -- *James Rankin* --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
