How to uninstall and decommission MS Exchange Server 2013?

This is using a co-exist of MS Exchange 2013 and2016 Exchange Organization. Both Exch servers are multi-role. Exch2k3 server has been installed and working for the past 3 years. Exch2k16 server was newly-joined 2 months ago. All user mailboxes have been moved to Exch2K16. Mail sending/receiving and other exchange operations are working fine.

Now, we want to disjoin and decommission this Exch2k13 server. How to do it properly? My experience on removing exch2k10 was rather scary, as uninstalling didn't turn out smoothly. Most of the time, I have to "force" uninstall.

Thanks in advance.
Who is Participating?
Jose Gabriel Ortega CEE Solution Guide - CEO Faru Bonon ITCommented:
Just make sure that there are not any mailboxes on your current old databases (hosted on 2013).

Running this script

liket this:
Get-MailboxesCountByDatabase.ps1"  -Count

Open in new window

you should have arbitration and system mailboxes in the old dbs.

just move those over a database on 2016 server.

Get-Mailbox -database <databaseNameIn2013> <option> | New-MoveRequest -targetdatabase <databasein2016>

Open in new window

if you have arbitration mailboxes in option -arbitration
if you have monitoring the option is: -monitoring
if they are users     : omit the option parameter

you can check the movements :
Get-MoveRequest | Get-Moverequestatistics

and to remove the move requests:
Get-MoveRequest | Remove-MoveRequest -confirm:$false

Once you run again the script and you see "all ceros" below for the databases in 2013.

you will be able just to uninstall the exchange 2013 using "add or remove programs" as a normal program.
Sunil ChauhanExpertise in Exchange Server, Office 365 & Powershell ScriptingCommented:
As you have exchange 2016 already installed and running and all stuff have already been moved over, the next step should be rather very smooth.

This is the approach I would use.

  1. confirm if the CAS is out of the Loadbalancer pool.
  2. Once confirmed, monitor IIS logs to make sure that new connections are not being made to these nodes.
  3. verify if the address book generation is happening on the new servers
  4. If you use the exchange for application mail relay, make sure to remove these servers from the mail relay pool.
  5. If you have the hybrid setup with office 365 make sure to rerun the hybrid wizard and replace the 2k13 servers with 16.
  6. Disable all the service on the 2k13 servers at least for a week or two, before the final uninstall, in case anything was still coming up to servers you will be reported on the same.
  7. and then finally uninstall the Exchange
Kapil SharmaTech Geek :)Commented:
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

you also need to move all arbitration mailboxes from 2013 server to exchange 2016 database, that is an important step
Your SPF record should include 2016 server public IP, that is an important step
If you also have public folder, that also need to be moved to 2016 server
I believe you already have pointed MX to new server
Sandeep KumarAssociate ConsultantCommented:
For Decommissioning Exchange Server and clean up of Exchange Server 2013, visit: for the steps to Decommission Exchange Server 2013.
MichaelBalackAuthor Commented:
Thanks for 3 experts in providing very useful articles and suggestions. my exchange server was decommissioned successfully.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.