In this article lets have a look at installing exchange 2016 in exchange 2010 coexistence.
Before proceeding with the installation i would like to give a small summary and features of exchange 2016 not a detailed one since there are good articles on the new features of exchange 2016 written by senior MVP’s.
Below are new features of the product :-
One Mailbox role with all the functionality
The mailbox server in exchange 2016 hosts all the components – Client Access protocols, Transport service, Mailbox databases, and Unified Messaging.
The main reason of this design is to simplify the architecture, reducing the hardware dependency by running on a healthy CPU power which is less expensive, and easier way to isolate any issues if we come across.
Edge transport role is coming with RTM
Considering the legacy RPC technology all Outlook connections will be MAPI over HTTP.
By default this is not enabled if you are installing on Exchange 2010/2013 coexistence and you can enabled them.
But if you have this already enabled in Exchange 2013 then it will be enabled.
If you are installing only exchange 2016 then its enabled mapi over http as a default
For further information on the architecture you can go through the below excellent series from MVP Prabhat and tech-net
Now lets go through the installation part
Readiness to be prepared for Exchange 2016 in Exchange 2010 environment :-
. Exchange 2010 SP3 with RU9 should be updated , for all Exchange 2010 servers.
· At least one Windows Server 2008 or higher Global Catalog in each AD site with Exchange installed
· At least one writable Domain Controller in each AD site with Exchange Servers installed (It can be a GC.)
· AD Forest must be Windows Server 2008 Forest Functional Level or higher
· Coexists with Exchange 2010 SP3 RU9 and Exchange 2013 CU7 *may be increased by RTM*
· Outlook for Windows – 2010 or later
· Outlook for Mac – 2011 or later
If you wish to enable mapi/http then you must have atleast outlook 2013 SP1 or later.
Operating System Prerequisites:
· Windows Server 2012 R2 64-bit Standard or Datacenter editions
· .NET framework 4.5.2.
· Windows Management Framework 4.0 .
· Unified Communications Managed API (UCMA) 4.0
Following types are supported
Single label domains
In Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. In the n\w if IPV6 enabled then it will take IPv6 addresses.
Hardware Requirements :
Processor : x64 architecture-based computer with Intel processor that supports Intel 64 architecture
For Mailbox – 8 GB Minimum recommended
Page File – minimum and maximum must be set to physical RAM plus 10 MB
Disk Space – Better to have 50 GB on the drive on which we install the exchange binaries.
Install the prerequisites on the Exchange 2016 server : ( Applies for Windows server 2012R2)
.NET Framework 4.5.2
Click here to download http://www.microsoft.com/en-us/download/details.aspx?id=42642
Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit.
Click here to download http://go.microsoft.com/fwlink/p/?linkId=258269
install the below features
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Download the Setup - http://www.microsoft.com/en-us/download/details.aspx?id=48210 Once the setup is downloaded just open the setup.exe file which will bring you to below screen Installation is pretty much straight forward and it remains the same as exchange 2013 The only change we see here is the role selection part without the CAS role Select mailbox role and proceed next We have the same option as we had in Exchange 2013 It goes through the readiness checks and 15 setup progress one by one same as Exchange 2013 and the setup will finish with the below screen Once the setup completes you get the EAC console like below You can check the coexistence Exchange 2010 and Exchange 2016 version 15.1 And we are done with installing Exchange 2016 in Exchange 2010 coexistence. In future as we get more updates from Microsoft on Exchange 2016 we will explore more on this product. Thanks Sathish Veerapandian MVP - Exchange Server
Hi Sathish! We are planning 2010 and 2016 coexistence. What’s not clear to me that after installing the 2016 server will mail flow stop? And do we need to change dns records right away to 2016 even all users are still in 2010?
Yes tommi you would need to point all of your DNS public and internal records to the Exchange 2016 server and then the e16 will direct the 2010 mailbox requests to the 2010 CAS server
I have deployed 2016 in a coexistence 2010 setting. Everything is working except being able to email to users still on the 2010 server. I get a 441 4.4.1 communication error, connection dropped socket error. Do you have any idea what this could be?
Hi Paul have to redirected all your EWS URL’s to exchange 2016 . Make sure that you enabled outlook anywhere on exchange 2010
nice article..can we use the same namespace for coexistance and same SSL certificate from Exch 2010?
yes you can use the same NameSpace. Shift all the URL’s and IP’s to your new Mailbox exchange 2016 and you can very well use your existing public SSL certificates.
Thanks for your comment
To transition from Exchange 2010 to Exchange 2016, one of the first things you must do is move Autodiscover and webmail to Exchange 2016.
Autodiscover and webmail must point to the Exchange 2016 server.
See step 14.
I believe you’re missing the point of the word coexistence. Coexistence in exchange terms has always focused on server placement and proxy VS redirect. You have none of that knowledge here.
If I add a public facing 2016 server to my existing environment and cutover my old public namespace is 2016 going to proxy access to my 2010 public folders when I start moving mailboxes? How does it handle EAS when the namespace is cutover?
This is a technical document on coexistence: http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
You need to point Autodiscover to the new server.You need to change URLs to point to the new server.
All URL settings on all virtual directories, Outlook Anywhere and Autodiscover should be configured properly on Exchange 2016.
Autodiscover will return the proper information for connection for Exchange 2010 mailboxes based on the database’s RPCClientAccessServer property. Internal clients will connect via a direct MAPI connection to that CAS or CAS array. External clients (Outlook Anywhere) should go through Exchange 2016, which will proxy the requests to the Exchange 2010 server
Outlook uses Autodiscover to connect to Exchange 2010 and 2016, and Autodiscover must point to the Exchange 2016 server for Outlook to connect to Exchange 2016 mailboxes. You’ll need to make sure that it’s properly configured as well as Outlook Anywhere.
Autodiscover and webmail must point to the Exchange 2016 server.
See step 14.
To transition from Exchange 2010 to Exchange 2016, one of the first things you must do is move Autodiscover and webmail to Exchange 2016. Before making that transition, you’re going to want to test that proxy and redirection works as designed.
I have one question on this subject. How will “Public Folders” be handled? I have multiple clients with a lot of Mail Enabled Public Folders and Cals.
Hi You can folow this link applies to Exchange 2016 as well – https://blogs.technet.microsoft.com/exchange/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond/
I have Installed Exchange 2016 in Exchange 2010 Coexistence but Exchange 2016 ECP is not opening after installation. It is automatically redirecting to Exchange 2010 OWA while opening Exchange 2016 ECP. Please assist me to resolve it.
Try the URL modification:
Can we install 2016 in existing 2010 environment and keep it in cold state??
On January 14, 2020, Exchange Server 2010 will achieve end of help. In the event that you haven’t just started your relocation from Exchange 2010 to Office 365 or Exchange 2016, presently’s an ideal opportunity to begin your arranging and migrate all the resources to Exchange 2016
Hello, I don’t know if the website still available, but I would give it a try, I have an issue after upgrading my Exchange 2010 with SP3 and RU 11, one Hub server that was originally setup as a backup server is now acting as the main server. And the webmail is no more working displaying a blank OWA page when browsing to the OWA page.
I’m not sure on this question and Exchange 2010 is out of support.
And may be you can give it a try is there was some customizations done on the OWA virtual directory and they are gone after upgrade Replacing them with that customizations can help to bring them back online.
Can i introduce Exchange 2016 in different AD Site (Branch Office) when an Exchange 2010 SP3 UR30 with 2 EDGE server are in Main Site A (another datacenter) ?
Mail flow continue to work or i need to install Exchange 2016 firstly into Site A ?
I need to kown if mail flow continue to work if i dont change client connectivity to Site B where Exchange 2016 is located and what about EDGE servers, because i know that EDEG servers are AD Site´s dependant, and dont work if Exchange 2016 are located in another site B for example, is that correct ? or i just need to remove EDGE subscritions from Excgange 2010 in Site A, and re subscribe EDGE to Exchange 2016 in site B ?. But i dont understand how mail flow continue to work if MX point to the site A and Exchange 2010 can not proxy up to Exchange 2016, i dont understand how to do it. I need to install Exchnage 2016 in Site B because it have more hardware resources. How can achieve that ? i need some help. Thanks
Since its Exchange 2010 you need to point your CAS URL’s to Exchange 2016.
Since Exchange 2016 does not support down version of Proxy for handling all the connections for Exchange 2016 mailbox servers.
So its recommended to introduce Exchange 2016 in main site to the Client Access shifting to 2016 and then later plan for designing 2016 to other sites.
Thanks for your reply Sathish, i already deployed an Exchange Server 2016 directly into site B (In another location) and its working perfectly. We have not done the CAS switching yet, but i have tested it with success doing quickly and temporary changes into public and private DNS server. As well as previously with changes in Windows HOST file.
CAS proxy works well. I have utilized the same namespace that the old Exchange Server in coexistence. The only issue encountered was with one exchange 2010 migrated test mailbox in wich i had to recreate it outlook profile.
I have a doubt, in which moment i need or if necessary to set all virtual directories to null$ in exchange 2010 ?
And what happens to SCP in Exchange 2010 ?
I need to do all of this after change DNS to point to Exchange 2016 or after when all mailbox is migrated to Exchange 2016 ?
Thanks for your time and help!