As many of you know from the previous blog post, Exchange 2010 End of Support Is Coming and the soon-to-be-a-classic sequel post Microsoft Extending End of Support for Exchange Server 2010 to October...
Updated Apr 27, 2020
Version 4.0
Blog Post
Great article. I think a couple of things you may want to add that I see it most migrations are:
- For known 3rd-party applications that integrate with Exchange, consider updating their HOSTS file to make sure they will work with a 2016 front-end server. If you have a test environment for those 3rd-party apps, even better.
- Consider using Log Parser Studio (insert EHLO blog post here) to help identify unknown 3rd-party apps, or, other integrations that tie into EWS.
- During decommission, parse the SMTP logs to identify any devices or applications submitting mail that may be doing direct IP (rather than via a VIP or FQDN).
- Parsing the IIS logs once you have migrated all users doesn't hurt either. May have apps doing direct EWS calls to an IP.