Migrating to Exchange Server 2013

Summary: This session presents an overview of the migration paths for upgrading from Exchange 2007 and 2010 to Exchange Server 2013.

About Jaap Wesselius

Jaap Wesselius is an Exchange Server MVP and working as a Sr. System Architect for Amsio, a managed Service Provider in The Netherlands. In this role Jaap is responsible for the complete Microsoft portfolio when it comes to hosting. Prior to working for Amsio Jaap has been working as an independent consultant and as an infrastructure consultant for Microsoft MCS in The Netherlands (focusing on Exchange Server of course).
Follow Jaap on Twitter at @jaapwess

Comments

  1. Kallol Parida says:

    Unable to download this video. Please upload it and share the link

    • Hi Kallol, it seems to be working okay from here. Can you please try refreshing the page, or use a different browser. Also if you’re connecting from work, verify that your proxy isn’t blocking the content.

      • Kallol Parida says:

        Thanks Paul. Now I can able to download it. Thanks for posting such a valuable information’s, I really appreciate it.

  2. I have a couple of questions regarding coexistence related to OWA redirection.

    1) Is it no longer necessary for “legacy” redirection? If so, was that feature introduced in 2013 or in 2010? And if with 2010, what SP and/or UR?
    2) Is it true that it is no longer necessary to shorten the OWA URL?

    Great session. Thank you.

    Todd

    P.S. Same for me on the video download. No joy!

    • FYI… Now the download is working for me.

    • Hi Todd,

      Thanks for your kind feedback.

      1. For Exchange 2010/2013 the legacy redirection is not needed, the connections are proxied directly from 2013 to 2010. For an 2007/2013 situation the legacy redirect is used again.
      2. Can you elaborate a bit on the question to shorten the OWA URL? I’m afraid I do not understand it correctly.

      Thanks,
      Jaap

      • Jaap,

        Thanks for the responses. Hopefully I can clarify on #2.

        Many of our customers implement a short or a simplified URL to OWA for their 2007 and 2010 users (i.e. http://oddytee.blogspot.com/2013/05/simplify-owa-url-for-exchange.html). I read in an article (can’t recall or fine the article right now other than that it was on TechNet) that 2013 allows users to access “webmail.companyname.com” and users are redirected natively to “https://webmail.companyname.com/owa”. Is this true? If not, how do we simplify the OWA URL in 2013?

        Thanks,

        Todd

        • ah, now I understand.

          Personally I’ve never heard of this. I cannot test since I have an F5 load balancer in front of my Exchange 2013 servers.
          According to this TechNet article http://technet.microsoft.com/en-us/library/aa998359%28v=exchg.150%29.aspx nothing has changed. Since I see several errors in the article I asked the Product Group for some clarification.

          Thanks,
          Jaap

          • Thanks, Jaap.

            The TechNet article you provide is for Exchange 2010 and it hasn’t changed even though it was modified earlier this month. I don’t necessarily like the layout, explanation or instructions given as much as other articles referenced in my blog post-and feel it leaves a lot for assumption. I will see if I can find the article I read last week.

            Thanks,

            Todd

          • Hi Todd,

            The article is in the Exchange 2013 tree and it also mentions “Exchange 2013 mailbox”, therefore I’ve asked the Exchange product group for clarification. IMHO the article should be updated asap.
            If you can find you article please let me know.

            Thanks,
            Jaap

          • Jaap,

            Found the article! However, it is not a TechNet article. It is from your fellow Exchange MVP, Jeff Guillet. Jeff documents briefly what I was referring to in his article (http://www.expta.com/2013/05/owa-2013-cu1-redirection-is-broken-for.html) but the TechNet release notes for Exchange 2013 CU1 do not include info in this “new” feature (http://technet.microsoft.com/en-us/library/jj150489(v=exchg.150).aspx).

            Previous attempts to manually configure IIS to simplify the OWA 2013 URL did not work-using the TechNet article you referenced earlier. I would love some definitive clarification that CU1 does allow this functionality.

            Thanks,

            Todd

        • Hi Todd,

          Sorry for my late reply. I have been traveling to New Orléans (and back) last week.
          When I was in New Orléans I’ve spoken to Jeff Guillet about this and he admitted this article from him is not correct and he will update the article asap.

          May I ask…. have you tried a load balancing solution?

          Thanks,
          Jaap

          • Jaap,

            I want to begin by letting you know how jealous of you (and all of the others) I am but could not attend this year-maybe in Houston TX for 2014. Hope you are now enjoying some relaxation time with your new Surfaces prior to TE in Madrid.

            Thank you for reaching out to Jeff. I did leave a comment on his post. However (as of this morning) it appears the article has been pulled down for further review. I hope to see something soon.

            We have tried load balancing solutions. Don’t really know how it applies to what I asked originally but would love to see the tie-in. Our customer base ranges from SMB, government, education and enterprise. Many customers, surprisingly, don’t have more than one Exchange server and as a result don’t have need for a load balancer with respect to Exchange in their environment. Many that have multiple Exchange servers do not want to spend the $$$ to procure multiple LBs for a proper HA design. Some do however. Do you have a inexpensive hardware or virtual LB recommendation? I would love something for my lab as well but with budget constraints it is difficult to do.

            Thank you for the follow up. Hoping to hear from you soon.

            Todd

  3. Exchange 2010 required a separate server for UM. How do we migrate the configuration, call attendants, etc. to the new Mailbox2013 server?

    Nice presentation - thank you

    • Hi David,

      Due to time constraints I was not able to cover this. For some upcoming migrations I have to do some more research on this and will let you know. Because of TechEd NA en TechEd Europe I’m pretty busy the upcoming weeks I’m afraid, but promise will get back.

      Thanks,
      Jaap