Exchange 2003 and Exchange 2010 OWA and DNS

I'm in the process of migrating slowing to Exchange 2010. Right now all of my user access 2003 owa https://server.domain.com/exchange.  I want to cut over to 2010 OWA before I start to move users mailbox what my want 2003 users to use the 2010 OWA. I have alredy read the article on how I can setup 2010 to do this. I have to force all users to use the new OWA name http://webmail.domain.com (please note this is going to me the same name foe internal and external). For example when I cut over to the new OWA server I want user who type in the old DNS address to get redirected to the new OWA address???? How can I do this. I thought about adding a CName record in our external done to point the old OWA address to the CAS 2010 IP. But I know the set-virtualdirectory command reference the old OWA address and I'm afreaif with a DNS CName record this will cauase a loop..

Please advice what do I need to do in DNS
LVL 20
compdigit44Asked:
Who is Participating?
 
Glen KnightConnect With a Mentor Commented:
>>1) Remove current external&internal A records for 2003 owa:  https://server.domain.org/exchange

Correct

>>2) In my internal domain create another A record called legacy.domain.com that points to my 2003 OWA server. Will I need to do anything on my IIS 2003 server?T

You will also need legacy.domain.com in your external DNS, not sure what you mean about the IIS server?

>>3) Create a internal and external CName recorrd the points all old server.domain/com/exchange connectinos to the new webmail.domain.com address..

You could do that, or just change the IP of the existing server.domain.org to be the same as the webmail.domain.com A record.
0
 
Glen KnightCommented:
You need a legacy URL conifigured, OWA 2010 will then redirect to the LegacyURL for Exchange 2003, the users will automatically be redirected to the 2003 server.

You will need to A records in your external DNS webmai.domainname.com and legacy.domainname.com, and 2 IP addresses one for each.
0
 
compdigit44Author Commented:
Thanks for the fast reply.. Ok this is where I get confused.. I already have a external A record for me 2003 OWA called. https://server.domain.com/exchange  - (internal name is: server.child.domain.locall)

Do I keep this A record to remove it?

Everyone keep taking about a LegacyURL do I know in my current 2003 OWA URL or make up a totoally new one?? Confused?

How can I force all conection attempts to the old 2003 OWA to be redirect to the CAS OWA? I want all user to use the CAS server for OWA access
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Glen KnightCommented:
you can keep that URL and then use it as the LegacyURL.

>>How can I force all conection attempts to the old 2003 OWA to be redirect to the CAS OWA?
Not sure I understand this? If you mean when users goto server.domain.com/exchange they automatically get redirected to the CAS server then this isn't possible if you will be using this server for the LegacyURL.

This is one of the reasons why people delete that record and create a legacy.domain.com so that users are then forced to use the new URL.
0
 
compdigit44Author Commented:
OK so you are saying that I can keep the external DNS A record for my 2003 OWA correct???

Then I still need a legacy URL ... Sorry I just not understanding this. It is very confusing
0
 
Glen KnightCommented:
No, what I said, is that you can use the External DNS A record for the 2003 server as the legacy URL.

However, if you do that, you will not be able to stop your users going directly to that URL.
0
 
compdigit44Author Commented:
OK wait  I think I'm getting it...

If I want to force all users to use the CAS server then I need to do the following.

1) Remove current external&internal A records for 2003 owa:  https://server.domain.org/exchange

2) In my internal domain create another A record called legacy.domain.com that points to my 2003 OWA server. Will I need to do anything on my IIS 2003 server?T

3) Create a internal and external CName recorrd the points all old server.domain/com/exchange connectinos to the new webmail.domain.com address..

Am I on the right track?
0
 
compdigit44Author Commented:
Ok I think I'm uninderstaing this now...

so when I remove the 2003 OWA DNS A record and replace it with the new legacy.domain.com this will point to the same 2003 IP correct..

any problems using the name webmail.domain.com for both internal and external access??

Do I need to create a internal A record to make sure client access the OWA url via it;s internal addrss when connect tot he network
0
 
Glen KnightCommented:
that all looks fine.
0
 
compdigit44Author Commented:
Excellant!!!!

BTW if I change my 2003 OWA A record to legacy.domain.com but give it the same ip as the old A record who will the OWA server know to bring up the exchange virtual directory?
0
 
Glen KnightCommented:
0
 
compdigit44Author Commented:
thanks

one more question..

On my SAN Certificate request where is says Legacy. Do I type in the internal FQDN of my2003 mailbox server or the new external legacy name for the 2003 OWA???
0
 
Glen KnightCommented:
it needs all the URL's that you will need to use to access the server with.
See the autodiscover section here on my article that lists the required names: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2300-Outlook-continually-prompting-for-username-and-password.html
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.