Forum Discussion
Where and when to install Exchange Hybrid
- Jan 29, 2018
Hi Tom,
Option 2 with a few changes to the process
. Install 2016, setup Exchange 2016, Setup Hybrid, cut mail flow to EOP (Test First), perform the migrations through Exchange 2016 from the 2010 mailboxes, then just tear down 2010 at the end
Hi Tom,
Option 2 with a few changes to the process
. Install 2016, setup Exchange 2016, Setup Hybrid, cut mail flow to EOP (Test First), perform the migrations through Exchange 2016 from the 2010 mailboxes, then just tear down 2010 at the end
- Tom GouldJan 29, 2018Brass Contributor
I agree with this approach and is what I would prefer. But I was having a friendly conversation on what approach people take. Curious what Paul and others recommend.
- Jan 30, 2018
You can do it both ways. Option 2, as Nuno already mentioned, would be the best and simplest one.
- Adam OchsJan 31, 2018Steel Contributor
This is a path we take with our clients for pro serve migrations, and we follow option 2, of putting the 2016 server in place, then doing the migration.
At the end of the migration you can decomm your old 2010 servers without a ton of extra hassle, and the 2016 server looks and feels like Office 365. It puts you in the end state as soon as your migration is done, and has some of the pre-work going on when users are unaware and still just doing their normal thing. By following this path too, there is typically some AD cleanup work that happens when you upgrade the exchange schema, which means a cleaner/better foundation as a starting point in O365.
These are the primary motivators for my company, which causes us to follow option 2.
The one "got ya" that we have come to look out for is Public Folders. The architecture of Public folders changes pretty drastically from 2010, to 2013/2016. When you perform the Exchange Schema upgrade to your AD, which you have too in order to do 2016, then your Public Folders in 2010 start having issue for anyone you have moved.
The way you get around this is by migrating the PF's to 2016 as cross platform move, then doing commands in Office 365 to have the 2016 folders be discoverable in Office 365. Then you stage and move them over just like a remote mailbox move. The first time we did this it was kind of a cluster, but we have sense got much better at the process.
Some good resources if you do have PFs:Overview of what you can do- https://technet.microsoft.com/en-us/library/dn249373%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396
Migration Commands - https://technet.microsoft.com/en-us/library/dn874017(v=exchg.150).aspx
Great blog - https://blogs.technet.microsoft.com/undocumentedfeatures/2017/04/08/migrating-hybrid-public-folders-to-office-365/Hope this helps!