Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2013 autodiscover returned Namespace for OAB is not what I expected

$
0
0

Hello,

I've installed Exchange 2013 in an Exchange 2007 environment.  I have Exchange 2013 servers (CU5) in 2 AD sites (US and UK) and I'm connecting with Outlook 2013 internally via Outlook Anywhere.  Our main site is in the US and secondary site is in the UK.  I've created two namespaces - mail.domain.com for the US and mailUK.domain.com for for the UK.  I've set up the OWA, ECP, OAB, Outlook Anywhere and AutodiscoverInternalUri to use these.  The names point to a E2013 server and not E2007.  I also have a second OAB generated in the UK site.  When I'm on a UK workstation, in the UK AD site and on a domain joined machine (SCP lookup), I start outlook and run the test email autoconfig, it returns the correct namespaces for EWS, OOF and UM but the OAB is pointing to the US namespace.  For example:

Availability Server: https://mailuk.domain.com/ews.Exchange.asmx

OOF URL: https://mailuk.domain.com/ews/Exchange.asmx

OAB URL: https://mail.domain.com/oab/OabGuid

UM URL: https://mailluk.domain.com/ews/UM2007Legacy.asmx

The GUID for the OAB is correct (UK OAB) but it's connecting to the US server and coming back to the UK server for the OAB.  The US databases are configured with a different OAB than the UK databases.  It looks like autodiscover is returning an internal OAB URL from one of the US servers.

Doesn't autodiscover return the OAB URL based on the location of the mailbox (UK) and the OAB GUID?  Can anyone see something that I'm missing?

Thanks


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>