![]() ![]() Instead, the devices will automatically get the current version, and Edge will stay up to date as the channel is updated. This means you do NOT need to revisit this app deployment wizard nor create any new deployment package every time Edge is updated. NOTE: Using this method will always install the “current” version of Edge based on the release channel you choose (Stable / Beta / Dev). ![]() The Chromium-based version of Edge will begin shipping as the default browser beginning with Windows 10 20H2, but until then, you’ll need to deploy it. You can even install Chrome Extensions in Edge if that’s your thing. It’s a neat trick, and it’s easy to set up. And once those settings are in Edge, they can also be synchronized to the users Azure AD account, which allows those settings to effectively roam between devices. With features like the ability to import settings from other browsers such as Bookmarks, Favorites, Extensions, Saved forms data and Saved Passwords, installing “new” Edge also gives an opportunity to truly migrate from several browsers (that may or may not be managed) in to one. ![]() As the Spartan version of Edge is gradually being replaced with the new Chromium based edition of Edge, it’s a good time to start deploying and managing this new browser which will soon become the default browser starting with Windows 10 20H2 which should land in just a couple months from now. ![]()
0 Comments
Leave a Reply. |