Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 4521

Exchange 2013 - 2007 coexistence legacy namespace issues

$
0
0

Got an odd config here. Exchange 2007 CCR mode co-existing with split role 2013 servers over 2 Data Centers. Each DC has its own subnet so DAG has 2 IPs. New Certificate purchased with extra legacy namespace and loaded onto ISA and F5 as well as the exchange servers.

I can send and receive from the Exchange 2013 servers. But I'm struggling to deploy the legacy namespace

Here's where it gets ugly. The client wants to continue (short term) to put legacy.company.com through ISA2006 servers and 2013 traffic through F5 load balancers. On the f5 side the path goes through a firewall then an f5 to the mailgateway

When we cut over to legacy (dns changes etc) OWA suffered intermittent Internal 500 errors. Active sync had to be pointed to webmail to work (we had it set blank as per Steve Goodmans recommendation) and Outlook Anywhere had no connectivity.

Urls were set correctly

  • Outlook Anywhere -> webmail.company.com
  • Autodiscover -> webmail.company.com
  • WebServices -> legacy.company.com
  • OWA -> legacy.company.com
  • OAB -> legacy.company.com
  • UM -> legacy.company.com
  • ActiveSync -> legacy.company.com

This is our 4th attempt to get this working. We can only work in the small hours so we are all fairly tired. Pointers anyone?

 

 


Viewing all articles
Browse latest Browse all 4521

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>