If I manually create the RedirectionMode key and then re-launch Edge, it correctly follows the policy and sets RedirectionMode to 0. I know we are behind the ball but were planning on finishing up our. This seems premature from the June 15 timeline as has been advertised. This his our company this morning and we are now scrambling to roll out policy we hadn't finished testing yet. We've set both the RedirectSitesFromInternetExplorerRedirectMode and the RedirectSitesFromInternetExplorerPreventBHOInstall policies to prepare for the release of. If the BHO doesn't find the key, the default is to redirect. The new version of Edge (Build 102) that just rolled out seems to be forcing all IE traffic to Microsoft Edge. (antivirus software) I contacted QuickHeal and they suggested me to disable their antitracking tool and uninstall their software: and then reboot the computer and. Further digging shows that the HKEY_CURRENT_USER\Software\Microsoft\Edge\IEToEdge | RedirectionMode key, which is what the BHO itself uses, is not being created nor set to 0 when the policy is read by Edge. I have opened Edge in my new laptop and found that it’s Managed by your organization. While "Never" is displayed correctly in Edge settings, it doesn't work. Set the RedirectSitesFromInternetExplorerPreventBHOInstall policy to Enabled. This setting will stop redirecting as soon as the policy takes effect. Remember, we had no way to fully test this prior to the 87 release since we're domain-joined. Set the RedirectSitesFromInternetExplorerRedirectMode policy to Enabled AND then in the dropdown under Options: Redirect incompatible sites from Internet Explorer to Microsoft Edge, select Disable. We also added the RedirectSitesFromInternetExplorerRedirectMode policy, again before the 87 release, just to cover our bases. This isn't documented in the release notes or the ADMX itself, but it's logical since the installer/updater typically runs as system. While the RedirectSitesFromInternetExplorerPreventBHOInstall policy appears in the User Config, it looks like it fails because the setup doesn't detect the setting unless it's set in the Computer Config. We generally prefer to add settings to the ADMX User Configuration, since it makes exceptions easier to manage. We implemented both policies prior to the Edge 87 release.
0 Comments
Leave a Reply. |