locked
Exchange 2007 to Office 365 with 2013 Hybrid Deployment RRS feed

  • Question

  • I'm looking in to doing a migration to Office 365 from my Exchange 2007 server and I've read about setting up an Exchange 2013 server in a hybrid configuration to facilitate the move.  What I'm confused about is whether or not I need to move to Exchange 2013 first, or if I can move directly from 2007 to Office 365.  I went through the Exchange Server Deployment Assistant and used this scenario, hoping that I'd find the answers there, but it simply says to do a remote move to Office 365 with no mention of moving to Exchange 2013 first.  Can anybody clarify this for me?  If you've done this sort of move, I'm especially interested in hearing from you.
    Monday, October 13, 2014 9:58 PM

Answers

  • Yes, you can move directly from 2007 after configuring hybrid with 2013. All you need to cutover is your Autodiscover record, you can configure 2013 with a new URL such as "hybrid.company.com" to avoid cutting over your current URLs and to limit changes to your current environment.

    Joseph Palarchio http://www.itworkedinthelab.com

    • Proposed as answer by Joseph Palarchio Tuesday, October 14, 2014 1:05 AM
    • Marked as answer by jrs79 Tuesday, October 14, 2014 4:21 AM
    Tuesday, October 14, 2014 1:04 AM
  • If you read this article closely, it talks about moving mailboxes using the EAC for 2003/2007/2010/2013: http://blogs.technet.com/b/exchange/archive/2013/08/29/hybrid-mailbox-moves-and-emc-changes.aspx

    Joseph Palarchio http://www.itworkedinthelab.com

    • Marked as answer by jrs79 Tuesday, October 14, 2014 10:49 PM
    Tuesday, October 14, 2014 10:42 PM

