locked
Exchange 2010/2013 co-existence and Lync integration RRS feed

  • Question

  • Hello,

    I'm looking at integrating Lync Server 2013 into my lab environment, which consists of a mixed 2010/2013 Exchange environment.

    UM - Exchange 2010

    CAS - Exchange 2013

    MBX - Exchange 2010

    MBX - Exchange 2013

    I've been reading about associating CAS and MBX servers with UM dial plans, when integrating with Lync.

    The Technet articles, and MS Press documentation I've read suggests that all CAS and MBX servers need to be associated with the dial plan.

    Does this include the 2010 MBX servers?

    As far as I was aware, in a co-existence environment between 2010/2013 all traffic is proxied to the MBX servers via the CAS 2013 role?

    Does this rule still apply when UM and Lync exist in the environment?

    Also, does the 2010 UM server need to be associated with the Lync UM dial plan, or does the 2013 CAS server handle this traffic as well?

    Thanks


    Matt


    Thursday, August 7, 2014 11:21 AM

All replies

  • So, just the UM server in 2010 would be associated with the dialplan, you won't even have the option to add a 2010 MBX server.

    The traffic isn't proxied by the 2013 CAS, it's more of a redirect, and yes this happens.  A lot of what will happen under the hood will be somewhat transparent, Lync will determine where it wants to send the UM traffic.  You can watch this in the Lync logger by watching SIPStack.

    The 2010 UM server can be associated with the dial plan, but you might not need it unless you're trying to recreate that specifically in your lab.  Exchange 2013 UM can serve mailboxes on an Exchange 2010 server.

    I would suggest just deploying it in your lab and watching what happens, that's half the fun. :)


    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Friday, August 8, 2014 9:14 PM