Ensure the information you enter is correct and then select " Next."Ĩ. The next window will prompt you to enter your email address for your Outlook account. Rename the new profile (the name of the new profile does not matter). Select " Add" located at the bottom of the white text box.Ħ. Select " Show Profiles" near the bottom of the window.ĥ. Select the option that says “ Mail (Microsoft Outlook 2016).”Ĥ. Navigate to the search bar on the top right of the Control Panel and enter in " Mail."ģ. Open the Control Panel by searching for the application in the Microsoft search bar near Cortana. Ensure that Outlook is completely closed.Ģ. Protip: you can open Outlook into an empty profile with no email by runningOutlook.exe /PIM NoMail This will provision a new profile "NoMail" to use Outlook as a "Personal Information Manager" (PIM) .This document details how to recreate an Outlook profile when you have syncing issues.ġ. Note: Opening the Autoconfiguration test requires Outlook to already be open, but if you are having trouble configuring the email account, you may not be able to get far enough to try running the tool. However, the Outlook Autoconfiguration Test DOES test these on-premise problems as well. The Remote-Analysis site cannot test your on-premise DNS, or check your Active Directory for an SCP record that might be getting in the way - neither would Fiddler. I would recommend to use either the builtin Outlook Autoconfiguration Test and the Microsoft Remote Connectivity Analyzer (particularly the Outlook Connectivity test and the Exchange Online Custom Domain DNS Connectivity Test). Just wanted to throw out there that Fiddler is probably not the best way to test AutoDiscover. Have you tried to clear the Windows Credential Cache?Īnything broken with Autodiscover - Fiddler usually helps here.Outlook will show a nice Password Required message in this case.
Any conditional access policy set for Exchange Online? For example, which blocks basic authN or modern authN clients.Tried Microsoft Support and Recovery Assistant.Anything broken with Autodiscover - Fiddler usually helps here.Any error messages in the Windows 10 - Event Viewer - Application and Services Logs / Microsoft / Windows / AAD?.have not tested with Win 10 1903.or the combination you posted. Setting DisableADALaTopWAMOverride becomes a problem for example with "older" Win 10 builds aka 1809 and with Outlook OfficeProPlus 1908 and newer.Key.maybe just the keys, without any user identity values. Would be great if you can post at least parts of theĬomputer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity is OWA working / Browser / and or the other MS apps - Word/PowerPoint etc `? do you have AAD joined or hybrid joined clients? do you run cloud only authentication or federated authentication?
0 kommentar(er)
