Exchange 2013 - AD SCP Lookup with mismatched UPN and Primary SMTP

Hi Everyone,

I have inherited a few old domains that are .local, but the primary email domains are .com.

When performing a "Test E-Mail AutoConfiguration" using the primary SMTP address which is automatically populated internally on the domains, I receive the following errors:

GetLastError =0; httpStatus=401

GetLastError =0; httpStatus=200

However, if I use the UPN, I receive the correct SCP record as it authenticates properly.

Without adding the primary SMTP domain to AD and modifying all the users' UPNs. 

Are there any alternatives or fixes?

September 14th, 2015 7:17pm

The UPN and email address not matching shouldn't matter.

Are the clients on the domain?

Is the Autodiscover value populated correctly on the Client Access Server?

Simon.

Free Windows Admin Tool Kit Click here and download it now
September 14th, 2015 7:29pm

Yes, the clients are domain joined.

I have not changed the internal URLs of autodiscover per http://blogs.technet.com/b/rmilne/archive/2013/04/02/busting-the-set-autodiscovervirtualdirectory-myth.aspx, but the CAS URIs are set to their associated site name.

The URIs are set to the com domain names rather than the .local. (eg, https://mail.contoso.com/Autodiscover/Autodiscover.xml).

It seems the URLs are set correctly as they work when I use the UPN for authentication rather than the email address.

September 14th, 2015 8:36pm

It is definitely not necessary to match your SMTP domain and AD domain. User's primary SMTP address and UPN can be in different domain.

If you're using SCP, it should work without any customization. But you mentioned the behavior is domain dependent. Looks like Outlook is using DNS instead of SCP. Can you post the entire AutoDiscover log here?


  • Edited by Li Zhen 4 hours 50 minutes ago
September 14th, 2015 10:33pm