Outlook 2016

I want to migrate from exchange 2010 to office365 and have now updated my autodiscover DNS entry.

After removing mail accounts and adding them back in,  phones and other devices switch fine after the DNS change,

however; Outlook 2016 on prem still always points itself to our exchange servers. I've tried removing all profile data in case it had the autodiscover cached somewhere but now i'm wondering if it is an exchange 2010 / domain type setting.
My domain controllers are Server 2008 + 2012 in case that matters.
Can anyone help me out?

Thanks very much.
Who is Participating?
jamiegfConnect With a Mentor Author Commented:
Have now resolved this.
The solution is from here:

And for those who hate a link (or if it goes dead)

The reason:
Outlook uses SCP (Service Connection Point) to autodiscover your local exchange server before it tries DNS

The solution:
Add: ExcludeScpLookup=dword:1
(This is for Outlook 2010, Outlook 2013 and Outlook 2007 will be the different area such as xxx\15.0\xxxx)

You can also delete the SCP record altogether using ASDI edit:

Select the “Configuration” naming context
Drill down to:
CN=Microsoft Exchange\
CN=<Your Org name>\
CN=Administrative Groups\
CN=Exchange Administrative Groups\
CN=<Your Server Name>\
And delete the CN=<Your Server Name> of class serviceConnectionPoint in there
Todd NelsonSystems EngineerCommented:
What method of migration did you perform ... cutover, staged or hybrid?
Loretta HarrisCommented:
Is it possible there is still in entry to your old Exchange 2010 server in your internal DNS server?
Also I believe we had to create a CNAME record for autodiscover and a CNAME for the msoid host for Office 365.

Hope this helps.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

jamiegfAuthor Commented:
Hi Todd. I am using a Hybrid method as I need to keep a few domains on here (whilst i figure out how to get this right).
So far I've just used the migration wizard in the "Admin" part of office365.  Its has worked okay for devices not on our domain in our office.

Hi Loretta. If i ping (from inside our network) autodiscover.mydomain.com it pings the right place as opposed to our exchange boxes. So the DNS entries are looking to be right. Also, our mobile devices work okay on the same network wirelessly. I am only being requested to set up 3 entries (MX, TXT and CNAME for autodiscover) in the domains section.
Todd NelsonSystems EngineerCommented:
Typically, you should not make changes to the autodiscover (CNAME or A) or MX records until after all of the mailboxes for a specific domain have been migrated to EXO.  The same holds true for the autodiscoverinternalserviceuri setting in Exchange.

I guess I'm curious about the Outlook profile still pointing to on premises statement you made.  After migrating an on premises mailbox to EXO, the Outlook reconfiguration should be seamless.  Does the Outlook profile have on premises mailboxes it is still connecting to?  If it does, then the profile will still point on premises for those specific mailboxes.
Loretta HarrisCommented:
Agree with Todd's comments.  I also wonder if all the old profile data has been removed.  Have you tried manually entering the settings in the profile rather than letting autodiscover handle it (not ideal, but may be worth a try)?
jamiegfAuthor Commented:
This fixed my issue
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.

All Courses

From novice to tech pro — start learning today.