因为一台EXCHANGE服务器没有正常UNINSTALL，就转作它用了。

所以需要人工从AD里清除相关信息。

操作指南如下：

我按此操作，一切顺利。

但真的要小心再小心，确认再确认。不然，，真的会一抖手成千古恨的。

http://www.wackytechtips.com/force-removal-of-exchange-server-remove-exchange-2010-manually/

Force Removal of Exchange Server – Remove Exchange 2010 Manually

If you want to be the best at something you gotta start somewhere, get stuck somewhere & find your way out.

Today I am going to show you how to remove Exchange Server from a network when you are unable to uninstall it / You have created a new server & want to get rid of the old server but it wont go away easily.

Word of Warning!

Now I am doing this on VMware Workstation Test Lab and you will have to be very very careful and double check what you are doing before you do it if you are on a production environment , because deleting something from any of these steps will cause serious network & server instability if not done correctly. The recommended way to remove an Exchange server from your network is to properly uninstall it. If the installation no longer exists, then there is also the option of installing a new server with the same name and restoring the original Exchange configuration. However, I have not explored this path as it appears to be much more time consuming.

If you removed an Exchange 2007/2010/2013 server from your network without properly uninstalling it, either because you experimented with it on a test box or on a virtual machine, or because the computer got hit by an earthquake, or simply because you didn’t know better, you may notice that the server continues to exist in the network’s Active Directory and shows up in the Exchange Management Console of your new exchange server.

This Post will help you clean those aftermath in your domain controller without having to reinstall your entire Infrastructure.

Removing AD Configuration

The list of Exchange servers on the domain is stored in the Active Directory configuration. Following steps below to remove the obsolete server:

1. Log on to the Domain Controller.

2. From the Start menu select Run… and enter adsiedit.msc to launch the ADSI Edit tool

3. In the tool, right-click ADSI Edit and select Connect To…

4. In the Connection Settings dialog under Select a well known Naming Context select Configuration and click OK

5. Navigate to CN=Configuration [domain] → CN=Services → CN=Microsoft Exchange → CN=[organization] → CN=Administrative Groups → CN=Servers

6. Right-click and Delete the container for the offending Exchange server.

Removing Mailboxes

The Active Directory also stores information about the mailboxes that were located on the non-existent server. To remove these, perform the following steps in the ADSI Edit tool:

1. Navigate to CN=Configuration [domain] → CN=Services → CN=Microsoft Exchange → CN=[organization] → CN=Administrative Groups → CN=Databases

2. Identify the Mailbox Database containers that belonged to the lost server and Delete them.

Make sure that you are not deleting working mailboxes from the list, if you delete any by mistake you will have to delete & recreate the entire user using Active Directory Users & Computers. If there are multiple Exchange servers on the network, the Mailbox Database folders to delete can easily be identified by clicking on the folder and checking the Name field of the first entry, which should contain the name of the lost computer. Do not delete references to databases belonging to other Exchange servers!

Removing Security Settings

Now that the server is removed, some other settings need to be cleaned up as well. Perform the following additional steps on the domain controller:

1. Launch Server Manager

2. Navigate to Roles → Active Directory Domain Services → Active Directory Users and Computers [domain] → [domain] → Microsoft Exchange Security Groups

3. Remove the computer from the members list of Exchange Servers

4. Remove the computer from the members list of Exchange Trusted Subsystem.

If the computer was removed from the network altogether, you may also want to remove it from the Active Directory’s list of computers, as well as the DNS Server’s Forward Lookup Zones.

Please note that the above steps will work for Exchange 2007 / 2010 & 2013