Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Serge Caron

Autodiscover issue after migration from Exchange 2010 (SBS 2011) to Exchange 2016

Greetings!

I just ran trough a "perfect" migration from Exchange 2010 to 2016: no error messages, etc. Exchange 2010 was uninstalled from SBS 2011 without any issue.
 
External autodiscover works as expected.
 
Internal autodiscover somehow picks up an old URL.
 
The SCP can be verified in Exchange 2016 :
 
[PS] E:\Notes>Get-ClientAccessService | fl AutodiscoverServiceInternalUri
 
AutoDiscoverServiceInternalUri : https://postoffice.(domain.tld)/Autodiscover/Autodiscover.xml
 
where "postoffice" is the hostname of the Exchange 2016 server: this is what is expected.
 
Every virtual directory in Exchange 2016 is setup with the above URL.
 
Using Ctrl-RightClick on the Outlook icon in the notification area, "Test Email AutoConfiguration..." works with the following quirk:

Immediately after the line "Autoconfiguration has strated, this may take up to a minute", there is a popup to connect to a Microsoft account: cancelling this window yields a "Allow this website to configure user@(domain.tld) server settings ?" and the URL provided in this window is
 
"https://SBS2011RWW.(domain.tld)/autodiscover/autodiscover.xml"

with the comment "Your account was redirected to this website for settings."

Cancelling this second window yields the proper autoconfiguration results.
 
Now, why is Outlook 2106 suddenly wants to connect to a Microsoft account when it was installed years ago? And where does this client pick up the URL for the SBS 2011 web site (which is still active, by the way, even if it is being phased out) ?
 
We can observe that Outllok 2016 on workstations stop with the status "Need password" : double clicking twice on the status, Outlook reconnects to Exchange server 2016 without any issue. There seems to be no constant in the frequency of these requests.
 
This is NOT an hybrid migration and I have verified that this was not started by mistake: these clients have no reasons to connect to a Microsoft account and all have been properly activated long ago.
 
This is a major annoyance even if the rest of the migration is picture perfect ;-(. I will be grateful for any thoughts on this issue ;-)
 
Regards,
 
 
 
asked08/22/2019 18:24
364 views
Add Comment
Serge Caron

Greetings!

For those who will face the same issue: autodiscover for an internal domain client still involves a request on the EXTERNAL DNS server. In my case, a SRV record was still pointing to the SBS 2011 / Exchange 2010 server.

Updating the SRV record solves the issue where the wrong URL is used at the start of the autodiscover search.

Nevertheless, I still get the popup Window requesting for a Microsoft login while none is required.

So I am halfway there ;-)

Regards,

 

Serge Caron

Greetings again,

This appears to be version specific. Microsoft Office 2016 forces the Office 365 endpoint on affected machines unless

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover has a DWORD value ExcludeExplicitO365Endpoint with a non-zero value.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\RedirectServers has a list of domain autodiscover overrides in the form "server.domain.tld" REG_NONE zero-length binary values. This will override the autodiscover for domain.tld and you may be stuck with an older server name instead of the shiny new install that you just put in service. Delete/rename the sad thing and get your life back.

Regards,

replied 08/22/2019 21:45
Reply
Last Activity 08/30/2019 12:35

No answers found

Add an Answer