XADM: How to Assign a Server to a Routing Group

This article describes two methods to assign a server to a routing group. The first method explains how to assign the server during the installation of Microsoft Exchange 2000 and the second method explains how to assign the server after the installation process is finished.

How to Assign a Server to a Routing Group During Installation

A server can be assigned to a routing group during the installation phase only if the routing group already exists. By default, only one administrative group, the First Administrative Group, exists. Within this group, one routing group is available, the First Routing Group. During installation, you can only install the server in the default routing group for the default administrative group.

To create new routing groups, you must create them in an administrative group using Exchange System Manager after the Exchange 2000 Server is installed. You can choose your routing group from a list. However, you can only choose routing groups that are available within the administrative group. Therefore, during the installation, you must choose the administrative group before you choose the routing group.

Routing groups are created within administrative groups. You can create several administrative groups each with multiple routing groups.

For additional information about administrative and routing groups, click the article number below to view the article in the Microsoft Knowledge Base:

How to Assign a Server to a Routing Group After Installation

After a server is installed in a routing group, you can reassign it to a different routing group using a drag-and-drop operation in Exchange System Manager.

NOTE: The source routing group and the destination routing group to which the server is moved should belong to the same administrative group.

To assign a server to a routing group, follow these steps:

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. In the left pane of Exchange System Manager, expand the Administrative Groups container so that all administrative groups within the container are visible.
3. Expand the container for the administrative group where the server was assigned during the installation phase.
4. Expand the Routing Groups container to see all routing groups within the administrative group.
5. Expand the container for the routing group (source RG) where the server was assigned during the installation phase.
6. Expand the Members container for the routing group (source RG) that you expanded in step four. The stubs should be displayed for all the servers assigned to this routing group.
7. Expand the container for the routing group (destination RG) where the server needs to be reassigned.
   
   NOTE: The routing group needs to be a member of the same administrative group that you expanded in step three.
8. Expand the Members container for the routing group (destination RG) that you expanded in step seven. The stubs should be displayed for all the servers assigned to this routing group.
9. Select a server stub from the Members container of the source RG that you expanded in step six and drag it to the Members container of destination RG that you expanded in step eight.