System Administrator

Paul Walsh

<div>
Hi Mas,<br><br>I managed to fix the issue myself. Looks like I need to restart the Autodiscvoer App Pool and the RPC APP pool in IIS. Within a few minutes of doing this, all was fine. Ill do some further testing to see if I only have to do this the once, or after every migrated mailbox.<br><br>Thank for replying however and so quickly. Very much appreciated.
</div>


<div>
No need RPC restart the Autodiscover pool is more than enough.<br>Ths is a bug of MS
</div>


<div>
I have updated the comment after few min.<br><br>
</div>


<div>
<div class="content wysiwyg-content fr-view">
Hi Experts,<br><br>In the lab I have completed an Exchange 2010 - 2016 migration ahead of doing it live in production. I setup split DNS, configured Exchange 2016, changed the DNS records to point to the new server for mail and autodiscover and I am at the point of migrating mailboxes.Using Outlook 2016, if the mailbox is on the Exchange 2010 Server, it works. If I run a Test email configuration it shows that autodiscover is on the old server. Shouldnt this show the new server? If I migrate the mailbox over to 2016, Outlook 2016 wont connect to the Exchange server and if i run the same autoconfig test, autodiscover fails. If I try to create a new mail profile, it will crash Outlook. A brand new user with new mailbox on Exchange 2016 works fine, no issues. I have migrated the arbitration mailboxes. I can ping autodiscover and it resolves to the correct IP address / NSlookup resolves correctly as well. Both basic and NTLM authentication is set on the autodiscover Virtual Directory. &nbsp;OWA works fine. <br><br>Any ideas?<br><br>Cheers,<br>Paul
</div>
</div>



Hi Experts,
In the lab I have completed an Exchange 2010 - 2016 migration ahead of doing it live in production. I setup split DNS, configured Exchange 2016, changed the DNS records to point to the new server for mail and autodiscover and I am at the point of migrating mailboxes.Using Outlook 2016, if the mailbox is on the Exchange 2010 Server, it works. If I run a Test email configuration it shows that autodiscover is on the old server. Shouldnt this show the new server? If I migrate the mailbox over to 2016, Outlook 2016 wont connect to the Exchange server and if i run the same autoconfig test, autodiscover fails. If I try to create a new mail profile, it will crash Outlook. A brand new user with new mailbox on Exchange 2016 works fine, no issues. I have migrated the arbitration mailboxes. I can ping autodiscover and it resolves to the correct IP address / NSlookup resolves correctly as well. Both basic and NTLM authentication is set on the autodiscover Virtual Directory.  OWA works fine.
Any ideas?
Cheers,
Paul

Exchange 2016 Migration Connection Issues

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.