User Profile
Thomas_Gessert
Copper Contributor
Joined May 20, 2019
User Widgets
Recent Discussions
Re: Dev channel update to 85.0.545.0 is live
josh_bodner In my understanding every GPO related to MS Edge Chromium is interpreted by all editions in the same way. The configuration of Edge is done for all our users and systems solely by GPO in AD. We are using an 2FA authorisation service for several insurance company extranet websites that behaves different in Edge Chromium Enterprise Stable 83.0.478.45 in comparison to Edge Chromium Enterprise Dev 85.0.545.0. In Stable its working, in Dev is not anymore. In fact, this is not the first version of Dev with this behavior. First reports came in a few weeks ago. The login page is at https://www.einfach-einmal-einloggen.de/ and relays the user after successful authorization to the URL https://portal.easy-login.de/auth-portal/easy-login/secure/linklist.xhtml by opening a new tab. In Dev this tab is not opened and no message appears in any way. For sure its not a popup blocker case because we made a exception entry for this domain. Big question, is it a bug or a feature that will go over to Stable after a few weeks if it's not configured correctly? Good job so far, we happily replaced Google Chrome on all our systems!11KViews0likes1CommentRe: Dev channel update to 81.0.416.3 is live
josh_bodner Finally I found out what to do to sync favorites and what is the showstopper to it. We have a local AD connected to AzureAD. I've learned that all users need to have Enterprise State Roam enabled in AzureAD. Edge is configured via GPO to automatically sign the user (Browser Sign-In enabled, Proactive Authentication enabled). Still on most devices I wondered why edge shows that sync is disabled for this account. With this settings Edge creates per default a new profile with the account name "<local domain>\<username>" (local account) instead of "<username>@<domain>" (connected Microsoft business account used for M365 apps). Profiles with the this account name (local user) aren't synced. This needs to be replaced by a manually created profile with selecting the Microsoft business account to enable sync. Nothing I can tell every user to do. In the local AD the account name is set to the version with "<username>@<domain>". Is there any option to tell Edge to use the "<username>@<domain>" business account for profile creation and sign-in? One addition: I've noticed that in the past one of the Edge Dev Version created a folder on OneDrive for the Collections. It seems that this isn't done anymore, correct? Or does it happen only under special circumstances?10KViews0likes4CommentsRe: *UPDATED* Dev channel update to 78.0.262.0 is live
josh_bodner We use Edge with the ADMX templates for managing pop-up settings. Default setting is all pop-ups blocked and a list of websites for allow. When using a website with pop-ups, for example http://www.popuptest.com, you get the symbol in the address bar "pop-ups were blocked on this page". After clicking on it, you get a context windows with two option buttons, but its impossible to switch to "always allows pop-ups and redirects from ...". What is possible, is clicking the button "Manage" and add the domain manually. I guess it's an error because it works with same settings in Chrome.4.2KViews0likes0CommentsRe: Dev channel update to 78.0.249.1 is live
josh_bodner I like to see Edge going forward and I use it regularly in business and at home, usually without any problems in my use cases. But for use as standard browser in our company there is one showstopper: We have one extension provided by an cooperative for their members for Chrome via Chrome Web Store. At the moment we use Chrome as standard browser and I can force the installation of this extension for our employees via GPO - but not in Edge (copied settings from Google Chrome ADMX to Edge ADMX). This extension can't be found in Chrome Web Store via manual search, so this is the only way to do it. Please add the feature to force install of extensions from Chrome Web Store too. Eric_Lawrence thank you for your fast response. I have to admit, in the end it was my fault. While processing your request for details I found out that the policy definitions work fine and there was a problem with deploying the latest version of the policies to the workstations. Thank you for guiding me in the right direction. I tried it on several workstations and our terminal server farm and it works now.3.2KViews0likes1Comment
Recent Blog Articles
No content to show