The latest release of the Edge Browser based on the chromium rendering engine provides support for plug-ins such as Microsoft Silverlight from a mode called ‘Compatibility Mode’.
The Edge browser has ‘Compatibility Mode’ turned on by default. However, an individual user will need to go to browser/settings/more tools and then chose the option to run the application in ‘Compatibility Mode’. This process does not need to be completed where the appropriate Group Policies are established.
When running the Conquest 3 platform there are two Group Policy Object (GPO) settings that can be used to control the new Edge browsers behaviour across your users with respect to ensuring Conquest 3 always runs in Compatibility mode.
They are as follows:
1. First Group Policy Setting. When running in Compatibility Mode there is a banner message that appears each time the application is accessed that suggests the user switch to native Edge mode. This first policy is required to remove this banner message. Removing the banner can be set via a Group Policy Object in the Active Directory. When using Active Directory Microsoft have a Group Policy Object Administration Template file ready to download which includes the settings to turn the banner off.
2. Second Group Policy Setting. The second group policy tells Edge which sites/applications to run in Compatibility Mode, by referring to the saved list of sites/applications from a file that is usually called Sites.xml on the file server. Recording Conquest in Sites.xml will ensure the Browser always runs Conquest 3 in the required Compatibility Mode.
Completing these two set up tasks will ensure the users have trouble free operation of Conquest 3 on the latest Edge browser running in ‘Compatibility Mode’.
A full list of GPO settings for controlling the MS Edge Browser is available here:
https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies