![]() ![]() I opened up Group Policy Management and created a GPO and linked it to my domain.I copied the extracted ADMX and ADML files to GP store on my server 2012 (this will be dependent on your server or PC’s OS).I had to install the Office 2016 Group Policy template located here.HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\ExcludeHttpsRootDomain (set value to 1)Īfter much testing and googling this is how to get Outlook to connect to our Office 365 mailbox when you still have an AD Connected Exchange Server ( it’s not my prettiest solution but it works until you can uninstall your Exchange server): HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity\EnableADAL (set Value to 1) The easy fix is to change the DNS server on the computer trying to connect to Office 365 to 8.8.8.8 and then change it back after it connects but we understand that this won’t always workĪdd these 2 registry entries to try and work around the Exchange issue as well: Until you uninstall Exchange, AD will often hijack your Outlook profile and try to sync your Exchange email profile instead of your Office 365 account So, after migrating everything over and shutting down the Exchange server I ran into the issue that Outlook would get hijacked by active directory and autocomplete or autodiscover the user’s AD and Exchange information and not allow us to input our Office 365 mailbox credentials I ran into the issue where Outlook wouldn’t find our Office 365 mailbox because there was an on-premise exchange server, this happened after we performed a migration from an on-premise Exchange 2010 server to Office 365. ![]() Outlook won’t find Office 365 Mailbox when there is an on premise Exchange Server ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |