How to Uninstall a Stubborn Exchange Server

The Active Directory (AD) schema is extended. New class and attribute definitions are created.

The configuration information in AD is modified. Under the Configuration partition in the Services section, a new container named Microsoft Exchange is created. This container represents the Exchange organizational hierarchy.

New user groups are created in AD. For example, in Exchange Server 2003 and Exchange 2000 Server, two user groups—Exchange Domain Servers and Exchange Enterprise Servers—are created in the domain's Users container. The Exchange servers in a domain are members of the Exchange Domain Servers group. The Exchange Domain Servers group is a member of the Exchange Enterprise Servers group. In Exchange Server 2010 and Exchange Server 2007, several new groups are created under a new organizational unit named Microsoft Exchange Security Groups, which resides in the root domain of the forest.

The server's registry is changed. The changes occur in two registry keys: HKLMSoftware and HKLMSystemCurrentControlSetServices.

A folder hierarchy for the Exchange installation files is created under a folder specified during the installation.

You don't need to worry about the AD schema changes that the Exchange installation made. These changes can't be reversed because you can't delete schema objects and attributes. Even if you could, it wouldn't be a good idea. If you have multiple Exchange servers, the remaining servers need these schema objects and attributes. Plus, if you uninstall your lone Exchange server, the schema objects and attributes that remain won't cause any problems. In fact, if you should later decide to install Exchange again, it would take a shorter time because the schema have been already changed.

The server's configuration information in AD can be removed using the ADSI Edit console (ADSIEdit.msc). In Windows Server 2003 and Windows 2000 Server, this tool is one of the Support Tools, which aren't install by default. In Windows 2008, the ADSI Edit console is installed by default. To remove the configuration information, open the ADSI Edit console, and navigate to ServicesMicrosoft ExchangeExchangeOrganizationNameAdministrativeGroupsRelatedOrganizationGroupServerswhere ExchangeOrganizationName is the name of your Exchange organization. After you locate the server you want to uninstall, simply delete it.

Alternatively, you can delete the Microsoft Exchange container altogether. By doing this, you delete the Exchange organization's information in AD. However, be aware that removing a server this way isn't supported by Microsoft unless you're instructed to do so by its Customer Service and Support (CSS) staff. In addition, you run the risk of leaving semi-deleted objects or partially mail-enabled objects in AD. This isn't important if you don't plan to install Exchange into a forest again, but it is important if you do, as you can run into problems. To mitigate these risks, I delete the Microsoft Exchange container after moving the mail-enabled objects to other servers or after deleting them.

You can delete the user groups related to the Exchange server, but this step isn't necessary. You should do this only if you want to undo all the changes.

You need to delete the following registry keys on the Exchange server:

In the HKLMSystemCurrentControlSetServices key, delete the keys that were created for the Exchange Server services. In Exchange 2010 and Exchange 2007, all the keys related to the Exchange Server services start with MSExchange (e.g., MSExchangeIS). In Exchange 2003 and Exchange 2000, most of the keys also start with MSExchange. However, three keys have names that don't include this string. They are IMAP4Svc, POP3Svc, and RESvc.

You should delete the files under the root Exchange Server folder.