Exchange Server 2016 removing version 2010 servers

The moment we have migrated mailboxes, public folders and services to new servers. All traffic is routed to Exchange 2016 and we have done sufficient testing that everything works. We can proceed to decommission the original Exchange 2010 servers. The servers must be removed correctly, i.e. Exchange must be uninstalled.

displayed: 7 268x (6 318 CZ, 950 EN) | Comments [0]

This article is part of a series based on my notes during the migration of an Exchange organization from version 2010 to 2016. This is not a complete procedure, but a description of the main points and areas. The examples relate to a specific design, but can usually be generalized. Similarly, although this is a description of a migration, the information is also suitable for a new installation or administration.

Official documentation Exchange Server 2016.

This article contains only certain steps in a concise manner. It depends on the Exchange 2010 architecture. Here, it is assumed that there are several servers that had all roles and used a DAG.

At the beginning, we can check if there are any connections to the original servers. In the IIS logs, we can see client access, and in the log files (and Message Tracking Logs) if SMTP traffic is coming in.

Preparatory Steps

It's possible that we have already performed these steps earlier. If not, we'll start with them.

Modify Send Connector

If we haven't already removed the original servers from the Send Connectors, we'll do it now.

EAC - Exchange Admin Center
Mail Flow - Send Connectors
select the appropriate connector
Edit - Scoping - Source server
remove the old servers here

Remove All Migration Batches or Move Requests

For further operation, I recommend deleting all completed migrations, info in Exchange Server 2016 moving mailboxes and OAB. Can be done using the Exchange Management Shell.

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest -Confirm:$false

Removing Databases and the DAG

For Exchange to be uninstalled, the server must not contain any mailboxes or generate an OAB. It's best to remove the mailbox databases (again, they must not contain any mailboxes) and the public folder databases. In the case of a DAG, remove the entire DAG.

If we haven't removed the public folders after the migration, we'll delete the PFProxyMBX (Proxy mailbox) user and the DBPFProxy database, and remove the public folder databases.

Removing Passive Database Copies

Remove a mailbox database copy

We can do this on Exchange 2010 or Exchange 2016 (instructions here).

EAC - Exchange Admin Center
Servers - Databases - select the DB
on the right of the passive copy (must be in the Healthy state) that we want to remove, click Remove
confirm the removal and we get the information that we can remove the DB and log files
manually delete the files on the disk

Removing Databases

Remove a mailbox database

If we remove all database copies, we can delete the entire database.

EAC - Exchange Admin Center
Servers - Databases - select the DB
click the Delete icon (trash can) in the top row and confirm
manually delete the files on the disk

Removing Server Membership from the DAG

Perform this on Exchange 2010. For Exchange 2016 Manage database availability group membership.

EMC - Exchange Management Console
Organization Configuration - Mailbox - Database Availability Group
right-click on the DAG and choose Manage Database Availability Group Membership
select the server and click the cross and Manage

Removing the DAG

Perform this on Exchange 2010. For Exchange 2016 Remove a database availability group.

If the DAG does not contain any servers, we can delete it.

EMC - Exchange Management Console
Organization Configuration - Mailbox - Database Availability Group
right-click on the DAG and choose Remove
confirm Yes

Cleanup

after removing the DAG, we can delete the computer object in AD DS that was named the DAG
if we used a CAS Array, we can remove the DNS record and on Exchange 2010 delete it using Remove-ClientAccessArray, but it's not supported at all from Exchange 2013, so it doesn't matter
if we have an old Offline Address Book (OAB) generated on Exchange 2010, we'll delete it

Uninstalling Exchange

in the standard way, we start the uninstallation (Control Panel - Programs and Features or Add/Remove Programs) - Uninstall
uncheck all the roles
first, it checks that the uninstallation can proceed

Related articles:

I was migrating an organization from Exchange Server 2010 to Exchange Server 2016. The whole process was quite demanding and long (it took me 4 months even with my studies). In the process, I came across a number of problems, errors and shortcomings (even in the official documentation). I am creating this series from my notes. This is not a complete guide to the transition, but highlights and mentions of issues I encountered. Individual articles describe different areas of Exchange Server 2016, so it is not only a transition from an older version, but also suitable for a new installation or administration.

Almost since the beginning of my practice, I have been involved in the administration of the Microsoft mail server, i.e. Exchange Server. I started with the 2003 version and worked my way up to Exchange Online. The articles cover many areas of management. Most since the migration to Exchange Server 2016 and its complete configuration. But also Exchange Hybrid and e-mail security.