(If you checked Skip this page by default sometime in the past, that page will, of course, not appear.) Now, it's time to select the installation type.
For DNS servers, you will be selecting the Role-based or feature-based installation.
I would highly recommend giving this article a read before proceeding with my article: article should still work, but it is definitely not the most efficient way to do an upgrade as pointed out in the technet article above.
My guide essentially goes over cutting over to a completely new ADFS deployment “an upgrade”, side-by-side to your production environment.
If the server is load balanced – You will have to point to the VIP (Virtual IP of the load balancer) Which will be the internet facing server for your Webmail and all other URLs Create a A Record – autodiscover.and point to the Exchange 2013 Server or Exchange 2016 Server .
If the server is load balanced – You will have to point to the VIP (Virtual IP of the load balancer) Which will be the internet facing server for your Webmail and all other URLs Which will serve your outlook and Active Sync phones to send configuration settings automatically.
To setup and configure DNS, one must install the DNS Server Role on Windows Server 2012.
Not only can management of static IP addresses become time consuming, but such management also increases the chances of misconfigured parameters.Create a MX record – and point to the A record you created above for small businesses Which will serve your mail flow if you are going to use any Cloud based anti – spam or Anti-Spam Appliances .you will have to point it to their DNS Records or your Anti-spam Appliances.NOTE: Prior to writing this article I had only found limited documentation provided by Microsoft on a proper upgrade path for this.Since then, it apperas that tools had been included with the Server 2012 installation media which will greatly cutdown on the number of steps needed as well as provide as little downtime as possible.