Something Went Wrong Try Again When Adding Security Key
"Something went incorrect" when configuring Outlook
Just had an outcome where new Outlook contour creation would fail on a machine.
Autodiscover was configured correctly and working, but new profile creations would fail. The error below would show upwardly every time.
Something went wrong.
Something went wrong and Outlook couldn't setup your account. Please attempt again. If the problem continues, contact your email administrator.
Eventually I noticed that the login prompt window was appearing for a fraction of a second then disappearing.
I ready the registry cardinal beneath, restarted Outlook and I was able to get the auth prompt which allowed the contour to get created.
HKEY_CURRENT_USER\Software\Microsoft\Office\xvi.0\Common\Identity
DisableADALatopWAMOverride = dword:00000001
One the profile is created you can delete the reg key since the account is already authenticated. I accept besides used this reg key to actuate role when it shows like symptoms (login prompt appears for a split second and then disappears). Enabling this primal may or may not pause 2FA support.
Popular posts from this web log
Best Practices for Deploying User Profile Disks
Last Updated 2020-01-03 After months of testing I recommend deploying FSLogix Profile Containers instead of User Contour Disks. You can find my guide here . Some of the items below apply to FSL Profile Containers. User Profile Disks (UPDs) are swell for load balanced RDS farms since it allows users to seamlessly roam from server to server. The goal of this commodity will be to configure the RDS and file servers in a way that maximizes performance and reduces the likelihood of UPD disconnects. I'll go along this updated any fourth dimension I observe new improvements. Use FSLogix Earlier you fifty-fifty consider deploying UPDs you demand to be aware of this limitation . On Server 2012 and 2022 (Server 2022 does not accept this upshot, but it doesn't support Function ) the Windows Search index is automobile broad. This means that when a UPD is disconnected the user'due south index data is deleted. The result is that the next time the user logs into the RDS and opens Outlook their search index will demand to rebui
FSLogix Troubleshooting guide
This article volition cover some common problems I have ran into, and steps on how to resolve them. The guide should be followed in guild since most of the advanced items are normally not the cause of a problem. If you lot but set up FSLogix, make sure that y'all followed every step nether Deploying FSLogix Role 365 Containers and Deploying FSLogix Profile Containers Terminology ODFC = Role Data File Containers This is there Office (Outlook, Teams, Licensing) data is stored This can be used in conjunction with UPDs FSL Profiles Replacement for UPDs User profiles are stored hither (Office information is stored in the ODFC) Cannot be used in conjunction with UPDs Not-Issues The items below should be ignored when troubleshooting Local_ files nether C:\Users If FSLogix profiles are enabled, these folders can be ignored. They will exist deleted the side by side fourth dimension the user signs in. Basic Checks Before troubleshooting any specific items you need to verify that all of thursday
Deploying FSLogix Office 365 Containers
Updated 2020-04-27 This search portion of this guide does non apply to Server 2022 since it should roam the Windows search out of the box . However, you can still configure FSLogix to store Office 365 data. In my feel it is best to avoid mixing FSLogix and UPDs. My recommendation is to get with FSLogix Profiles and FSLogix ODFC. If you have dealt with User Profile Disks and Function 365 then you might know nigh the issues with search indexing. Every fourth dimension a user signs out of the RDS their alphabetize is cleared and it has to be rebuilt the next time they sign in. The index will never fully rebuild one time you have v+ users on the server since it throttles itself. Recently I discovered FSLogix which resolves this issue with minimal configuration. FSLogix creates its own UPD that it uses to store Outlook, OneDrive, and search alphabetize data. It and so tricks Windows into thinking that it is stored on the local auto rather than on a UPD. The result is the index working immediately for al
Source: https://www.amorales.org/2019/10/something-went-wrong-when-configuring.html
0 Response to "Something Went Wrong Try Again When Adding Security Key"
Post a Comment