Guess I'll just give the new server a new name then. 8^)

Has to be another site, private cloud.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Michael B. Smith
Sent: Friday, February 14, 2014 5:48 PM
To: [email protected]
Subject: [Exchange] RE: exch2013 <-> exch2007 legacy redirects

I'm referring to placing the servers in different sites.

I can tell you that probably 99% of testing was done in single-site redirect 
scenarios.

And Androids? Fuhgedaboutit. They will give you ulcers. MANY Android releases 
do not properly understand either the 302 redirect or the 451 redirect that EAS 
uses.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Rick Berry
Sent: Friday, February 14, 2014 5:34 PM
To: '[email protected]'
Subject: [Exchange] RE: exch2013 <-> exch2007 legacy redirects

By difficult, do you mean my choice of 2013 vs 2010, or messing around with 
legacy redirect in general, or something else? 8^)

I just don't want to have to listen to a billion phone calls about 'why isn't 
my android working' when I change the IP behind their external URL and pray for 
the legacy redirect to work

Perhaps I'm being optimistic or naïve.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Michael B. Smith
Sent: Friday, February 14, 2014 4:21 PM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] RE: exch2013 <-> exch2007 legacy redirects

I think it will work, except for SSO.

That being said, why are you making life difficult on yourself? :P

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Rick Berry
Sent: Friday, February 14, 2014 4:11 PM
To: '[email protected]'
Subject: [Exchange] exch2013 <-> exch2007 legacy redirects

Have Exch2007 sitting in 'site A', premise server, patched to latest, on 
Windows Server 2008.

Have Exch2013 sitting on VM in 'site b', different IP range of course, but 
reachable from inside/outside network.  Running CU3 on Server 2012.

Does legacy redirect work ok between two different sites?

I ask because I read some forum items about folks struggling with it and they 
were on the same network segment, I'm wondering if I'm inviting problems/PSS 
call if I try this to two different subnets.  I control DNS with really short 
public TTLs so it's not end of the world if I trial and error a bit, but what I 
read in prep for this new Exchange server scared me a wee bit.

-Rick




Reply via email to