Well in my case it wasn’t to be, until I found out what the underlying issue was! Read on to find out.
*Queue Fresh Prince of Bel Air theme song*…Now this is a blog post all about how I jumped on board and look at me now…
Released for public preview in 2018
Rumours surfaced in 2017
Microsoft coding geniuses putting the beast together since 2014
And I, pure awesomeness, trying to keep up with the changes since 2009!
Hi folks! Yep, pure awesomeness here again and no, I’m not here to talk about cross forest this and mail flow that. I’m here to let you all know our good friends at Microsoft have now advised the next release of Exchange server is in public preview!
By now you would’ve read my previous blogs where I walked you through completing cross forest mail migrations, setting up cross forest mail flow and implementing this thing called multi-tenancy. If you haven’t read those blogs, stop reading this one, click on the links below and come back:
Hi guys, yep it’s me again…the pure awesomeness that got you through the cross forest migrations. Just when you thought your cerebrum, you know, the large part of your brain that does all the thinking, had just been taken through its paces with trying to memorise cross forest migrations, along comes me again!
Welcome back my trusted Exchange consultant! So by now you would’ve read my previous blog “The Mother of All Cross Forest Migrations” and after you finished running laps around the office in pure joy that you now have a way to migrate your finance department from your source to target forests,
On-premises Exchange server migrations are straight forward enough (when technology behaves itself) but then you come across a new Exchange migration project where two words pop out of the scope and slap you right across the face…CROSS FOREST. Before you proceed to understand the scope, you already know that the overall complexity has multiplied by 10.