Exchange2010 cleanup does not exist, the Exchange Server is offline, and the system quorum mailbox is rebuilt

Existing EXCHANGE2010 environment has been offline exchange, because the system administrator operation was wrong, the BJ site directly shut down the Exchange server, did not follow the standard operation to clear, so that the existing environment still exists in the BJ site of the new database/copy, BJDAG,BJ for residual information such as Exchange servers. Also found in the Exchange environment, the system, Discovery search mailboxes are present in the BJ Exchange database, and each time in the Exchange console operation, the "Unable to contact BJ Exchange Server" warning message appears, which greatly affects the management experience.

The implementation steps are now organized as follows:

Current Status:

As you can see, both the system mailbox and the discovery search mailbox exist in the database sg-ydzs-01-bj of one of the Exchange servers in the BJ site.

Implementation steps:

1. Log in to the existing Szexchange server with the domain pipe contoso\administrator account;

2, try to migrate the system mailbox, Discovery Search mailbox to Szexchange server;

Execution of the command, the following error occurred:

Migrating system mailboxes does not work, consider deleting and rebuilding system mailboxes.

3. Clear the Ad account of the mailbox on the BJ Exchange database;

4, delete BJ site database and database copy;
Since both bjombx01/02 are offline, it is not possible to remove the database by first removing the database copy from the console and then deleting the primary database. When you delete a database directly from the console, the following error occurs:

The console cannot be deleted, consider removing it through Exchange PowerShell, with the following command:

The first error is that because the current copy of the EXSYSTEMDB-BJ database exists with the 02 server, the copy can be deleted after replacing BJOMBX01 in the command with BJOMBX02.
After the copy is deleted, you can go back to the console to delete the EXSYSTEMDB-BJ database, similar to the rest of the database (the database that holds the system mailbox and discovery search mailbox needs to be removed after the 5th step is completed).

5, delete the system mailbox, found the search mailbox account;
Currently, both the system mailbox and the discovery search mailbox exist in the SG-YDZS-01-BJ database, and to delete the database, you must first migrate the mailboxes to a different database. Because the migration mailbox failed in the 2nd step, the system mailbox and Discovery Search mailbox account are removed from the ad, and the system and discovery search mailboxes are rebuilt after the BJ Exchange Server information is cleaned up.

6, delete the last BJ database;

7, remove the Bjdag member server;

The console removes the member server from the Bjdag with the following error:

Attempting to remove a member server via PowerShell also has an error:

Since the member servers in the DAG cannot be removed following normal steps, consider deleting the Bjdag database high availability group directly.

8, delete bjdag;

An error occurred through both the Exchange console and PowerShell:

General deletions are not possible, only consider removing Bjdag from ADSI Edit, refer to step 11th.

9, delete BJmail.contoso.com array;

10. Delete the send, receive connector created for BJ Exchange Server;

11. Remove Bjdag and Bjexchange servers from ADSI;

Delete data in ADSI, be cautious!!!

1) Delete Bjdag in ADSI:

You can see that the console Bjdag has been removed:

2) Delete BJ Exchange Server in ADSI:

Back to the Exchange console to check the BJ database, the BJ server has been deleted.

12, the Active Directory/dns delete Bjocas and BJOMBX and other computer information;

13, ad sites and services to manually synchronize the ad information to other site servers;
Because the system mailbox and Discovery search mailbox accounts have been removed from the above steps, and the BJ Exchange Server information has been purged in ADSI and AD, it is best to manually synchronize the information in AD sites and services to DCs in other sites in order to prevent inconsistent data.

14, expand the structure, rebuild the system mailbox account;

On one of the Exchange servers, insert the same version of the exchange2010 CD and prepare to extend the schema. Setup.exe/preparead
As shown in the following:

After extending the schema, you can see in the DC that the system mailbox account has been generated:

15, enable the system mailbox, specify the database to hold the system mailbox;

16, set the system mailbox display name and size;

Use the following command to set the display name and send size of the mailbox:

Set-mailbox-arbitration-identity "SYSTEMMAILBOX{E0DC1C29-89C3-4034-B678-E6C29D823ED9}"-DisplayName "Microsoft Exchange "

Set-mailbox-arbitration-identity "federatedemail.4c1f4d8b-8179-4148-93bf-00a95fa1e042"-ProhibitSendQuota 1MB

17, check the system mailbox settings;

18, check the Exchange Server and DC information is synchronized;

At this point, exchange2010 cleanup does not exist, the Exchange server has been offline, and the rebuild system quorum mailbox has been completed.

Exchange2010 cleanup does not exist, the Exchange Server is offline, and the system quorum mailbox is rebuilt