Now when all the mailboxes have been moved to a new database – TestCompany2016 – that is part of the new DAG2016 we can start configuring Exchange 2016 servers as the new client assess points – the procedure is exactly the same (*) as for Exchange 2013 – you can read it in detail in Part2, Part3, Part4, Part5.
Let’s briefly recap what must be done (at mininum) to allow users to connect to Exch11 and Exch12 instead of Exch1 and Exch2 (or strictly speaking, Exch2 and Exch3 as I had to replace non-functioning Exch1 with Exch3):
- Create the autodiscover site on Exch11 and Exch12 and set the Client Access SERVICE (- NOT the ‘ROLE’!) to point to Exch11 and Exch12.
- Install the same wildcard certificate on Exch11 and Exch12 and assign it to SMTP and IIS.
- Configure external access domain.
- Add the new servers to the SEND connector (optional for one of the two servers if you don’t want the both servers to be able to send mail directly to the Internet).
- Create the new DNS A records for mail.testcompany.com and autodiscover.testcompany.com pointing to 18.104.22.168 and 22.214.171.124 and remove the old ones.
These steps were already explained im my previous articles so I’ll just post the resulting screenshots here.
1-2 Create the autodiscover virtual directory and configure the Client Access SERVICE (not the Client Access ROLE!) – this is the only difference in configuring Exchange Server 2016 comparing Exchange Server 2013.
New-AutodiscoverVirtualDirectory -WebSiteName “Autodiscover.TestCompany.com” -WindowsAuthentication $true
- SetClientAccessService -Identity Exch12 -AutoDiscoverServiceInternalUri https://Autodiscover.TestCompany.com/Autodiscover/Autodiscover.xml
Now I can test a) the Outlook Web Access (now known as Outlook that makes it rather difficult to distinguish between browser-based Outlook and its application counerpart) and b) Outlook 2013.
At this stage it’s already possible to proceed to unistalling Exchange Server 2013 from Exch2 and Exch3(Exch1) and optionally reusing those old server computers.