Decommission Exchange 2013 After 2019 Migration | Complete Solution

  author
Written By Andrew Jackson
Anuraag Singh
Approved By Anuraag Singh
Published On August 25th, 2022
Reading Time 5 Minutes Reading

Summary: If you are finding solution how to decommission Exchange 2013 after 2019 migration? If yes, then you are at the right place and reading the correct article. Here, we will explain the process of decommission the Exchange Server 2013 after upgrading it to Exchange 2019.

Microsoft is upgrading their versions and services day by day. So, that users can keep their Exchange data safe and secure from threats or error. It is important to use the latest version of Exchange Server, as it provides many amazing and advance feature such as: security, compatibility with latest or new software & security applications, etc… to prevent the data.

That’s why upgrading the MS Exchange Server from the existing version to the latest one is always very good for users, IT organization and other industry verticals. But the worst part of migration is to clean up the process of older version. It is mandatory for users to clean uninstall the application rather than deleting the serve with decommissioning it. If this is not done properly then you have to face certain issues as well as complications.

Certain Things to Consider Before Decommission the Microsoft Exchange Server

For business installation in the organization or any other sector that use Exchange, it is necessary to consider Skype or Lync. There are no unified messaging services in the Exchange Server 2019, so users that to note that they will no longer able to save the voice mailbox from the Lync or Skype to the Exchange user’s mailbox for business after decommission the Exchange Server 2013.

The alternative solution for this is to use the CX-E and Office 365 subscriptions for the business online plan 2. Another things is to take into consideration is the client support before decommission the Exchange 2013. It support Microsoft Outlook 2010 sp1 & 2013. If users are using the office 2010 or they have some older installations, then they need to upgrade at least to office 2013.

Note: Decommissioning Exchange Server 2013 shouldn’t affect you, if you are using office 2013.

Ensure that all the URL of virtual directory are pointing to the Exchange 2019 Server. Users can do this from EAC (Exchange Management Shell) or by using the Exchange PowerShell command – “Get-OutlookAnywhere” and various other command given below. Users have to make sure that all the URL are pointing towards because this provide you the MS Outlook Anywhere URL.

command

Use the Command given below to get all URLs

Get-ClientAccessServer | Select AutoDiscoverServiceInternalURL
Get-ECPVirtualDirectory | Select InternalURL,ExternalURL
Get-WebServicesVirtualDirectory | Select InternalURL,ExternalURL
Get-MAPIVirtualDirectory | Select InternalURL,ExternalURL
Get-ActiveSyncVirtualDirectory | Select InternalURL,ExternalURL
Get-OABVirtualDirectory | Select InternalURL,ExternalURL
Get-OWAVirtualDirectory | Select InternalURL,ExternalURL
Get-PowerShellVirtualDirectory | Select InternalURL,ExternalURL
Get-OutlookAnywhere | Select InternalHostName,ExternalHostName

This will provide you the insight of all URLs. Note that these are pointing toward the Exchange Server 2019.

Then, users have to check and verify all the mailbox database is moved to the Exchange 2013 and there is no online database left behind. You can check this via EAC and PowerShell cmdlet – “Get-MailboxDatabase”.

Another important thing is to check the email is pointing to the Exchange 2019 Server before decommissioning the Exchange Server 2013. You can check this on two location. One is the internet domain’s DNS records and the other one is router.

From DNS record, user need to confirm the MX record of domain that is pointing the correct IP address, if the server external IP address has changed or you assigned the new one.

On router, open all related port or change port, pointing to the Exchange 2013 to the Exchange Server 2019. Also, check the firewall rules from the router side and see the active ones. If there is any on the Exchange Server 2013 then update to point to the Exchange 2019.

After checking all the things the next thing that users have to do is decommission the server.

How to Decommission Exchange 2013 After 2019 Migration?

Follow the steps given below:

Step 1: From Exchange Server 2013, go to Program and Features or execute the appwiz.cpl from command line

Step 2: Select the Microsoft Exchange Server 2013, right click >> Click on Uninstall

open program and features

Step 3: Click on the Next button on the welcome screen of Exchange 2013

Step 4: Then the Microsoft Exchange readiness check screen appears >> When you get the uninstall screen >> Press it and remove all roles from the server

Step 5: After this process, users will be asked to reboot the system

Step 6: Then, go with decommission the server by disjoining the machine from domain >> After that turn off the machine

Bringing It All Together

Here, in this write-up, we have explained the things that need to me consider before decommission Exchange 2013 after 2019 migration. There is no doubt that this is clean uninstall with no hindrance or problem. However, issues may rise during migration and while moving Exchange mailboxes. Users also face issue after decommissioning and migration the old server like – mailbox is missed during migration. In such case, advanced software i.e. SysTools Exchange Server Recovery Tool comes useful. The utility easily resolves database corruption Exchange 2010/2013/2016, repair EDB file and mailboxes from corruption with no data loss. You can export the healthy and recovery mailboxes to the Live Exchange Server, Office 365 and multiple file formats in a simplified manner.

Downloadpurchase

  author

By Andrew Jackson

I am SQL DBA and SQL Server blogger too. I like to share about SQL Server and the problems related to it as well as their solution and also I do handle database related user queries, server or database maintenance, database management, etc. I love to share my knowledge with SQL Geeks.