You can change the flag settings under edge://flags They are actually not titled differently. Remember Microsoft`s download page for Edge? If we add a /business at the end, we get a new page: If you click on the download edge today, we will get a different result than before. However, in terms of Group Policy and other enterprise features, WSUS and the stand-alone package (assuming the same version) are identical.
Deployment with WSUS is recommended and easier, but you can also manually download the Microsoft Edge package and deploy it the same way you deploy other apps, and you can get it from: In terms of features and functionality, they are the same, but if you are using an older version, No new features and bug fixes are supported. The other option would be to upgrade to 20H2 and then deploy Microsoft Edge. You can simply use WSUS and deploy the new Microsoft Edge, and the data is imported from the old Microsoft Edge, and users can quickly continue using the new Microsoft Edge. You can download the AMDX files from here -> which then download and copy (to a domain controller) the latest msedge.adml and msedgeupdate.adml files Support for Microsoft Edge (legacy) ended on Madepends on your policy. If you want to force the installation of an addon, you need to get the extensionID that is in the edge://extensions, then go to the extension and find the ID. Note: If you don`t know how to access the Settings menu, you can type edge://settings in your address bar and press Enter.
0 kommentar(er)
