Learn Exchange the Guru way !!!


“Legacy Exchange Servers Decommission” Post Exchange 2013 Migration

It has been demanded from many of you to publish this part of the migration. So here you go!!


Transferring  Exchange 2010/2007 roles to 2013

Below mentioned Blogs will help in transferring roles


Move the following roles before you uninstall Exchange 2010/2007 from your organization:

  1. Move all user mailboxes to Exchange 2013.
  2. Move all room mailboxes to Exchange 2013.
  3. Move all arbitration mailboxes to Exchange 2013.
  4. Move all Discovery Search mailboxes to Exchange 2013.                                                                                                                                                   moving mailboxes
  5. Change the Client Access server FQDNs DNS host record to point to Exchange 2013 CAS/NLB/Windows NLB on both Public and Private DNS.
  6. Add exchange 2013 mailbox role servers in all the send connectors and remove the Exchange 2010/2007  servers.                                     Source Server
  7. Move your relay receive connectors to Exchange 2013 mailbox servers means create new relay receive connectors and add source server IP and configure same security setting as 2010/2007 receive connectors.
  8. Ensure you have configured Autodiscover correctly at AutoDiscoverServiceInternalUri properties if all CAS 2013.                                         Autodiscover
  9. If you are using public folders, make sure all the public folders have been migrated to Exchange 2013 Public Folders mailbox.
  10. Remove Exchange 2010 CAS arrays. This cmd will help:                                                                                                                                              “Get-clientaccessarray | remove-clientaccessarray”
  11. Make a list of applications that may be using Exchange 2007/2010 and then make sure to configure these applications to start using Exchange 2013 if necessary.


 Testing week without 2010/2007:

Shutdown all Exchange 2010/2007 servers for a week to test if their removal will cause any issue.


Remove Exchange Server 2010/2007


  1. Bring all legacy servers online means power start all servers which we shutdown in previous step.
  2. Remove all Public Folder replicas else Public Folder Database will not be removed.
  3. Remove Exchange 2010/2007 mailbox and Public folder databases from EMC or EMS then remove their files and folders.                       removeDB
  4. You can either run Exchange 2010/2007 or go to Control Panel to remove Exchange 2007/2010. On Program and Features screen click on Uninstall.             e Maintenance Mode page of the Exchange Server 2010/2007 Setup wizard begins the process of removing your Exchange installation. Click Next to continue.                                                                                                                                                                              2010 Uni 1
  5.  On the Server Role Selection page, uncheck in 2010/2007 all Exchange server roles and Exchange management tools to remove & in 2007 CCR remove passive node first then follow the same steps on active node. Click next to continue.                               2010 Uni 2
  6.  On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If the prerequisites check doesn’t complete successfully, review the Summary page and fix any issues that are preventing Setup from removing exchange 2010/2007. If the checks have completed successfully, click Uninstall to remove the entire installation of Exchange 2010.                                                                                                     2010 Uni 3
  7.  On the Completion page, click Finish.                                                                                                                                                                                       2010 Uni 4
  8. Remove the setup log files and folder located at c:ExchangeSetupLogs.
  9. Remove the Internet Information Services (IIS) from remove role or add/remove program and features.                                                     2010 Uni 5
  10. Remove C:inetpub folder.
  11. Remove any DNS entry left for CCR, DAG, NLB, Array, VIP, Autodiscover, OWA or anyother legacy DNS entry from internal and external DNS servers.
  12. Disjointed the legacy Exchange servers from the Domain.


That is it. You have removed all legacy Exchange servers from your Exchange ORG and AD Forest.




Prabhat Nigam

Microsft  MVP | Exchange Server

Team @MSExchangeGuru

15 Responses to ““Legacy Exchange Servers Decommission” Post Exchange 2013 Migration”

  1. Exchange 2010/2007 to 2013 Migration and Co-existence Guide « Says:

    […] […]

  2. NeWay Technologies – Weekly Newsletter #59 – September 5th, 2013 | NeWay Says:

    […] “Legacy Exchange Servers Decommission” Post Exchange 2013 Migration – […]

  3. NeWay Technologies – Weekly Newsletter #59 – September 6th, 2013 | NeWay Says:

    […] “Legacy Exchange Servers Decommission” Post Exchange 2013 Migration – […]

  4. Blog Posts of the Week (1st - 7th September 2013) - The South Asia MVP Blog - Site Home - TechNet Blogs Says:

    […] “Legacy Exchange Servers Decommission” Post Exchange 2013 Migration […]

  5. Prabhat Nigam Says:

    Someone pointed me that I should correct the doc as there is no discovery search in 2007 but I have not changed anything as this document belongs to both 2010 and 2007.

    So If you have 2007 don’t worry about arbitration and discover mailboxes. Just make sure you move all the mailboxes before deleting the database. Don’t worry about System Attendant mailbox. SA mailbox has stopped from 2010 but if you are left with PF migration then you need this mailbox.

  6. Ns Says:

    Hi, i am wondering what happens to federation that was created in exchange 2010, how do we move federation to (Org relation, sharing policy and federation )exchange 2013.

  7. Prabhat Nigam Says:

    All these you have mentioned are org level config and does not required to move.

  8. NS Says:

    Thanks Prabhat for the confirmation.

  9. mohammad Imran Says:

    I talk with one of the exchange expert he told me first install mail box and hub transport server than in the last uninstall CAS server role.
    Second is there any way to recover back user mailbox after it successfully moved to new server 2013 and having issue in new server.

  10. Prabhat Nigam Says:

    I think you wanted to say uninstall mailbox then…. When you are uninstalling after moving all pointer then it does not matter which role is getting uninstall first because all roles are already dead and we are just removing their existence from AD so that we can free up servers and reduce AD size. And also be ready for new version.

    Second – you should move the test mailboxes until you see 2013 is working fine. Even if you have to connect any mailbox back then you need to check it in the disconnected mailboxes of legacy servers DB and select reconnect from there.

  11. IMRAN Says:

    We are in coexistence phase when i check my
    Arbitration mailbox status its show me 5 mailbox three are in ex-2010 and 2 are in 2013 i dont understand why 2 Arbitration mail box in Exchange 2013.

    Name : SystemMailbox{1f05a927-0c67-4d4d-98c4-6b7bea3092de}
    Database : DAG01NDB01
    ServerName : ex1-2010

    Name : FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
    Database : DAG01NDB01
    ServerName : ex1-2010

    Name : SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
    Database : DAG01NDB01
    ServerName : ex1-2010

    Name : SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
    Database : DAG02DB01
    ServerName : ex1-2013

    Name : Migration.8f3e7716-2011-43e4-96b1-aba62d229136
    Database : DAG02DB01
    ServerName : ex1-2013

    kindly help.

  12. Prabhat Nigam Says:

    2 Arbitration mailbox in Exchange 2013
    This is because of 2 new mailbox are added by 2013 which were not there in Exchange 2010.
    You have to move all mailboxes from 2010 to 2013.. Have a look on the 2013 migration guide.

  13. movi Says:

    if we are migrating from 2010 t0 2013 or 2016, what we have to do with the cas array if it has the same name like, will the same name on cas 2016 will with that cas arrar ? communicate with

  14. Jatin kakkar Says:

    Hi Prabhat

    we have moved all PF as well connectors to 2013 as well mailboxes and PF to cloud. We have also upgraded Dir Synch tool to AAD connect as well. What should be the best process to decommishing exchange 2007 server ?

    Thanks JK

  15. Prabhat Nigam Says:

    Follow this blog. Let me know if any issue.

Leave a Reply




Do NOT follow this link or you will be banned from the site!