Shulou(Shulou.com)06/02 Report--

There is an offline exchange in the existing Exchange2010 environment. Due to the misoperation of the system administrator at that time, the exchange server in the BJ site was shut down directly and did not follow the standard operation, so there is still residual information in the existing environment, such as newly-built databases / replicas and BJDAG,BJ exchange servers in the BJ site. At the same time, it is found that the system and the search mailbox in the exchange environment all exist in the BJ exchange database, and every time you operate in the exchange console, there will be warning messages such as "unable to contact the BJ exchange server", which greatly affects the management experience.

The implementation steps at that time are sorted out as follows:

Current status:

As you can see, both the system mailbox and the discovery search mailbox are stored in the database SG-YDZS-01-BJ of an exchange server in the BJ site.

Implementation steps:

1. Log in to the existing SZexchange server with the domain administration contoso\ administrator account

2. Try to migrate system mailboxes and find search mailboxes to SZexchange server

Execute the command, and the following error occurs:

Migrating the system mailbox does not work. Consider deleting and rebuilding the system mailbox.

3. Clear the AD account of the mailbox on the BJ exchange database

4. Delete the database and database copy of the BJ site

Since both BJOMBX01/02 are offline, you cannot delete the database by deleting the copy of the database and then deleting the primary database in the console. When you delete a database directly in the console, the following error occurs:

The console cannot be deleted. Consider deleting it through exchange powershell. The command is as follows:

The first error report is that because the current copy of the ExSystemDB-BJ database exists on the 02 server, you can delete the copy after replacing BJOMBX01 with BJOMBX02 in the command.

After the copy is deleted, you can go back to the console to delete the ExSystemDB-BJ database, and the rest of the database is similar (the database that stores the system mailbox and discovers the search mailbox, need to be deleted after step 5).

5. Delete the system mailbox and find the search mailbox account.

Currently, both the system mailbox and the discovery search mailbox exist in the SG-YDZS-01-BJ database. To delete the database, you must first migrate these mailboxes to other databases. Because the mailbox migration failed in step 2, delete the system mailbox and the discovery search mailbox account from the AD first, and then rebuild the system and discover the search mailbox after the BJ exchange server information is cleaned up.

6. Delete the last BJ database

7. Remove member servers in BJDAG

The console removes the member servers from the BJDAG with the following error:

An attempt was made to delete a member server through powershell, and an error also occurred:

Since you cannot remove member servers in dag by following the normal steps, consider deleting the bjdag database high availability group directly.

8. Delete BJdag

An error has occurred through both the exchange console and powershell:

Regular deletion is fruitless, so you can only consider removing bjdag from the ADSI editor, refer to step 11.

9. Delete the BJmail.contoso.com array

10. Delete send and receive connectors created for the BJ Exchange server

11. Remove bjdag and BJexchange servers from ADSI

Delete data in ADSI, you must be careful!

1) Delete bjdag from ADSI:

You can see that the bjdag in the console has been deleted:

2) Delete BJ exchange server from ADSI:

Go back to the exchange console to check the BJ database and see if all the BJ servers have been deleted.

12. Delete computer information such as BJOCAS and BJOMBX from active Directory / DNS

13. Manually synchronize AD information to other site servers in AD sites and services

Because in the above steps, the system mailbox and the account that found the search mailbox have been deleted, and the BJ Exchange server information has been cleared in ADSI and AD, in order to prevent data inconsistency, it is best to manually synchronize the information in "AD sites and Services" to DC in other sites.

14. Expand the architecture and rebuild the system mailbox account

On one of the exchange servers, insert the same version of the exchange2010 CD to prepare to expand the architecture. Setup.exe / prepareAD

As shown in the following figure:

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

15. Enable the system mailbox and specify the database to store 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. View system mailbox settings

18. Check whether the exchange server and DC information are synchronized.

At this point, exchange2010 cleanup does not exist, the exchange server has been offline, and the reconstruction of the system arbitration mailbox has been completed.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.