• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 425
  • Last Modified:

Moved from local Exchange 2007 to Exchange Online (O365) Old local SSL cert still pops up in Outlook.

We have recently moved to O365 for email. Our on premises Exchange 2007 box is still up and running for some internal email processing (a copier, and some industrial machinery that is behind the times).

All of the Outlook installs have a new profile configured for O365. Now and again, an SSL warning pops up in Outlook for the local Exchange server. How can I make Outlook forget this exists?


  • 2
1 Solution
David Johnson, CD, MVPOwnerCommented:
you've updated your mx and autodiscover records?
Tom_BombaciAuthor Commented:
Yes. I have changed the autodiscover cname in my local DNS to point to the outlook.com servers as well as the MX record.

Actually, the local domain name is xxxx.local and I have an added DNS entry for xxxx.com I only added the autodiscover to the xxxx.com DNS entry. Do I need to add it to the xxxx.local as well?
Simon Butler (Sembee)ConsultantCommented:
The clients are still querying the domain for Autodiscover information. That is because you still have the Exchange 2007 server in place. While that is in place you cannot stop them from doing that. Autodiscover DNS records aren't going to help because they don't use them.

Two things to do here.
1. Remove the Exchange 2007 server and replace it with an IIS SMTP server to do the email processing. That will save you from having to patch the Exchange 2007 server to maintain it.

2. Change the Autodiscover value you can see here:
get-clientaccessserver | select identity, autodiscoverserviceinternaluri to point to the host name you have been told to use for Autodiscover for Office365. That way if a client does query the domain they are then pointed to the Office365 installation instead.

Tom_BombaciAuthor Commented:
Thank you. That explains why I couldn't configure Outlook locally without using config365.com

Thank you again!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now