Once you’ve completed the migration from Exchange 2010 to, let’s say, Exchange 2016, you should prepare the 2010 environment prior to decommissioning the servers. If your organization has moved all mailboxes to Office 365 and is in a Hybrid environment, we are assuming you will maintain an Exchange footprint per Scenario 2 in How and when to decommission your on-premises Exchange servers in a hybrid deployment. This post assumes that your organization is maintaining some Exchange presence on-premises, whether Exchange 2013 or 2016 (we do not mention Exchange 2019 in this post because it cannot coexist with Exchange 2010). Do not reuse Exchange 2010 server IP addresses (until they have been fully decommissioned).Do not reuse Exchange 2010 server names (until they have been fully decommissioned).Please plan the decommission process carefully.Īs a general statement, here are some things that we want to caution against: Please note that since there are many different types of deployments and configurations it is difficult to cover all scenarios, but many of the common steps are included here. This post is intended to provide best practices to plan for and complete the Exchange 2010 decommission. Uninstalling Exchange 2010 is as easy as running Setup and selecting to remove the server roles, but there are prerequisites to removing the roles and legacy items left over, which should be removed. We’ve created this post to cover the best practices for decommissioning an Exchange 2010 environment after the migration has completed. As many of you know from the previous post regarding Exchange On-Premises Best Practices for Migrations from 2010 to 2016 the end of support for Exchange 2010 is quickly approaching.