Solved

Exchange 2010 - 2013 Co-existence

Posted on 2013-06-20
6
702 Views
Last Modified: 2013-06-25
Hi Experts,

I have recently installed Exchange 2013 into an Exchange 2010 environment using the Microsoft Exch Deployment 'guide'

Everything has gone successfully and the servers can see each other, I have also successfully done a pilot migration of one user to the Exchange 2013 server.

Setup as follow for reference.

Exch 2010 internal address - mailserver.domain.co.za
Exch 2010 external address - exchange.domain.co.za

Exch 2013 internal address - exchange.domain.co.za
Exch 2013 external address - exchange.domain.co.za

3rd Party SSL cert SAN - exchange.domain.co.za

My question is, how the hell do you get the servers to work together properly?

The mail flow is fine, mail is flowing in and out through the 2010 server, but things like Outlook anywhere, Mobile devices, owa ect aren't redirecting the mailboxes.

My 'remote' address is exchange.domain.co.za and that is currently pointing to the Exchange 2010 server, but when I try connect a user on the exchange 2013 server to exchange.domian.co.za (for mobile setup, owa and outlook anywhere) it says the mailbox is unavailable or doesnt exist (becuase from what I can see the exchange 2010 isnt forwarding the request to the 2013 server)

I remember during 2003 -2010 migrations, this used to work well.

What do I need to do to get the co-existence to work using 1 FQDN exchange.domain.co.za

Basically, I want all requests to hit the Exchange 2010 server, and then if it realises the mailbox is on the exchange 2013 server, do the relevent redirects.

Thank you
Daniel
0
Comment
Question by:gerard_thusa
  • 3
  • 2
6 Comments
 
LVL 12

Expert Comment

by:Imtiaz Hasham
ID: 39261789
I am in the same boat, if the OWA points to the new server and the mailbox is on the old server, it won't work.

If you haven't done your migration yet, you should keep port 443 to the old mailserver.
0
 

Author Comment

by:gerard_thusa
ID: 39261800
Yes, all my ports are forwarded to the old server still, because 99% of the people are still on there, but I don't want to move people off because then only users on 1 server will be able to work remotely, just doesn't make sense to me ?

I want exchange to work whether you are on the old server or the new server, using the same SAN name :-/
0
 
LVL 12

Expert Comment

by:Imtiaz Hasham
ID: 39261812
The issue is there is no way I know to redirect requests to exchange 2013.
0
Do email signature updates give you a headache?

Do you feel like you are constantly making changes to email signatures? Are the images not formatting how you want them to? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today.

 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39262173
You need two different URLs, with two different IP addresses. You cannot use a single host name for everything.

Therefore the usual method is to have all traffic go to Exchange 2013, then configure a legacy host name for Exchange 2010. Exchange will then redirect the client to the other server if required. Currently at the moment you are creating a loop - the client is told to connect to the same URL that is already connected to.

Simon.
0
 

Accepted Solution

by:
gerard_thusa earned 0 total points
ID: 39262242
Hi,

I got it to work, by changing my port forwards to make the new exchange 2013 server the main front end server, the redirection works to the old server.

It seems that the redirection will only work if you are logging onto the exchange 2013 server and then redirecting users to 2010, not the other way round
0
 

Author Closing Comment

by:gerard_thusa
ID: 39274215
I fixed the issue myself
0

Featured Post

The problems with reply email signatures

Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

746 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now