Change setting Allow sites to be reloaded in Internet Explorer mode > Allow. > Settings > Default Browser (shortcut: go to edge://settings/defaultBrowser ) New versions of Edge allow using a simplified process: NEW SIMPLIFIED USER-BASED PROCESS (required for Windows 11): PLEASE NOTE: qvp:// links are not supported with Microsoft Edge For a corporate-wide setup, please reach out to your group policies/domain administrators. The example provided helps you configure a single PC. In case of problems, please refer to Microsoft's documentation. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The information in this article is provided as-is and to be used at own discretion. QlikView IE-Plugin April 2020 SR3 (12.50 SR) or higher. This article is about the client-managed ("on premise") version of QlikView.įor QlikView on Qlik Cloud please follow " QlikView on Qlik Cloud: open documents using the IE-plugin via Edge Chromium" hiding or removing the previously installed enduser-version of Edge and offering only the enterprise-editon, maybe with the risk of loss of information of our users like favourites etc.How to configure Microsoft Edge (Chromium version) to run QlikView's IE-Plugin. 
But this mustn't trigger new problems for our users when we start upgrading their computers to build 20H2 (e. So what are the differences between these Edge-versions, how does one check which version is installed? As right now users keep getting notifications that the should switch to the newer Edge we need to decide if we deploy a software-package of the 'regular' Enduser-Edge-version (Chromium-based) with our soft- and hardware-managment-tool. etc.), not a standalone-installation using its own update-function (without WSUS).
On the other hand it was said that MS does not support the 'regular' Edge-version on enterprise-installations, WSUS only offers several Edge-Channels (Stable, Dev. A colleague has tried such an inplace-upgrade (using a special group in our WSUS, only there the 20H2-feature-update is availble) and now it seems that the Edge-Browser (Chromium-based) does show the same information as a manually installed 'enduser-'Edge (Chromium-based too) on another Win10 enterprise-computer.
We are planning to switch our Win 10 enterprise-computers to upgrade from build 1890 to 20H2.
0 kommentar(er)