All replies

  • Yes, you can move directly from 2007 after configuring hybrid with 2013. All you need to cutover is your Autodiscover record, you can configure 2013 with a new URL such as "hybrid.company.com" to avoid cutting over your current URLs and to limit changes to your current environment.

    Joseph Palarchio http://www.itworkedinthelab.com

    • Proposed as answer by Joseph Palarchio Tuesday, October 14, 2014 1:05 AM
    • Marked as answer by jrs79 Tuesday, October 14, 2014 4:21 AM
    Tuesday, October 14, 2014 1:04 AM
  • Would you be able to point me in the direction to some documentation backing that up?  I've looked, but haven't found anything.  I actually already have all of this set up and when I try to do a remote move to O365 it fails with an error about the MRS Proxy timing out.  I have a ticket open with Microsoft about it and the tech told me that I have to move to Exchange 2013 first, which I didn't think was right and prompted me to ask the question here.  If I do a remote move from Exchange 2013 it also fails, but with a different error about the domain not being an accepted domain and I'm looking in to that.  

    Does the MRS Proxy need to be enabled on both the Exchange 2007 CAS and Exchange 2013 servers?  That's something I haven't tried, but it just dawned on me that it may have to be that way.

    Tuesday, October 14, 2014 1:38 AM
  • I don't have a link handy but I'm positive it works, all I do is migrate organizations to Exchange Online; I have this exact configuration with one of my clients right now

    You're using the MRS Proxy on the 2013 server, 2007 didn't really have that functionality.

    Support is correct in that I'd make sure you can move from 2013 first.  The accepted domain is likely due to the mailbox having a proxy address that is for a domain that is not registered in Exchange Online.  Pay particular to any legacy "coexistence" domains that might have been leftover from a previously migration such as ".local" domains.  These will need to be removed from the mailboxes.

    For the timeout, I would be interested to see the results of Test-MigrationServerAvailability using the -Verbose switch:  http://technet.microsoft.com/en-us/library/jj219169(v=exchg.150).aspx

    Is the 2013 server published through any type of reverse proxy (i.e. TMG) or load balancer?


    Joseph Palarchio http://www.itworkedinthelab.com

    Tuesday, October 14, 2014 1:54 AM
  • Ok, no problem. I trust that you're right, I just wish I could prove it to the Microsoft tech that I've got a call with tomorrow.  He was saying that a full migration to 2013 is required before going to 0365.

    I was thinking that the problem with the accepted domain was probably the internal domain.  It's a .com, but it's not an accepted domain on O365, so I"m sure that's why.  I had removed that address from the user that I tested, but I didn't force a dirsync afterwards and I reused the same batch request, so I wouldn't doubt if one of those things is why I had the same failed result even after removing that domain.  I just haven't had a chance to try it again.

    Attached is a screenshot of the results of Test-MigrationServerAvailability with the verbose switch.  We're not running a reverse proxy or load balancer, just a firewall between the 2013 server and the internet with 80 & 443 open.

    Tuesday, October 14, 2014 3:14 AM
  • He was saying that a full migration to 2013 is required before going to 0365.

    That doesn't give me a lot of confidence...  If you don't get a resolution fairly soon I'd request an escalation as he's probably not the engineer that will ultimately resolve your issue.   Once hybrid is setup, you can even migrate directly from Exchange 2003 with only downside there being that the migration is offline and thus the mailbox is locked during the migration (so sometimes it makes sense to move to 2010 first so you can move online and suspend when ready to complete).

    The Test-MigrationServerAvailability looks okay although it looks like you're not using Autodiscover to find the endpoint (not an issue but sometimes a sign that things aren't setup right too).  Is Autodiscover setup correctly and pointing to the 2013 server?  You'll also want to make sure the SCP is registered correctly in AD depending on how 2007 was setup.


    Joseph Palarchio http://www.itworkedinthelab.com

    Tuesday, October 14, 2014 3:26 AM
  • I've got a call with this tech tomorrow and I'm planning on asking for escalation if we can't get things resolved.  My ticket with them will be 1 week old tomorrow on this issue, so it's time to escalate IMO.

    I noticed that it wasn't using autodiscover too.  Autodiscover is pointed at the Exchange 2013 server and exrca.com tests run successfully.  I'll double check everything internally.

    Tuesday, October 14, 2014 3:46 AM
  • To clarify, would that be a remote move from Exchange 2007 to Office 365?
    Tuesday, October 14, 2014 9:48 PM
  • Yes, when you have hybrid in place, your moves are "remote moves" as opposed to "staged" or "cutover" migrations.

    Joseph Palarchio http://www.itworkedinthelab.com

    Tuesday, October 14, 2014 10:12 PM
  • Thanks.  The Microsoft tech is standing firm on saying that I'd have to do a staged migration if I want to go from 2007 directly to O365.  I'm having a rough time trying to get him to escalate.
    Tuesday, October 14, 2014 10:15 PM
  • If you read this article closely, it talks about moving mailboxes using the EAC for 2003/2007/2010/2013: http://blogs.technet.com/b/exchange/archive/2013/08/29/hybrid-mailbox-moves-and-emc-changes.aspx

    Joseph Palarchio http://www.itworkedinthelab.com

    • Marked as answer by jrs79 Tuesday, October 14, 2014 10:49 PM
    Tuesday, October 14, 2014 10:42 PM
  • Awesome, that's just what I needed.  Thanks!
    Tuesday, October 14, 2014 10:48 PM
  • Hi,

    What was the final outcome of your escalations with MS support? What was the final call taken based on the guidance on taking the staged migration approach to migrate Exchange 2007 mailboxes to Exchange Online?

    Is it mandatory for a customer running a disparate/de-centralized Exchange 2007 infrastructure to adopt a staged migration vs having a hybrid setup with O365 or is it that Exchange 2013 needs to be introduced at each location where an E2K7 MB/CAS server resides?

    Regards,

    Savio F.


    Sr. Consultant - MS Infrastructure

    Sunday, January 17, 2016 10:53 AM