Like most companies out there, my company is getting ready to migrate to Windows 10. As part of our migration, we are using IE Enterprise Mode to handle many legacy web applications to ensure our end users get the best experience possible, and reduce the manual effort to ensure they are using the proper browser (and browser mode).
IE Enterprise Mode includes the ability to automatically re-direct sites from Microsoft Edge to Internet Explorer on Windows 10. This is fantastic for those who choose to use Edge as their default browser (as I do).
This post will not be covering exactly HOW to implement IE Enterprise mode as there is plenty of that documentation out there on the web. Instead, I’ll be focusing on a recent discovery that my colleagues and I made.
You’ve spent the last several months working with business partners to come up with a customized MS Edge redirect XML file and are ready to implement the file via GPP (or Compliance Settings or any other method you choose to set the registry key). You choose to set this on a Per-User basis because you want it to follow the user, not the machine (don’t ask why, just assume this is the reason).
The registry key that gets configured with your custom MSEdge xml file is at:
In addition to the above, you are running System Center Configuration Manager build 1602 (v1511 may also be affected – see below).
You expect this new XML file to redirect your custom LOB apps, but it doesn’t. Upon further inspection within Edge (HINT: Use about:compat in the URL bar of Edge), you ONLY see entries for your site server (specifically the server hosting the Application Catalog site).
I messaged David James (@djammer) on the ConfigMgr Product Team to confirm that the ConfigMgr Client Settings to add the Application Catalog URL in Trusted Sites is, indeed, using an MS Edge redirect XML file similar to that from IE Enterprise Mode.
As you can see from that last tweet, the solution (workaround really) is to set the reg key using the same path in the HKEY_LOCAL_MACHINE hive instead of HKEY_CURRENT_USER. Doing so allows your custom IE Enterprise Mode XML file to load and not be overwritten.
This can be verified by looking at SoftwareCatalogUpdateEndpoint.log and looking for this
I hope this information can help someone else out there. IE Enterprise Mode and ConfigMgr are awesome products and will be integral to a successful migration.