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

autodiscover

$
0
0

I've mostly completed a successful coexistence/migration from EX2010 to EX2013 for a small test-environment.

One of the issues that I'm quite puzzled with is when configuring an Outlook client using AutoDiscover.  Instead of the expected local FQDN of the CAS, the 'Server-name' gets populated with what looks like a GUID(f8a4ed0f-24c1-487f-7709-1031ed808516@[mail.EXT-FQDN.com]) and the proxy-addresses get populated with *internal* DNS-names([svr-FQDN.local]/msstd:[svr-FQDN.local]).

I have to manually change the proxy addresses, and then the Outlook client works just fine...even with the existing strange GUID-looking server-name in place.

I've verified that the OutlookAnywhere settings in ECP contain the correct FQDN's for both external & internal host-names...I even changed them both to be external FQDN's since I have split-brain DNS in-place thinking that might help the cause.

thanks in advance for any/all insight to this odd little problem,

~~Rob


thx, ~~Robb


Viewing all articles
Browse latest Browse all 7129

Trending Articles



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