
TStevenson asked a question.
Microsoft Edge 85.0.564.51 was just implemented in our environment. I have some users reporting that Edge is opening IE in compatibility mode for them. I think this is due to the web.config having the following:
<httpProtocol>
<customHeaders>
<add name="X-XSS-Protection" value="1; mode=block" />
<add name="X-Frame-Options" value="SAMEORIGIN" />
<add name="X-UA-Compatible" value="IE=9" />
<add name="X-Content-Type-Options" value="nosniff" />
Do I need to remove value=IE-9 or add Value="Edge" to this file? Looking for guidance on this. We're using DNS right now as the previous version web extensions weren't working in the environment and we have just packaged up version 3.0 of the extensions. I'm also wondering if version 3.0 web extensions will work with 2019 R1 until we upgrade to 2020 R1 in January
Charles,
I finally got back to this one after the holidays. After looking at the extensions and working with David we were able to determine the extensions are now in the store and we need to set the GPO policies with:
Chrome: omfdapccbikpkiheohohbohhglmijeeb;https://clients2.google.com/service/update2/crx
Edge: aejhddcfmefciddeneccplpjlnkfmapo;https://edge.microsoft.com/extensionwebstorebase/v1/crx