locked
Planning to migrate the User Mailboxes from Exchange 2013 to Exchange 2016,decommission Exchange 2013 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    We have installed Exchange server 2016 and added the DAG in Exchange 2013. Planning to move the Mailboxes from Exchange 2013 to 2016.

    Total Mailboxes are more than 10,000. At present 3000 Mailboxes i have moved.

    I wanted to know how to decommission the Exchange 2013 after Mailboxes migration done.Need to perform once all the Mailboxes migration done.

    It's taking a lot of time to migrate the User Mailboxes.

    Thanks-Sami

    Thanks-Sami

    Tuesday, August 20, 2019 5:40 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi samiurrahiman,

    Those steps may be useful to you:

    1. Migrate mailboxes, public folder, arbitration mailbox from Exchange 2013 to Exchange 2016.

    2. Delete DAG from Exchange 2013.

    3. Switch mailbox from Exchange 2013 to Exchange 2016(Point Autodiscover, Mail and MX record to Exchange 20016)

    4. Shut down Exchange 2013 and watch for a while whether there exist issue.

    5. If there doesn't exist issue, you can uninstall Exchange 2013 from your organization.

    Exchange Deployment Assistant will also be useful to you.

    Regards,

    Kyle Xu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, August 21, 2019 6:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi samiurrahiman,

    I am writing here to confirm with you how thing going now?

    If the above suggestion helps, please be free to mark it as an answer for helping more people.

    Regards,

    Kyle Xu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • Marked as answer by samiurrahiman Tuesday, September 3, 2019 9:01 AM
    Friday, August 23, 2019 9:19 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can do migrate Exchange Server 2013 mailboxes to 2016 manually by following steps given at https://www.kerneldatarecovery.com/blog/step-by-step-guide-for-migrating-exchange-server-2013-to-2016-part-1/

    For automated solution to migrate all 10,000 mailboxes and also check the moved mailboxes completion, you can use Kernel Migrator for Exchange software.

    The uninstalling process for Exchange Server 2013 post migration is described at https://www.kerneldatarecovery.com/blog/step-by-step-guide-for-migrating-exchange-server-2013-to-2016-part-6/

    ___________________________________________________________________

    Search, Recover Mailbox , Export Mailboxes, Contacts, Calendars, Tasks from Mailbox(EDBs) and Office 365. Migrate/Recover into On-Premises Exchange Server, Office 365, PST etc. with Kernel

    Tuesday, August 20, 2019 6:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Dav,

    How to remove the Exchange 2013 DAG on Exchange 2016. Powershell commands to remove the Exchange 2013 DAG. I'm unable to get much information on this.

    Thanks-Sami

    Thanks-Sami

    Tuesday, August 20, 2019 2:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Remove-DatabaseAvailabilityGroupServer -identity <dag name> -mailboxserver <server name>

    will remove a server from the DAG. Once that's done and all the mailboxes (including arbitration mailboxes) are removed, just uninstall Exchange from Programs and Features control panel and you're done.

    Tuesday, August 20, 2019 3:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It's a 3 step process.

    In the example below, EX1 is the server, DB1 the mailbox database and DAG1 the DAG.

    1. Remove any database copies:

    Remove-MailboxDatabaseCopy DB1\EX1

    2. Remove the server(s) from the DAG:

    Remove-DatabaseAvailabilityGroupServer DAG1 -MailboxServer EX1

    3. Remove the DAG:

    Remove-DatabaseAvailabilityGroupServer DAG1 -MailboxServer EX1


    You probably will want to verify the server is removed as a source server in send connector properties and not the server responsible for OAB generation.

    Then you can uninstall.

    Some more information and tips here:

    https://practical365.com/exchange-server/exchange-server-2010-2013-migration-removing-legacy-servers/

    http://techgenix.com/removing-exchange-server-mailbox-your-environment/

    EDIT - and since you are not removing Exchange altogether (but only Exchange 2013) make sure you target the correct servers and DAG!

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.


    Tuesday, August 20, 2019 6:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi samiurrahiman,

    Those steps may be useful to you:

    1. Migrate mailboxes, public folder, arbitration mailbox from Exchange 2013 to Exchange 2016.

    2. Delete DAG from Exchange 2013.

    3. Switch mailbox from Exchange 2013 to Exchange 2016(Point Autodiscover, Mail and MX record to Exchange 20016)

    4. Shut down Exchange 2013 and watch for a while whether there exist issue.

    5. If there doesn't exist issue, you can uninstall Exchange 2013 from your organization.

    Exchange Deployment Assistant will also be useful to you.

    Regards,

    Kyle Xu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, August 21, 2019 6:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi samiurrahiman,

    I am writing here to confirm with you how thing going now?

    If the above suggestion helps, please be free to mark it as an answer for helping more people.

    Regards,

    Kyle Xu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • Marked as answer by samiurrahiman Tuesday, September 3, 2019 9:01 AM
    Friday, August 23, 2019 9:19 AM