User Profile
Joachim_T
Iron Contributor
Joined Jan 31, 2020
User Widgets
Recent Discussions
Re: Bug Report: "Open in Sidebar" Available Despite Sidebar Being Disabled with HubsSidebarEnabled
Kelly_Y kojisugiyama Hi, yeah i have just seen it and came back ro report ;). Its included in 122.0.2365.63 policy files and hopefully also works with edge 122.0.2365.63. Now try to rush it along our company release process to get it into the wild 😉 Have a great weekend JoachimRe: Bug Report: "Open in Sidebar" Available Despite Sidebar Being Disabled with HubsSidebarEnabled
kojisugiyama and @Kelly_Y The V122 Policy documentation and the stable release notes talks about its included. https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies#edgeopeninsidebarenabled https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel Unfortunatly in the 122.0.2365.59 policy file its still not included. So documentation lies to us? Or is documentation just faster than real world?Re: Policy ShowMicrosoftRewards doesnt prevent to show up Microsoft Rewards in Menu any more
Kelly_YHi. Very thanxs for your efforts. So far it seems to work in Beta 113.0.1774.9. Unfortunaly, because we are only on extended stable, we cant participate in this improvement before 114. So still a long way to go. So backporting would be very much appreciated I hope our compliance officers dont stumble over this automatic bribing system before its gone again. JoachimPolicy ShowMicrosoftRewards doesnt prevent to show up Microsoft Rewards in Menu any more
Hello together, since Beta 111 Microsoft Rewards shows up in menu of Edge even if ShowMicrosoftRewards is set to false. Its first time recognized in 111.0.1661.27. Not sure if it showed up before in other 111 Versions. If a user opens the menu point a login page shows up. These kind of personal data stealing functions have to be completly removed in our company by law. Please fix this asap. I cant risk that a federal data protection office shows up and shut us down because of this. Thanx in advance JoachimRe: How to open office files in Edge browser without downloading
rafalw15851895, Kelly_Y https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies#quickviewofficefilesenabled I have this Policy enabled since its availabel. I have never ever seen it working. All MS Office documents continue to be downloaded (Word, Excel, Powerpoint). No matter from where. We dont have a urgent need for this feature. So we never missed it. But anyway. I am curious if there is anybody out there who have seen it at work. JoachimRe: UserDataSnapshotRetentionLimit and Endless growing Edge Profile
smithbe40 - No unfortuntaly not. At the moment i just have completely excluded the folder in CItrix Profile Management. That means i am not able to go back to an older version. Its a risk and means i need proper testes before rollout. But on the other hand it never happend yet. JocachimIs CVE-2022-1634 to CVE-2022-1640 included in extended Stable 100.0.1185.60?
Hello, once again the documentation of extended Stable is not worth the electrons used to write the entrance in the release notes. And once again a responsible enterprise admins is forced to use a crystal ball or tarot cards to find out if my enterprise is safe with extended Stable 100.0.1185.60 No information in https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel No information in https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnotes-security#may-13-2022 No information in https://msrc.microsoft.com/update-guide Seems once again my company and i are doomed. JoachimRe: Disable Update Edge Chromium
Trister_Andre This window should only come if you have set https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#relaunchnotification to "Required (2)". Check your Policys under edge://policy/ to find ou whats really set. Seems there are more policys active than you might thought. JoachimRe: Small problems with RelaunchNotification policy
Kelly_Y. Yes thats right. You got it. Its not a real big problem because 95% of our users never see the notification. They reboot daily or close edge after work. And 90% of the remaining users have only a single edge windows with a lot of tabs. But unfortunatly there are 3 or 4 how i call them window messys with dozen of open never again used edge (and many other) windows. Even then no security problem. Edge closes and new version is active. Its just a tiny little comfort problem for a hand full of users who might or might not get suprised by a suddenly restarting Edge. JoachimSmall problems with RelaunchNotification policy
Hello folks, to prevent never updated Edge instances because some of our "specialists" never close their edge and never reboot their client we use the policy "https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#relaunchnotification" -> Notify a user that a browser restart is recommended or required for pending updates We set it to: Required (2) = Required - Show a recurring prompt to the user indicating that a restart is required This works fine overall. But there are situations where the user never sees the prompt and gets surprised by the restart of the browser. The popup is modal and comes only with the first edge window. If the user opended several windows and the one getting the popup is a forgotten background window the user never gets the information and Edge restarts without warning. Maybe it would be better to prompt it on every window. Sincerly JoachimRe: Annoying new welcome message after update to 101beta
Kelly_Y Hi. I dont know how to proper test this behavior. It just happens on major version changes. So IMHO i can test it only on next change from 101 to 102. i will wait until the GPO issue is fixed then i will think about a test solution 😉 Anyway - Happy Easter! See you again next week same place JoachimRe: Annoying new welcome message after update to 101beta
Good Morning Kelly_Y I had a update from Beta 100 to 101. It was auto restarted due to https://docs.microsoft.com/DeployEdge/microsoft-edge-policies#relaunchnotification = 2. All tabs where restored plus the whats new insider page. https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#restoreonstartup is set to 4 and https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#restoreonstartupurls is set to our company intranet But there is still the problem with the only partly working GPO. If this page is not a new function for 101 then maybe the problem comes from Bug: Edge Beta 101 on Start: This policy is blocked - its value will be ignored. JoachimRe: Bug: Edge Beta 101 on Start: This policy is blocked - its value will be ignored.
Hello mkruger i have the same problems as Gunnar-Haslinger. After new start of EdgeBeta a whole bunch of policies are marked as error, ignored According to edge://policy/ its following values: AutoOpenFileTypes HomepageLocation MetricsReportingEnabled NewTabPageLocation NonRemovableProfileEnabled PreventSmartScreenPromptOverride PreventSmartScreenPromptOverrideForFiles RestoreOnStartup RestoreOnStartupURLs SmartScreenAllowListDomains SmartScreenEnabled SmartScreenForTrustedDownloadsEnabled SmartScreenPuaEnabled After releoad policie is looks fine again. This bug needs to be fixed before rollout. Joachim
