Link to home
Start Free TrialLog in
Avatar of liquid101
liquid101Flag for United States of America

asked on

Exchange 2003 to 2010 upgrade networking question

As I understand it, the CAS handles all new traffic for web access during install (OWA, ActiveSync, Outlook Anywhere, etc.).  That being said, I have a network that essentially has a VIP that load balances 2 Exchange 2003 OWA servers that then enter our SPAM filter then onto the Exchange 2003 MBXs.

So if I change the VIP to redirect to the new CAS after install, the old 2003 environment is still active since no mailboxes have been moved, correct?  Essentially the CAS takes the traffic from the VIP, and if the mailbox exists on the 03 servers, it does a URL redirect to "legacy.example.com", right? We have a very large environment and I really need to understand exactly how the routing works before we attempt approval.  I need to be the subject matter expert in a matter of a few weeks.

I hope I explained how it works currently.  I appreciate the assist in advance.

-Carlton
Avatar of praveenkumare_sp
praveenkumare_sp
Flag of India image

u need to do the following(lets assume your current OWA(2003) URL is "mail.example.com")
1) Create a new Public DNS entry like "legacy.example.com" and make it point to where "mail.example.com" is pointing to.

2)Now point "mail.example.com" to your 2010 CAS server

3)Run a command Set-OWAVirtualDirectory -Identity "CAS2010\Owa(Default WEB Site)"  -Exchage2003URL "legacy.example.com"

4) Go have a nap or chill out as your work is done

Note:-IF you point  your VIP to point to CAS(or CAS array) , how will you load balance the Exchange 2003 ? so dont do any of those just follow the above steps
Avatar of liquid101

ASKER

So what about the CAS array?  We do want to Load Balance those as well.  Which is another question.  We don't want to use Windows Load Balancer to create the array.  Does the CAS array tool allow for that or do we just need to Load Balance 2 or more CAS boxes and not worry about the array settings?
ASKER CERTIFIED SOLUTION
Avatar of praveenkumare_sp
praveenkumare_sp
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
My concern is the routing, which I understand a bit better thanks to the link above (THANKS!).  In the current environment, the two OWA boxes are outside of the firewall, which then access the mailboxes inside the firewall.  With the CAS array being behind the firewall, will the URL redirect to the legacy 2003 boxes during the coexistence cause an issue?
No the redirect will work just fine ;P

but understand putting the CAS before the Firewall is not a very good option, do reconsider this architecture
When I say behind the firewall, the CAS will be well within the confines of protected space along with the Mailbox servers.  In the older environment, however, the OWA boxes were in the DMZ as front-end servers used for authentication.
I know but still

what i meant is the below
CAS->Firewall->MBX is not correct

meaning there must be no F/W between Cas and Mbx