We are currently planning our upgrade to Exchange 2010. We are using Exchange 2007 SP2. Our confusion is around the need to create a legacy.domain.com entry to be used with the external url configurations. Currently, we do not expose our Exchange environment to the internet - any access to it is through an SSL VPN solution. So, our Exchange 2007 servers do not have an external OWA or EAS entry on them. Will we need to create an legacy.domain.com, or does the Exchange 2010 point users back to the Exchange 2007 environment? Or do we just have to configure the internal urls? Thanks.

Hi, If you don't have any direct access you don't need to worry about the legacy naming. When you are on the internal network both exchange 2007 and 2010 CAS servers will automatically redirect you to the proper server. Will you be exposing the Exchange 2010 to the internet? /MartinExchange is a passion not just a collaboration software.

We do not plan to expose Exchange 2010 either. We do plan on using the UAG for external access, but that will be similar to how external users access Exchange now. Basically, we have an SSL VPN appliance from which users access the apps they need.

One further question I have is, does Exchange 2010 automatically understand that there is an Exchange 2007 environment to redirect to or is there a few configurations that have to be done? I thought I remembered running a powershell command in my lab when I did this. Thanks.

Then you should be alright :) The legacy url is only used to forward mobile phones and owa between the two version. As wrote above the exchange server deal with this automatically when they are inside the firewall. /MartinExchange is a passion not just a collaboration software.

I gather that you are not running EAS since the server is not exposed, but what about OWA? /Martin Exchange is a passion not just a collaboration software.

We run both acutally, but do not have the external URLs configured on the CAS. For EAS users we redirect them from our ISA server back to the CAS.

Hi, How many mailboxes you got on the Exchange 2007 Server? if this is not a large enterprise and if you can move all the mailboxes at a single go, then Legacy record on DNS and Legacy url configuration is not required if you can't move all the mailboxes at the same time and you want to have the mailboxes on both the servers then this configuration is required. refer http://msexchangeteam.com/archive/2009/11/20/453272.aspx Regards, Hari | MCSE+ Messaging

Hi, As Heri writes, since you are using both EAS and OWA from the outside you do need this configuration with the Legacy name if you can move all mailboxes during a service window. I apoligize for the confusion, but when you wrote that Exchange wasn't exposed and you were using SSL VPN i assumed that there were no access to Exchange without the VPN. The article that Hari links to is good reading and it explains a lot. /MartinExchange is a passion not just a collaboration software.

Here's another link you can read through about coex and planning http://technet.microsoft.com/en-us/library/dd638158.aspx Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog