Need to config O365 client to attach to local exchange server

Dstp7334
Dstp7334 used Ask the Experts™
on
Customer is using a Exchange 2016 server on a small network.  Everything was working great until they decided to install Office365 client on the Boss's workstation.  The Outlook client decided to set itself up as a remote to Office365 instead of directly to Exchange 2016.  The Office365 people are baffled but offer no solution other than to contact premier support.  Hesitant to install Office365 client on any other desktops
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
IT Engineer
Distinguished Expert 2017
Commented:
I think it must be something not 100% right with your local domain DNS.
Double check setting.
If your Exchange 2016 is inside your company make sure your internal DNS is pointing to your local exchange.
You did not specified what domain is register in your local network and if is different from public domain name, if yes, just simply create revers lookup zone with your:

exchange.domain.com
autodiscover.domain.com

in your local DNS and point A record to Exchange server in your local network
Most Valuable Expert 2015
Distinguished Expert 2018

Commented:
This is a new "feature" in Outlook that configures the Office 365 account with priority, if one exists of course. You can disable it by toggling the ExcludeExplicitO365Endpoint key, as detailed here: https://support.microsoft.com/en-us/help/3211279/outlook-2016-implementation-of-autodiscover

Author

Commented:
I tried it but it didn't work.  The old exchange server was 10.0.0.251, the new one is 10.0.0.250 - autodiscover was set to the old server, I changed it to the new server and added the ExcludeExplicitO365Endpoint key and am still not able to receive emails.  They are going to the exchange server but the O365 client is reading from the cloud

Author

Commented:
I think it was originally a autodiscover dns record pointing to the wrong server.  I had to flush the records and re-register dns on the work station, then I had to go into Credential Manager and remove any references to o365 and it finally worked.,  This was a lot of hassle for what worked perfect in other versions of Office.  Thanks for the input.

Author

Commented:
Thanks for all the help - there doesn't appear to be a lot of info out there and the O365 support team basically told me to buy premium support.  

I did add ExcludeExplicitO365Endpoint and ExcludeHTTPRedirect to the autodiscover registry location, neither did anything and nothing worked until I fixed autodiscover and deleted the credentials

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial