Forum Discussion
IE Site list mode not working
Hello,
I'm trying to use the Enterprise Site List in Edge chromium. I read and followed the instructions and set the GP settings as mentioned in the MS instructions page.
The site list xml file was created using "Enterprise Mode Site List Manager v2" and worked fine on the pre-chromium Edge versions. I loads fine when trying to open in the browser.
I see the set policies in the 'edge://policy/' page (exported json file attached), it shows correctly with the correct URL addresses in the 'edge://compat/enterprise' page, but when I try to actually open one of the URLs, it loads up via Edge chromium and not IE, as I would expect.
I'm Running Windows 10 Enterprise OS Version 1803 (Build 17134.1304)
and Edge Version 80.0.361.54 (Official build) (64-bit)
Would appreciate any help on this, as I'm sure I followed all requirements, but fail to see the results.
eladz6 That is odd. We can take a look. Can you please send us the following -
1. A screenshot of edge://compat/iediagnostic
2. Start Edge with the command line "msedge.exe --enable-logging --v=1 --vmodule=*/dual_engine/*"
This will create a log in "%localappdata%\microsoft\Edge<Canary/Dev/Beta>\user data\chrome_debug.log"
This log is human readable and will contain URLs. Please proof read to ensure there is no PII information included before you share back with us.
Feel free to share the log via Private Message if you prefer.
Thanks!
28 Replies
- In my case. New copied admx doesn't show in gpo list. So I found out there was C:\Windows\sysvol\sysvol\yourdomain.net\Policies\PolicyDefinitions folder so I deleted it, now all admx works from C:\Windows\PolicyDefinitions
To work need modify this values at Policies\Administrative Templates\Microsoft Edge (not Policies\Administrative Templates\Windows Component\Microsoft Edge):
Configure the Enterprise Mode Site List
Configure Internet Explorer integration I had the path on a c:\edge\sitelist.xml as I was configuring for one AWS WorkSpace because C:\ is hidden (but reachable by typing in address C:\ of File Manager) I thought it was may a permissions issue in the AWS Workspace Window 10 64 bit workstation.
I had created the sitelist.xml file by right clicking and making a note file. This of course as .TXT to the end of it because extensions are not displayed by default nor is the details grid (which would have shown me the type). I sent the extensions on in View menu and found I forgot to change the extension to XML. I cut and pasted the file because I did not have a file transfer mode to that system (separate networks etc). Hope it helps others to make sure to check that.I see the same problem in Edge Version 100.0.1185.36 (April 2022)
I have created a sitelist and included it in Edge using Group Policy Editor.
1. When I open Edge and go to the IE11 compatability site, The site will NOT be opened in Internet Explorer compatibility mode.
if I instead
1. Open edge, go to edge://compat/enterprise and press "Force Update"
2. Opening the IE11 compatability site will open the site in Compatability mode
If I close Edge and open it again, I need to do the "Force Update" in edge://compat/enterprise again to make the site work in compatibility mode.
Is there any new information about this behaviour?- Kelly_Y
Microsoft
rauhe Would you be able to confirm if you have enabled the group policy for IE mode, “Configure Internet Explorer integration” (Configure IE mode Policies | Microsoft Docs)? Thanks!
-Kelly
Hi Kelly, Thanks for the reply...
Yes, yesterday I tried setting setting the “Configure Internet Explorer integration” option and this seems to have done the trick.
I was, however, hoping for an easier solution. I have to instruct non-PC-super-users to setup a pc for IE compatibility, and the solution I have (as described in your link), requires downloading and installing "Microsoft Edge Policy Template" to the Group Policy Editor (this is required for the option “Configure Internet Explorer integration” to be available). Even for me as a professional, this is not an every day task, so for a non-PC-super-user I think this is more or less impossible.
Do you know if it possible to set the “Configure Internet Explorer integration” setting trought the registry?
Best regards
John
eladz6 When "Configure Internet Explorer intergration" policy is set to Internet Explorer mode you need to set Open in IE11 and check Standalone IE .
The Engine will be set to IE11APP if you check it in
edge://compat/enterprise
Did you choose "Internet Explorer Mode" in "Configure Internet Explorer Integration" setting in the Group Policy editor?
Edit: 3rd picture in this URL ->
DeadCanDance I did, thank you. Just re-checked it after your message and it seems to be set correctly.
- Shilpa_Subramanian
eladz6 It looks like you have the policies set correctly. Does the site you expect to open in IE mode have the <open-in> tag set to IE11?
<site url="contoso.com">
<open-in>IE11</open-in>
</site>
I have a similar problem.
Our client has a website that uses the Activex component and the address must have initials in capital letters. The address is defined in the Enterprise mode list as follows:
//address.some.net/csp/test/Some.Window.cps
-<site url="address.some.net:57773/csp/test/Some.Window.cls">
<compat-mode>Default</compat-mode>
<open-in>IE11</open-in>
</link>
However, when checking edge://compat it shows the address in lower case. Like this: /address.some.net/csp/test/some.window.cps
Could this cause the site to not open correctly?Thanks for the reply.
I tried it both with "open-in" set to IE11 and to MS-Edge, but nothing really occurred on either. I also tried to place the site list Xml file both locally and remotely, but again - it had no effect.
- Shilpa_Subramanian
eladz6 I misread your initial post.
Sites configured to open in IE mode through the site list will load in Microsoft Edge (Chromium-based) on the same tab. The only indicator that the site is in IE mode is the IE11 icon on the top left next to the Refresh button.
It looks like you are expecting the site to open in the IE11 standalone app and not in Edge. If this is correct, you will need to add an additional attribute to the <open-in> tag.
<open-in app="true">IE11</open-in>
