Deployment requires the use of Enterprise Mode Site List with Microsoft Edge on Windows 10 in a linked clone environment running Windows 10. This setting is typically delivered via GPO. The goal: when a user opens Edge and attempts to navigate to a site, Windows automatically opens that site in IE 11 and close Edge.
When the user logs in, they are required to open Edge once to get the policy downloaded. Once downloaded, the next time a user opens Edge with the URL in question, IE 11 opens the URL and closes Edge as expected, but this is required to occur once during every time the user logs into a new desktop, they must repeat these steps. What they’d like to is have UEM persist the fact that Edge has received the policy and simply open the link in IE 11. We are using UEM 9.2.1, with the Edge.ini file provided on the VMTN site. We are looking for assistance on how to persist the site list downloaded by the policy.
Edge stores the Enterprise Mode Site List information in <LocalAppData>\Micosoft\Windows\WebCache. This WebCache information is regularly in use by a scheduled task called Wininit\CacheTask which always keeps the files in use.
By simply adding <LocalAppData>\Micosoft\Windows\WebCache to the UEM config file, the FlexEngine.log file will show access denied errors when attempting to import the WebCache files. This is why the login tasks are necessary.
Three steps are required to ensure the Enterprise Mode Site List is made available to Edge immediately at logon. Those steps are below:
- Modifications to the Edge.ini file used by UEM
- Logon Task to cancel the CacheTask scheduled task before profile import
- Logoff Task to begin the CacheTask scheduled task once profile import is complete
Below are detailed information for each step required to remedy the issue.
Step 1: Modifications to the Edge.INI file used by UEM
Step 2: Create a Logon Task to stop the CacheTask process
The first logon task ends the Scheduled Task mentioned above using the SCHTASKS command and is set to run before the profile archive import – this unlocks the files in <LocalAppData>\Microsoft\Windows\WebCache in order to allow UEM to import the persisted data from the users’ profile.
Step 3: Create a Logoff Task to stop the CacheTask process
The second logon task runs the Schedule Task mentioned above using the SCHTASKS command and is set to run after the profile archive import – this reinitiates the CacheTask scheduled task.
There is one unknown to this solution. Given that the webcache file contains not only the Enterprise Mode Site List settings – it also contains Internet Explorer History, Cookies, Modern App cache, and more. As a result, the webcache will grow over time. This can consume a storage and could cause performance issue on logon time to copy the file back in. This solution may require the use of some mechanism to purge older cache data
This blog by James Rankin provided some insight on the scheduled tasks
Clear Cache via Command Line