<div>
in IIS Autodiscover and Microsoft Server-Active sync edit the basic authentication put a \ in the default domain and your NetBIOS domain name in the Realm ie Microsoft if the internal domain is Microsoft.com<br />
Make sure the domain is in CAPS inside Realm<br />
Restart IIS after you save the changes<br />
command to reset IIS- &nbsp; &nbsp;“IISRESET /NOFORCE /TIMEOUT:120”<br />
<br />
also the user logon(UPN) name must match the email address for IOS devices to not ask for the server, domain etc...<br />
<br />
re link: <a href="http://msexchangeguru.com/2013/08/06/e2013mobiledomain/" rel="ugc">http://msexchangeguru.com/2013/08/06/e2013mobiledomain/</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2020/04_w17/1450837/basicauthentication.JPG" target="_blank" class="file-inline" title="PUT REALM IN ALL CAPS -BASIC AUTHENTICATION SETTING (21 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>basicauthentication.JPG</a>
</div>


PUT REALM IN ALL CAPS -BASIC AUTHENTICATION SETTING

basicauthentication.JPG

<div>
Thanks - no sure to 100% follow your response here.<br />
<br />
I guess you are referring to the IIS running on the Exchange server I don't want to use ... ? Why would Outllook actually &quot;talk&quot; to that server if nothing in the DNS points to it ? And if nothing points to it and Outlook doesn't talk to it how would any change to IIS on that machine be whatsoever relevant to the issue at hand ?<br />
<br />
I still want the users using my main domain to find &quot;their&quot; Exchange server if they have a mailbox there. I don't want the user that are using the external, unrelated, Exchange server to end up on the internal one.<br />
<br />
Would you be so kind as to explain the auto-discovery sequence for a domain-joined workstation? Clearly something is being queried (and obtained) even before the &quot;usual&quot; DNS based for the mail domain is being queried. I.e. if I try to setup an e-amail for contoso.com somehow Outlook will find that there is an Exchange server in the domain and will not even try to get the auto-discovery information for contoso.com...
</div>


<div>
Are you trying to just set up an email account on your outlook that is not the company based one?
</div>


<div>
Correct.<br />
<br />
But it &nbsp;_was_ previously handled by our corporate server (it was handling two domains but one has been migrated elsewhere). Some of the domain users have still e-mails on our corporate server with our domain, some have e-mail on the externals server,<br />
<br />
A mentioned I have made sure that our DNS does not resolve anything for said external domain and that our internal Exchange doesn't know anything about that external domain.<br />
<br />
Yet when trying to setup a mailbox to that external domain auto-discovery sends me to the internal server... Obviously I can't complete the setup.
</div>


<div>
In outlook<br />
File&gt;Add account&gt; fill out the user's information and then click MANUAL CONFIGURATION
</div>


<div>
Tried that...<br />
<br />
Enter the external server name then &quot;user&quot; name &nbsp;- check... no go :(<br />
<br />
Interestingly my issue is DNS related. If It temporary use only external resolvers everything works fine - but obviously it won't work for long for my domain-joined computers... And if I set up my account with that again everything works fine... until I restart Outlook, when it stubbornly tries to find the now non-existant mailbox on the internal server...<br />
<br />
I guess I can dig into the network traffic to see what DNS queries are sent (and responded) during the auto-discovery process ...<br />
<br />
There must be some &quot;leftover&quot; in the local DNS that is confusing outlook... just fo the life of me can't find out what.
</div>


<div>
Alexandre, <br />
The only other thing than can be overiding the manual config while the machine is on the network is a GPO setting.<br />
If you are able to manual configure the email account when not connected to the domain it is a GPO that is overriding.
</div>


<div>
aha - that's a something (GPO) that I have not considered - will check (but not right now). Thanks for the pointer
</div>


<div>
Well checked - no GPO. Outlook still finds the old server no matter what. This is getting crazy... <br />
<br />
Again, there is something in the windows domain (not a GPO) that supersedes the public DNS based auto-discovery. 100% certain. I guess there are some AD attributes for the user that are pointing to the old server.<br />
<br />
So my question remains... what is it ??
</div>


Alexandre Takacs

<div>
<blockquote>If migration is done all autodiscover records mentioned in DNS tab in Office 365 portal should be pointed to O356.<br>autodiscover shud not be then pointed to on-premise.<br><br>If you are still using onpremise then this is normal that user domain joined will still look using SCP.</blockquote><br>All DNS records are pointing to external (as mentioned in previous messages)<br><br><blockquote>Also if u have the old exchange server disable client access URI.<br><br>get-clientaccessserver | fl *uri*<br>Set-exchangeserver -autodiscoverinternaluri:$null<br>OR<br>you can delete the SCP object using ADSIEDIT.</blockquote><br>Ok THAT is helping (although your PS would not work on an Exchange 2013 server)<br><br><a href="https://www.cyberdrain.com/how-to-remove-local-autodiscover-when-migrating-to-o365/" rel="ugc">Following these instructions</a> I almost got it working... it is all ok except for a handful of &nbsp;Win7 workstations (yes, migration is underway...).<br><br>Any further idea ?<br><br><br>
</div>


<div>
No 100% solved but as we are phasing out win7 machines I can live with it
</div>


<div>
<div class="content wysiwyg-content">
Getting back to this question <a href="https://www.experts-exchange.com/questions/29179495/Outlook-auto-discovery-for-domain-joined-workstations.html" rel="ugc">about Outlook auto discovery</a><br />
<br />
I <i>thought</i> I had it solved but in fact, it is not the case...<br />
<br />
Everything I mentioned holds true... except that if I turn back the DNS to the domain one Outlook at next launch will connect again to the old server, creating a mess !<br />
<br />
This is a bit crazy. I have checked that <br />

<ul>
<li>our dns do not provide resolution for contoso.com</li>
<li>the (old) exchange server is not anymore authoritative nor holds contoso.com as &quot;accepted domain&quot;</li>
<li>I have (after exporting them) removed the contoso.com mailboxes</li>
</ul>
<br />
yet outlook forgets about it's valid setting and returns to the old server all by itself...
</div>
</div>


Getting back to this question about Outlook auto discovery (https://www.experts-exchange.com/questions/29179495/Outlook-auto-discovery-for-domain-joined-workstations.html)

I thought I had it solved but in fact, it is not the case...

Everything I mentioned holds true... except that if I turn back the DNS to the domain one Outlook at next launch will connect again to the old server, creating a mess !

This is a bit crazy. I have checked that 
our dns do not provide resolution for contoso.com
the (old) exchange server is not anymore authoritative nor holds contoso.com as "accepted domain"
I have (after exporting them) removed the contoso.com mailboxes


yet outlook forgets about it's valid setting and returns to the old server all by itself...

Outlook setup after migration in domain joined workstations

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.

Outlook

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.