The local computer is responsible for expanding group membership
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2006-06-06
Microsoft® Exchange Server 2007 setup cannot continue because its attempt to uninstall a Hub Transport role responsible for expanding group membership failed.
Exchange 2007 setup requires that distribution list expansion be removed from the current Bridgehead server before the Hub Transport role can be uninstalled.
The expansion of distribution lists enables identification of individual recipients who belong to the distribution list to be identified, or the identification of additional distribution lists for expansion. An expanded distribution list can return the path for any required delivery status notification (DSN). DSNs notify the Microsoft Exchange administrator or e-mail sender of the status of a particular e-mail message. Additionally, distribution list expansion identifies whether Out of Office messages or automatically generated replies should be sent to the sender of the original message.
To resolve this issue, move distribution group expansion to another server and rerun Microsoft Exchange setup.
To change the expansion server for a distribution group or dynamic distribution group
Open the Exchange Management Console.
In the console tree, expand Recipient Configuration.
In the console tree, click Distribution Group.
Create a filter to view all distribution groups and dynamic distribution groups that use the current Bridgehead server as an expansion server.
In the action pane, click Create Filter.
In the property drop-down list, click Expansion Server.
In the operator drop-down list, click Equals.
At the value box, click the Browse button to select the Bridgehead server that currently acting as the expansion server.
The following step is optional.
Click Add Expression to specify additional filter criteria. Only messages that meet all filter criteria will be displayed.
Click Apply Filter. The results that meet the filter criteria are displayed.
In the results pane, click the distribution group you want to change the expansion server for, and then click Properties in the action pane.
On Properties, click the Advanced tab.
In the Expansion server drop-down list, select a specific server from the list or select Any server in the organization.
Repeat steps 5 through 7 for all distribution groups or for dynamic distribution groups that are using the Bridgehead server as their expansion server.