Forum Discussion
ConfigureOnPremisesAccountAutoSignIn and Server 2012 R2 Edge Stable 84.0.522.40
- AnonymousSep 07, 2020
Jeffrey_Fronius Great news: the team was able to validate the issue and have now enabled a fix! The new code will be in https://www.microsoftedgeinsider.com/en-us/download 87.0.626.0 and later, allowing you to use the hthttps://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#configureonpremisesaccountautosignin. If you are not having success after trying this on Canary, let me know and I can help you securely submit a histogram to the team.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge
Deleted
Thank you! I'll keep an eye out on this thread.
Jeffrey_Fronius Great news: the team was able to validate the issue and have now enabled a fix! The new code will be in https://www.microsoftedgeinsider.com/en-us/download 87.0.626.0 and later, allowing you to use the hthttps://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#configureonpremisesaccountautosignin. If you are not having success after trying this on Canary, let me know and I can help you securely submit a histogram to the team.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge
- AnonymousDec 04, 2020
Jeffrey_Fronius Thanks for the follow-up! I've looped back with our Identity team, and confirmed that they saw your feedback. You should be receiving an email in response to it shortly!
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Jeffrey_FroniusDec 04, 2020Brass ContributorDeleted
Hello, checking back on this thread to see if anything further has come out. We'd love to start rolling this feature, however we'd like to avoid having to recreate user profiles if possible! - Jeffrey_FroniusOct 19, 2020Brass Contributor
Deleted
Just curious if anything has come of this since providing the feedback. Thank you!
- mictsiOct 16, 2020Copper Contributor
Deleted Hi, sorry about the delayed response
.
I can gladly say that the latest version includes the fix, tested and validated the feature this morning.
Thank the @edgeTeam. - AnonymousOct 08, 2020
Jeffrey_Fronius Perfect, it sounds like they received it! Thanks again, and I'll let you know if/when the team has insights to share on this.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Jeffrey_FroniusOct 08, 2020Brass Contributor
Deleted I've submitted the feedback with logs for this issue. Thanks!
- AnonymousOct 03, 2020
Jeffrey_Fronius Thank you for posting those! Our Identity team would love to take a further look, if you are willing to submit some logs through our secure in-browser feedback tool (Shift+Alt+I or "..." menu > Help and feedback > Send feedback.) If you're comfortable with gathering the following three logs and submitting them as attachments with diagnostics, that would be great. If you include the string "ConfigureOnPremisesAccountAutoSignInandServer2012R2Edge," that will ensure that we can correctly route your feedback.
Please attach the following to the feedback submission:
A. Histograms
- Open
edge://histograms
page. - Ctrl + S or Right click -> Save as.
- Save as type: Webpage, complete (*htm, *html)
B. Version
- Open
edge://version/?show-variations-cmd
page. - Ctrl + S or Right click -> Save as.
- Save as type: Webpage, complete (*htm, *html)
C. Sign-in internals page
- Open
edge://signin-internals
page on profile with problems. - Ctrl + S or Right click -> Save as.
- Save as type: Webpage, complete (*htm, *html)
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Open
- Jeffrey_FroniusSep 25, 2020Brass Contributor
Deleted
I don't seem to be getting that behavior. In this screenshot, I have BrowserSignin = 0, disabling the policy. This is currently what I have deployed to production. If you need, I can provide a full list of our policies we're applying.
This screenshot is what I see after I set the policies. The on-premise account is not automatically signing in.BrowserSignin = 1
RoamingProfileSupportEnabled = 1
RoamingProfileLocation = \\server\path
ConfigureOnPremisesAccountAutoSignIn = 1This is what I get on a fresh launch where no pre-existing profile exists. I deleted the profile from c:\users\username\appdata\local\microsoft\edge\ and then re-launched it, so this is a newly fresh launch with these policies set. In this case, the on-premise account is signing in automatically.
BrowserSignin = 1RoamingProfileSupportEnabled = 1
RoamingProfileLocation = \\server\path
ConfigureOnPremisesAccountAutoSignIn = 1 - AnonymousSep 23, 2020
Jeffrey_Fronius Here's what the team said, "On-launch, if Microsoft Edge detects that first profile is not signed-in, it will automatically try sign-in. So, if you have a single unsigned in profile, you don't need to delete the user data folder, as it will auto sign-in once you enable policies and launch again."
Hopefully that helps!
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Jeffrey_FroniusSep 23, 2020Brass Contributor
Deleted
Thank you, again! It would be really great if the policy would convert the device's profile to automatic sign in. I'm looking to roll this out to 5000 devices and I'd hate to have to clear out the existing profile to get it to work.
- AnonymousSep 23, 2020
Jeffrey_Fronius Great, I'm glad to hear it worked! And followed up with the team regarding the issue with automatic sign-on with those policies, and will let you know if/when I hear back from them.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Jeffrey_FroniusSep 23, 2020Brass Contributor
Deleted
I've successfully tested this on Server 2012 R2 with Beta 86.0.622.11.
I did notice one other small issue, and if you'd like, I can create a separate thread for it. I'm testing the on-premise sync with the following policies configured.
BrowserSignin
RoamingProfileSupportEnabled
RoamingProfileLocation
ConfigureOnPremisesAccountAutoSignInIf I have a device where these policies are not yet enabled and the device has an Edge profile already, when I apply these policies the device will not perform the automatic browser signin.
If I delete the Edge profile and start cleanly, apply the policies, then launch Edge, the automatic browser signin occurs as expected.
I have several thousand clients where I'm looking to apply this and I'd hate to have to clear out Edge profiles before the setting works.
- AnonymousSep 10, 2020
mictsi Good news: the team confirmed that the fix will be in v86 of the Stable channel, which will be released in ~1 month! (Following your feedback, they did look into backporting to v85, but there were a number of unexpected and confounding factors for that.)
Hopefully that helps! If not, please let us know.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - AnonymousSep 09, 2020
mictsi Thanks for reaching out, and welcome to the MSFT Edge Insider community.
Great question. I asked the team about possibilities and will let you know if/when I hear back from them.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - mictsiSep 09, 2020Copper ContributorDeleted
I validated that the canary version works as expected.
Is it possible to to backport the fix to version 85? We are looking into deploying edge as the default browser to 3000+ w10 machines and this is issue holding back our deployment. - Jeffrey_FroniusSep 08, 2020Brass Contributor
Deleted
Looking forward to v87 going stable! Wonderful!