?
Solved

Possible to Install Exchange Server 2013 as additional Server to Exchange Server 2010 on single network

Posted on 2015-01-13
3
Medium Priority
?
25 Views
Last Modified: 2016-06-22
As per current scenario we have Exchange 2010 on Hardware machine Which contains Mailbox, Client Access and HUB Transport Roles. now our plan is to install second Exchange Server 2013 ( as redundant/ additional ) on virtual machine.

Existing Exchange 2010 is on single Network and we cannot go for second network, even on Virtual Machine where we are planning to install Exchange 2013 will also be only on the single network ( same subnet as existing server).

now my question is whether we can install second Exchange server 2013 on VM as addition to Exchange 2010 on single network.
0
Comment
Question by:Samizaghloul
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 5

Assisted Solution

by:Robert_Turner
Robert_Turner earned 1000 total points
ID: 40546141
In short, 2010 & 2013 co-existance is certainly possible.  It will be with its challenges.

I personally have never had the 2 side by side any longer than 2 weeks, whether it was SBS or full blown as part of migration, so I personally haven't face long term problems with it, but here is some further reading going into recommended practices and problems people have come across.

http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
http://www.bctechnet.com/exchange-20102013-co-existence-experience/
http://www.techtalklive.org/ttlblog/Pages/Exchange-2010-2013-Coexistence.aspx
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 1000 total points
ID: 40546402
An additional Exchange 2013 is not going to give you any kind of redundancy for the Exchange 2010 server for anything other than the hub transport role. It cannot be a member of the DAG and client access is a mixture of proxy and redirection.
Therefore your best option may well be to install another copy of Exchange 2010 instead, or migrate to Exchange 2013 completely.

Coexistence is not a problem, you just need to have both Exchange 2010 and 2013 with its own external host name and IP address so that any redirection works correctly.
However you will not get Exchange 2013 OWA with Exchange 2010 mailboxes.

Simon.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question