none
URIs in exchange 2007 coexistence with 2013

    Question

  • Hi

    I have exchange 2013 CU2 and exchange 2007 in coexistence.  I have created legacy.domain.com and owa redirection works.  However I am totally confused about how to re-adjust other URIs. 

    Would you please advise?

    Legacy.domain.com --> Internally & externally points to exchange 2007 CAS

    mail.domain.com --> Internally & externally points to exchange 2013 CAS

    Exchange 2007 ==> 

    Set-ActiveSyncVirtualDirectory "https://legacy.domain.com/Microsoft-Server-ActiveSync"
    Set-WebServicesVirtualDirectory "https://legacy.domain.com/EWS/Exchange.asmx"
    Set-OabVirtualDirectory  "https://legacy.domain.com/OAB" 
    Set-OwaVirtualDirectory -Identity "https://legacy.domain.com/owa"
    Set-ClientAccessServer -AutodiscoverServiceInternalUri  https://mail.domain.com/Autodiscover/Autodiscover.xml

    ./,/,/,/,/,/,/,/,/,

    Exchange 2013 ==> 

    Set-EcpVirtualDirectory https://mail.domain.com/ECP 
    Set-Webservicesvirtualdirectory https://mail.domain.com/EWS/Exchange.asmx
    Set-ActiveSyncVirtualDirectory "https://mail.domain.com/Microsoft-Server-ActiveSync" 
    Set-OwaVirtualDirectory https://mail.domain.com/OWA 
    Set-ClientAccessServer -AutoDiscoverServiceInternalUri "https://mail.domain.com/Autodiscover/Autodiscover.xml"
    Set-OABVirtualDirectory "https://mail.domain.com/OAB"



    • Edited by Kman2k Monday, August 19, 2013 4:02 AM Title change
    Tuesday, July 30, 2013 4:09 PM

Answers

  • If you change the Exchange 2007 ActiveSync ExternalURL to legacy.domain.com you basically force a redirect to occur on the device. Some devices don't handle the 451 correctly. 

    If you set the Exchange 2007 ActiveSync ExternalURL to $NULL you force a proxy situation to occur where the Exchange 2013 CAS will proxy all requests to the Exchange 2007 CAS. This way devices are not affected by a redirect.

    BTW, is your OA internal and external namespace the same? If it isn't, you need to be aware of a known issue with OAB downloads in Outlook 2007 and 2010.

    From the release notes:

    "If the Offline Address Book (OAB) internal URL isn’t accessible from the Internet, Outlook 2007 and Outlook 2010 clients may be unable to download the OAB.
    To work around this issue for Outlook 2007 and Outlook 2010 clients, make the OAB internal URL accessible from the Internet. Outlook 2013 isn’t affected by this issue."

    http://technet.microsoft.com/en-us/library/jj150489(v=exchg.150).aspx

    Michael

    • Marked as answer by Kman2k Friday, August 02, 2013 11:59 AM
    Wednesday, July 31, 2013 4:32 AM

