{"id":3635,"date":"2019-06-10T09:35:37","date_gmt":"2019-06-10T09:35:37","guid":{"rendered":"https:\/\/www.kerneldatarecovery.com\/blog\/?p=3635"},"modified":"2021-03-25T06:48:00","modified_gmt":"2021-03-25T06:48:00","slug":"decommissioning-exchange-2013-after-a-cutover-migration","status":"publish","type":"post","link":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/","title":{"rendered":"Decommissioning Exchange 2013 After a Cutover Migration"},"content":{"rendered":"

The cutover migration is some of the best migration techniques to upgrade from migrating from on-premises Exchange to Office 365<\/a>. After completing the migration, it depends on your business’s structure to require an on-premises Exchange Server. The Administrator cannot uninstall the Exchange in a single attempt as it involves several checks and procedures. It is removing the Exchange Server from the system is called Decommissioning.<\/p>\n

Next, we will start discussing the essential checks and procedures prior to the decommissioning of Exchange Server.<\/p>\n

Decommission Exchange Server after Cut-Over Migration<\/h4>\n

First of all, confirm that the MX records are successfully changed to Exchange Online. After that, proceed with the processes given below:<\/p>\n

    \n
  1. Remove Old Connectors<\/strong><\/li>\n

    An administrator must check connectors to ensure that mails stop processing over the old server from which migration has taken place. You can carry out these steps in order to remove old connectors.<\/p>\n

      \n
    1. Open your new server Exchange Admin Center and go to Mail flow>Send Connectors.<\/li>\n
    2. Modify the old external connector and add the new servers.<\/li>\n
    3. Now, open the old source server and start the transport service again.<\/li>\n
    4. Pause the transport service in-between. This would stop old servers from processing any emails.<\/li>\n<\/ol>\n
    5. Disable Arbitration Mailboxes<\/strong><\/li>\n

      Even after migration of all the mailboxes and public folders from the Exchange Server to Office 365, the Exchange Server still contains some arbitration mailboxes also known as system mailboxes which need to be disabled or deleted. It is important to delete mailboxes from Exchange before its decommissioning as it could be a reason for error pop-up.<\/p>\n

      For disabling the arbitration mailboxes from old Exchange Server, run this command in Exchange Management Shell:<\/strong><\/p>\n

      \nGet-Mailbox -arbitration | Disable-mailbox -arbitration -disablelastarbitrationmailboxallowed<\/div>\n

      Now remove the remaining mailboxes (if any left) by running the command.<\/strong><\/p>\n

      \nGet-mailbox | disable-mailbox<\/div>\n
    6. Decommission Exchange Server<\/li>\n

      Finally, now you can try uninstalling or decommissioning the on-premises Exchange Server. For that, go to your Exchange system Control Panel. Click Programs and Features<\/strong> option. Then select your Microsoft Exchange Server from the list and click Uninstall<\/strong> or right-click on the Exchange Server and click Uninstall <\/strong>option.
      \n\"\"
      \nA message will pop-up, click Yes <\/strong>to confirm for your future action. You will get a display screen like this.
      \n\"\"
      \nOn this screen, click Next to move further. Next screen will be Readiness Checks page. Here, it will check for system mailboxes or mailboxes in queue.
      \n\"\"
      \nIf some mailboxes are not yet disabled, this check will throw an error saying that arbitration or other mailboxes are still running on your Exchange. Or, if you have disabled or removed all the mailboxes using above-mentioned commands in PowerShell, the next screen will be displayed.
      \n\"\"
      \nIt shows that the decommissioning of Exchange Server Setup is in progress, which will take some time to get completed. Once the process is completed, the message confirming for successful decommissioning of Exchange Server will be displayed. Hence, the Exchange Server is uninstalled finally.<\/ol>\n","protected":false},"excerpt":{"rendered":"

      The cutover migration is some of the best migration techniques to upgrade from migrating from on-premises Exchange to Office 365. After completing the migration, it depends on your business’s structure to require an on-premises Exchange Server. The Administrator cannot uninstall the Exchange in a single attempt as it involves several checks and procedures. It is […]<\/p>\n","protected":false},"author":11,"featured_media":7786,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_stopmodifiedupdate":false,"_modified_date":""},"categories":[7],"tags":[],"yoast_head":"\nDecommissioning Exchange 2013 After a Cutover Migration<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Decommissioning Exchange 2013 After a Cutover Migration\" \/>\n<meta property=\"og:description\" content=\"The cutover migration is some of the best migration techniques to upgrade from migrating from on-premises Exchange to Office 365. After completing the migration, it depends on your business’s structure to require an on-premises Exchange Server. The Administrator cannot uninstall the Exchange in a single attempt as it involves several checks and procedures. It is […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/\" \/>\n<meta property=\"og:site_name\" content=\"Data Recovery Blog - KDR Tools\" \/>\n<meta property=\"article:published_time\" content=\"2019-06-10T09:35:37+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-25T06:48:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2019\/06\/Decommissioning-Exchange-2013-After-A-Cutover-Migration-1-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t<meta property=\"og:image:height\" content=\"739\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Megha Sharma\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Megha Sharma\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Decommissioning Exchange 2013 After a Cutover Migration","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/","og_locale":"en_US","og_type":"article","og_title":"Decommissioning Exchange 2013 After a Cutover Migration","og_description":"The cutover migration is some of the best migration techniques to upgrade from migrating from on-premises Exchange to Office 365. After completing the migration, it depends on your business’s structure to require an on-premises Exchange Server. The Administrator cannot uninstall the Exchange in a single attempt as it involves several checks and procedures. It is […]","og_url":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/","og_site_name":"Data Recovery Blog - KDR Tools","article_published_time":"2019-06-10T09:35:37+00:00","article_modified_time":"2021-03-25T06:48:00+00:00","og_image":[{"width":1600,"height":739,"url":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2019\/06\/Decommissioning-Exchange-2013-After-A-Cutover-Migration-1-1.jpg","type":"image\/jpeg"}],"author":"Megha Sharma","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Megha Sharma","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/#article","isPartOf":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/"},"author":{"name":"Megha Sharma","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#\/schema\/person\/2d2712dd0b1647e9d0ee3be78ad0daf1"},"headline":"Decommissioning Exchange 2013 After a Cutover Migration","datePublished":"2019-06-10T09:35:37+00:00","dateModified":"2021-03-25T06:48:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/"},"wordCount":483,"commentCount":0,"publisher":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#organization"},"articleSection":["Tips & Tricks"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/","url":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/","name":"Decommissioning Exchange 2013 After a Cutover Migration","isPartOf":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#website"},"datePublished":"2019-06-10T09:35:37+00:00","dateModified":"2021-03-25T06:48:00+00:00","breadcrumb":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/decommissioning-exchange-2013-after-a-cutover-migration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.kerneldatarecovery.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Decommissioning Exchange 2013 After a Cutover Migration"}]},{"@type":"WebSite","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#website","url":"https:\/\/www.kerneldatarecovery.com\/blog\/","name":"Data Recovery Blog - KDR Tools","description":"Data Recovery Blog - KDR Tools","publisher":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.kerneldatarecovery.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#organization","name":"Data Recovery Blog - KDR Tools","url":"https:\/\/www.kerneldatarecovery.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2019\/04\/logo.png","contentUrl":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2019\/04\/logo.png","width":161,"height":47,"caption":"Data Recovery Blog - KDR Tools"},"image":{"@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#\/schema\/person\/2d2712dd0b1647e9d0ee3be78ad0daf1","name":"Megha Sharma","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.kerneldatarecovery.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2021\/11\/Megha.jpg","contentUrl":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2021\/11\/Megha.jpg","caption":"Megha Sharma"},"url":"https:\/\/www.kerneldatarecovery.com\/blog\/author\/megha-sharma\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/posts\/3635"}],"collection":[{"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/comments?post=3635"}],"version-history":[{"count":7,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/posts\/3635\/revisions"}],"predecessor-version":[{"id":7792,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/posts\/3635\/revisions\/7792"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/media\/7786"}],"wp:attachment":[{"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/media?parent=3635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/categories?post=3635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kerneldatarecovery.com\/blog\/wp-json\/wp\/v2\/tags?post=3635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}