User Profile
Gunnar-Haslinger
Steel Contributor
Joined Jun 05, 2017
User Widgets
Recent Discussions
Re: Make Edge Beta Default
Why you like to use "SetDefaultBrowser.exe" which is a tool for automating Settings during Automated/Unattended-Deployment if you are "new to computers"? This is not a tool an End-User needs, this is a tool for IT-Professionals. As an End-User just use the GUI to configure your default Browser. But to answer your question: If you like to use the Tool without providing full path name you have to put it in a folder which is included in the %PATH% Variable.Edge 116 Beta: Policies are blocked if MDM-Managed & Userprofile-Sync personal Account
On most current Edge Beta & DEV Versions there is a NEW BUG regarding accepting the Configuration of "sensitive Policies" which need the device to be Enterprise Managed (AD-Join or MDM-Enrolled). [Edit on next day 22.08.2023: see newer post below, not only sensitive Policies but much more policies are ignored! Therefore I modified the title of this Discussion and removed "sensitive"] First, the affected Versions are: Beta: Version 116.0.1938.54 Dev: Version 117.0.2045.1 NOT affected, still working as expected is: Stable: Version 115.0.1901.203 To reproduce the issue, use a Windows 10 or Windows 11 22H2 Machine which is MDM-Enrolled. Fresh Edge-Browser install, first NO Profile Sync / logged on User Account in Edge: OK; Policies work, are applied - as you see in this screenshot: Now enable Profile-Sync / log on with personal Microsoft Account in Edge Browser (Profile). After Syncing Profile now restart Browser. => Problem: Device is not recognised as "MDM-Enrolled" any more, the "sensitive policies" are now ignored: If you "sign out" (no need to delete Favorites, just "sign out" is enough) the policies start working again after next browser-start: As I already said in the beginning, this is "brand new" problem in the most recent Beta- and DEV-Version. Was definitely not there in the last Beta-Version last week before (I think Beta Version 116.0.1938.51 was still OK). And Problem is not there in current Stable, only in Beta&Dev. So please look into this and fix this before it gets into Stable! Thank you! mkruger& Kelly_Y I hope you are still working on the Edge team and can bring this to the attention of the right person? Thank you! Not sure if this is an Edge Issue or an underlying Chromium-Issue. If it is a Chromium-Issue it maybe could be this Change: https://chromium-review.googlesource.com/c/chromium/src/+/4762065/1?tab=commentsRe: edge 116 does not work ie mode by enterprise site list(when login edge proflie)
lee_1_1 it seems Microsoft strips out almost all policies when you are "signed in" in Browser with a personal Microsoft Account now with Edge v116 (Edge for Business). For me this behaviour even if there is no Work-Profile configured (which would enable Edge for Business) is crazy, see my post here.Re: Edge v93 - v96 opens .MHT Files but shows no content ("white page")
Without setting policies .mht Files like I published in the given examples above won't work in Edge v113. To get them to open in IE-Mode use following Policies: 1. Set "InternetExplorerIntegrationLevel" (I used Level 1 to test). 2. Set "InternetExplorerIntegrationLocalMhtFileAllowed" to 1 3. Set "InternetExplorerIntegrationLocalFileExtensionAllowList" -> "1" -> ".mht" with those 3 policies set my Edge v113 opens .mht Files in IE-Mode by default and renders them correctly. Here a Screenshot of my policies, filtered by "InternetExplorer": Here a Link to my Test-MHT-Files: https://hitco.at/mht-test/ Here a Screenshot of an random .mht File, automatically opened in IE-Mode:Re: Dev Channel update to 109.0.1495.2 is live
AndresP yes, I think you understand it wrong. And I think the article is written misleading. There is this small sentence which should get your attention: In addition to trusting the built-in roots that ship with Microsoft Edge, the browser will also query the underlying platform for—and trust—locally installed roots that users and/or enterprises installed. so in fact nothing seems to change for Enterprise-CAs deployed to Windows-OS-CertStore. See this Blog-Post here, which is written much clearer than the official documentation: https://textslashplain.com/2022/12/06/tls-certificate-verification-changes-in-edge/ This blog is written by https://twitter.com/ericlaw who is working at MSFT/EdgeRe: Dev Channel update to 109.0.1495.2 is live
Thanks Eric_E for your reply. but what's missing is not the Policy-Documentation (this is a simple on/off policy - so the documentation is fine) but the Information about how to add own Enterprise CAs, SubCAs to MicrosoftRootStore of Edge. In this announcement Microsoft tells us: Microsoft recommends that enterprises that have break-and-inspect proxies or other scenarios involving TLS server certificates issued by roots not in the Microsoft CTL to proactively test with the policy enabled in Microsoft Edge 109 and report any compatibility issues to Microsoft. OK. So where to report? We cannot start the test because Information on how to configure this is missing. Please update / add Information to the announcement and provide documentation.Re: Dev Channel update to 109.0.1495.2 is live
where can I find Information about how to add own Enterprise CAs, SubCAs to MicrosoftRootStore of Edge when the MicrosoftRootStoreEnabled Feature is turned on? I currently have to add several CAs to the Windows 10 Certificate Store, as I understand in future Versions of Edge I would have to add them to the internal Edge MicrosoftRootStore too. How to do this automated during deployment? Where can I find documentation about this? On this page I can only find the timeline of Edge v109 to Edge v111 and the Policy itself but no link to details.