All replies

  • Hi,

    I don't see anything for Outlook Anywhere. You need to set Outlook Anywhere internal- and external hostnames as well.

    http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx

    Do you have multiple Exchange 2007 CAS servers in your environment?

    If yes, then you need to ensure that OA is enabled on all the CAS servers to allow Exchange 2013 to proxy OA requests to those servers. Also remember that NLTM is required on IIS for all legacy CAS servers.

    Its also important that the OA settings need to be the same as the 2013 CAS to ensure that clients receive the same proxy hostname.

    For ActiveSync on Legacy CAS - set the external url to $null. This will force proxying instead of redirection as some phones don't handle the redirection correctly.

    And dont forget, your Outlook clients need to be patched - http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx

    Other than the above, you seem to be good :-)

    Michael

    Tuesday, July 30, 2013 4:35 PM
  • Hi

    1. I got Multiple CAS servers and outlook anywhere URL is the same (using mail.domain.com) on both sides.

    2. Would you please clarify the piece about the legacy activesync URL and setting it to $NULL?

    What's going to happen to the existing 2007 activesync phones?  Will they continue to operate?

    I know setting it the legacy URL to mail.domain.com breaks things but never tried the $NULL
    Tuesday, July 30, 2013 9:38 PM
  • If you change the Exchange 2007 ActiveSync ExternalURL to legacy.domain.com you basically force a redirect to occur on the device. Some devices don't handle the 451 correctly. 

    If you set the Exchange 2007 ActiveSync ExternalURL to $NULL you force a proxy situation to occur where the Exchange 2013 CAS will proxy all requests to the Exchange 2007 CAS. This way devices are not affected by a redirect.

    BTW, is your OA internal and external namespace the same? If it isn't, you need to be aware of a known issue with OAB downloads in Outlook 2007 and 2010.

    From the release notes:

    "If the Offline Address Book (OAB) internal URL isn’t accessible from the Internet, Outlook 2007 and Outlook 2010 clients may be unable to download the OAB.
    To work around this issue for Outlook 2007 and Outlook 2010 clients, make the OAB internal URL accessible from the Internet. Outlook 2013 isn’t affected by this issue."

    http://technet.microsoft.com/en-us/library/jj150489(v=exchg.150).aspx

    Michael

    • Marked as answer by Kman2k Friday, August 02, 2013 11:59 AM
    Wednesday, July 31, 2013 4:32 AM
  • Hi

    1. Internal and External namespaces are different.  But I have created the zone for external entity on the Internal DNS.

    So is this good to go?


    Exchange 2007 ==> 

    OutlookAnywhere ExternalURL =  mail.domain.com
    Set-ActiveSyncVirtualDirectory internal = "https://legacy.domain.com/Microsoft-Server-ActiveSync" + external = $null
    Set-WebServicesVirtualDirectory "https://legacy.domain.com/EWS/Exchange.asmx"
    Set-OabVirtualDirectory  "https://legacy.domain.com/OAB" 
    Set-OwaVirtualDirectory -Identity "https://legacy.domain.com/owa"
    Set-ClientAccessServer -AutodiscoverServiceInternalUri  https://mail.domain.com/Autodiscover/Autodiscover.xml

    ./,/,/,/,/,/,/,/,/,

    Exchange 2013 ==> 

    OutlookAnywhere ExternalURL + InternalURL =  mail.domain.com
    Set-EcpVirtualDirectory https://mail.domain.com/ECP 
    Set-Webservicesvirtualdirectory https://mail.domain.com/EWS/Exchange.asmx
    Set-ActiveSyncVirtualDirectory "https://mail.domain.com/Microsoft-Server-ActiveSync" 
    Set-OwaVirtualDirectory https://mail.domain.com/OWA 
    Set-ClientAccessServer -AutoDiscoverServiceInternalUri "https://mail.domain.com/Autodiscover/Autodiscover.xml"
    Set-OABVirtualDirectory "https://mail.domain.com/OAB"



    • Edited by Kman2k Wednesday, July 31, 2013 1:44 PM change fonts
    Wednesday, July 31, 2013 1:43 PM
  • If you created the external zone on the internal dns, then you are using split domain and I don't see why you'd want to use separate namespaces for internal and external. Just use the same namespace if you are doing split domain dns. 

    Other than that you seem to be good.

    Michael

    Thursday, August 01, 2013 6:07 AM
  • hello,

    i have the same situation, except i have ex2010 instead ex2007. Are the rules for Outlook Anywere URL's the same?

    where is pointing your internal DNS record mail.contoso.com, to exchnage 2007 or exchnage 2013?

    in my situation record is still pointing to ex2010, and all the clients are on ex2010. Should i change it now or after migration?

    mail.contoso.com for ex2010  is windows NLB and exchnage 2013 CAS's have Round Robin mail2k13.contoso.com for DNS name.

    what should i do?



    • Edited by Mari_o Friday, August 16, 2013 6:37 PM
    Friday, August 16, 2013 6:25 PM
  • Well,

    I can sit here and tell you to open a new thread OR try to answer :-) ;  I will answer -->

    First of all provide more information....  In my case the external and internal domains were different so I had to create a zone for SMTP external domain on the inside DNS.

    Here we go -->

    1. Are the rules for Outlook anywhere URL's the same?  

    Answer: Yes; assuming that you are already use outlook anywhere and still want to use it.  If you don't want to use outlook anywhere and make life easy for yourself then don't enter an external URL on 2013 outlook anywhere side and leave outlook anywhere on 2007 disabled

    ------------------------------

    2. where is pointing your internal DNS record mail.contoso.com, to exchnage 2007 or exchnage 2013?

    Answer: What is mail.contoso.com anyway?  The web mail? OR MX record?

    - If it is MX record then initially it is pointed to 2007.  It should point to exchange 2010 HUB at the end assuming you have configured the receive connector properly on 2010

    - IF mail.contoso.com is the webmail/outlook anywhere/activesync address then it points to exchange 2013 CAS during coexistence

    --------------------

    3. 2013 round robin?

    Answer: I recommend looking into a hardware load balancer such as Kemp technologies.  They provide TRUE failover as they constantly check to see if the exchange 2013 CAS servers are up.  If paying around $2000 and more (depending on size of company) is out of question then round robin will be ok.

    -------

    I have adjusted my initial entry above so it is more clear





    • Edited by Kman2k Friday, August 16, 2013 7:04 PM more adjustments
    Friday, August 16, 2013 6:58 PM
  • thanks for answering :)

    in my case also, internal and external smtp namespaces are different and i also have external SMTP namespace on internal DNS.

    internal name space is xy.contoso.com, and external name space is contoso.com

    1. you are right, i am using outlook anywere, and still want to use it

    2. mail.contoso.com is address of webmail/outlook anywhere/activesync. but it is also DNS record of WNLB ex2010 cas/hub server and internal outlook clients are pointing to it.  my concerne is, if i change internaly mail.contoso.com to point to ex2013, will that affect existing users on ex2010 server?

    3. circumstances are that company is not ready to pay for hardware load balancing


    Friday, August 16, 2013 9:33 PM
  • Answer to 2: If the exchange 2010 CAS servers are configured with proper new URLs as discussed in this thread + SSL certificate that has legacy.domain.xxx; then you should be ok.  

    In my situation I exported the new certificate that I had bought for 2013 environment and exported it to 2010.

    You may want to do this during a maintenance window as there are multiple pieces to check including activesync, OWA, outlook and more.

    As you can see the autodiscover URI on both 2010 & 2013 are the same (mail.domain.com).  Whenever you are ready (Proper URIs + SSL); adjust the DNS entries and point mail.domain.com over to 2013.  Requests from 2010 mailboxes will get proxied over to 2010.

    This whole coexistence thing can be a beast to setup because it is rather new and resources online mostly cover the installation.

    Friday, August 16, 2013 11:29 PM
  • i have exchange 2010, legacy name is only used for ex2007.

    thanks. as you said, there is a little online resources covering coexistence, so you were very helpfull for me

    Sunday, August 18, 2013 5:58 PM
  • sorry men, i have one more question.

    answer to 2

    so that means when i point DNS record mail.contoso.com to exch2013, my exchange2010 clients, which  are now RPC over TCP will become  RCP over HTTP clients and they requests will be proxied to ex2010 until migrated to exch2013?

    Sunday, August 18, 2013 9:52 PM
  • Hi there.

    Welllllll,,,, Now that depends on how your environment is setup to handle outlook clients.

    Do you use have a CAS Array? Do you have outlook anywhere ALREADY enabled?  Are outlook clients using outlook anywhere?

    I say that because if your internal clients are not using outlook anywhere already then there will be problems with your outlook clients not being able to connect AFTER the DNS switch over is made!!

    This is called Ambiguous URLs and it applies to exchange 2010 / 2013 coexistence

    Check these links

    http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx

    Monday, August 19, 2013 4:09 AM
  • "If yes, then you need to ensure that OA is enabled on all the CAS servers to allow Exchange 2013 to proxy OA requests to those servers."

    This saves my days and hours of sleep. I wanted to thank you for this. 

    Tuesday, December 10, 2013 2:21 AM
  • As far as I remember, the ActiveSync redirection issue that was brought with Exchange 2007/AS 12.1 (Apple clients) was fixed 4 years ago.

    I don't think you need to set the $null value for the external URL.

    Tuesday, December 10, 2013 4:36 PM