Exchange 2010 Hybrids in 2018!

So it seems that Exchange 2010 hybrids are still alive and in demand even though the product is out of support and most certainly should have been replaced by now. However when customers are still running Exchange 2003 what can you do!

So as you can see by the title Exchange 2010 hybrids are still doing well out in the wild and customers who want to go through this transition have some challenges to say the least!

You might say why don’t I use 3rd party migration tools? Why are you doing a hybrid which is a valid point but lets not go there for now!

Well I wanted to highlight some of the technical challenges that Microsoft haven’t fully published out there for this product.

First of all as you are all aware the Hybrid Configuration Wizard is downloaded online so you can get the latest build/updates/etc (the same still applies to 2010). Generally most people would run this from their Exchange platform and this is where the HCW has some challenges although the HCW doesn’t have many hard pre reqs it won’t download unless .net 4.5.1 is installed on the server and furthermore won’t even start installing unless you have .net 4.6.2 of which neither are supported on Exchange 2010.

Now I am sure you are all aware but if not you can run the HCW from any server/workstation within your LAN as long as you have the .net requirements and you have defined the Powershell URL in your Exchange 2010 setup. If not you should publish this internally to allow the remote workstation to connect to Exchange and run the HCW! Ensure the firewall ports are open.

Then hopefully a few clicks later everything is in place and you are ready to go with your Exchange 2010 Hybrid to o365!

2 thoughts on “Exchange 2010 Hybrids in 2018!

  1. Hi thanks for this article. Right! We are too using Exchange 2010 with Hybrid method for migration. Have you been able to easily correctly decomission the exchange server at the end or do you think customers should keep their server during all the life of their Ecxhange usage ? 😉

    This is the tricky part of this kind of project at this time.

    1. Once you have migrated your Exchange server users to Office 365. Exchange can still serve two purposes. First of all however you should look to upgrade to Exchange 2016 (Microsoft provide the license key Free of charge with Office 365 – As long as no mailboxes are hosted on the server). The first purpose is the management of AD accounts if you have put Azure AD Connect in your AD is the source of authority for identity and this is Exchange included otherwise how will you do your Exchange changes or new mailboxes for new starters. The second is SMTP relay I find a lot of customers that have devices or apps that send email but either won’t support this with o365 or the customers don’t want to buy the licenses for the service accounts that need this. If you don’t sync AD and use Cloud only Identity the above is irrelevant and you can decommission the Exchange 2010 server fine.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.