none
Exchange 2010 coexistence with 2013 (URLs to use??)

    Question

  • Hi

    I have exchange 2013 CU2 and exchange 2010 in coexistence.  I need some help with URIs on both environments BEFORE I can change the DNS entries to point to 2013.   

    Would you please advise?  Especially on what I should use for 2010 URLs.

    mail.domain.com --> Internally & externally points to exchange 2013 CAS (Used to be FQDN pointing to 2010)

    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"

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

    Exchange 2010 ==> 

    Set-ActiveSyncVirtualDirectory 

    --> InternalURL:  "https://??????????/Microsoft-Server-ActiveSync"

    --> ExternalURL:  $NULL
    Set-WebServicesVirtualDirectory "https://??????????/EWS/Exchange.asmx"
    Set-OabVirtualDirectory  "https://??????????/OAB" 
    Set-OwaVirtualDirectory -Identity "https://??????????/owa"
    Set-ClientAccessServer -AutodiscoverServiceInternalUri  https://mail.domain.com/Autodiscover/Autodiscover.xml





    • Edited by Kman2k Monday, August 19, 2013 12:24 PM
    Monday, August 19, 2013 4:18 AM

Answers

  • Hi

    But the first article applies to 2003 migration to 2010.  Doesn't exchange 2013 proxy request back to 2010?  That is why I just want to be sure about the URLs.

    would you please tell me what should i put in place of ????????? above?

    Will that be legacy.domain.com 

    OR

    will it be $null?

    Monday, August 19, 2013 12:21 PM
  • Hello,

    Steve provides the link that is useful.

    Exchange 2013 can proxy request to exchange 2010.

    You can change the internalurl to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values on all Exchange 2010 mailbox databases accordingly.

    But we don't recommend you to do this. You can implement Outlook Anywhere internally for all users prior to introducing Exchange Server 2013 to the environment so that you needn't change the url.

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Tuesday, August 20, 2013 3:02 AM
    Moderator

All replies

  • Hi,

    In coexistance scenarios, with legacy Exchange server, it is usual do direct production namespace to Exchange Server 2013, and legacy domain namespace to old Exchange. In your case, you can define, for example, legacy.comain.com to your old Exchange. See this article : http://blogs.technet.com/b/exchange/archive/2009/11/20/3408856.aspx . It is for transitioning to Exchange 2010, but most of it can be applied to your scenario.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

    • Proposed as answer by damirdMVP Monday, August 19, 2013 8:01 AM
    • Unproposed as answer by Kman2k Thursday, August 22, 2013 12:32 PM
    Monday, August 19, 2013 8:01 AM
  • Hi

    Also take a look at this blog post to see if it applies in your case: Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations

    Steve

    Monday, August 19, 2013 8:22 AM
  • Hi

    But the first article applies to 2003 migration to 2010.  Doesn't exchange 2013 proxy request back to 2010?  That is why I just want to be sure about the URLs.

    would you please tell me what should i put in place of ????????? above?

    Will that be legacy.domain.com 

    OR

    will it be $null?

    Monday, August 19, 2013 12:21 PM
  • Hello,

    Steve provides the link that is useful.

    Exchange 2013 can proxy request to exchange 2010.

    You can change the internalurl to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values on all Exchange 2010 mailbox databases accordingly.

    But we don't recommend you to do this. You can implement Outlook Anywhere internally for all users prior to introducing Exchange Server 2013 to the environment so that you needn't change the url.

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Tuesday, August 20, 2013 3:02 AM
    Moderator
  • Hi

    Thanks for the reply HOWEVER it is not the answer to my initial question.  I did see the "Ambiguous URL" page and I have already implemented the outlook anywhere.

    But I am not sure about the URLs that needs to be used on the 2010 environment (The ones marked with ???????).  

    Would you please advise me on that ?

    Wednesday, August 21, 2013 12:07 PM
  • Hello,

    According to the blog steve provides.you needn't change the url. The ones maked still is "mail.domain.com".

    If you have any feedback on our support, please click here


    Cara Chen
    TechNet Community Support

    Thursday, August 22, 2013 1:34 AM
    Moderator