351 Step 3: Creating the Exchange Virtual Servers The final step in configuring Exchange Server 2003 on a cluster is to create the Exchange Virtual Servers. Step 3 includes the following tasks: 1. Create the resource group to host the Exchange Virtual Server. A separate cluster group is required for each Exchange Virtual Server. Exchange cluster resources should not be added to the default cluster group, and adding an Exchange Virtual Server to the cluster group is not supported. For detailed steps, see How to Create a Resource Group for an Exchange Virtual Server in a Windows Server Cluster. 2. Create an IP Address resource. For detailed steps, see How to Create an IP Address Resource for an Exchange Virtual Server in a Windows Server Cluster. 3. Create a Network Name resource. For detailed steps, see How to Create a Network Name Resource for an Exchange Virtual Server in a Windows Server Cluster. 352 4. Add a disk resource to the Exchange Virtual Server. For detailed steps, see How to Move an Existing Disk Resource into an Exchange Virtual Server in a Windows Server Cluster. 5. Create an Exchange Server 2003 System Attendant resource. For detailed steps, see How to Create an Exchange System Attendant Resource for an Exchange Virtual Server in a Windows Server Cluster. 6. Create any additional Exchange Virtual Servers. You need to repeat these tasks for each Exchange Virtual Server you want to add to your cluster. For example: If you are configuring a two-node active/passive Exchange Server 2003 cluster, you create only one Exchange Virtual Server. Therefore, you would only perform these tasks once. If you are configuring a four-node 3 active/1 passive Exchange Server 2003 cluster, you create three Exchange Virtual Servers. Therefore, you would perform these tasks three times. Before performing these tasks, familiarize yourself with the requirements necessary for creating Exchange Virtual Servers (Table 4). 353 Table 4 Exchange Virtual Server requirements Area Requirements Permissions If you are creating either the first Exchange server in the organization or the first Exchange server in the domain, the account must be a member of a group that has the Exchange Full Administrator role applied at the organizational level. If the server is not the first Exchange server in the organization and is not the first server in the domain, the account must be a member of a group that has the Exchange Full Administrator role applied at the administrative group level. File system MDBDATA folder must be empty. 354 Area Requirements Cluster resources Network Name resource must be online. Physical disk resources must be online. Other The FQDN of the Exchange Virtual Server may not match SMTP proxy domain of any recipient policy. Enforce Active/Active restrictions. Exchange Virtual Server(s) are installed into their own cluster group(s). 355 Adding a Disk Resource to the Exchange Virtual Server You must add a disk resource for each disk that you want to associate with the Exchange Virtual Server. This section includes links to the following procedures: If the disk resource you want to add already exists, follow the procedure to move an existing disk resource. For detailed steps, see How to Move an Existing Disk Resource into an Exchange Virtual Server in a Windows Server Cluster. If the disk resource you want to add does not yet exist, follow the procedure to create a new disk resource. For detailed steps, see How to Create a Physical Disk Resource for an Exchange Virtual Server in a Windows Server Cluster. If you are using mounted drives, follow the procedure to add mounted drives. This procedure applies only to server clusters running Windows Server 2003. Mounted drives are not supported in Windows 2000 server clusters. For detailed steps, see How to Add a Mounted Drive to an Exchange Virtual Server in a Windows Server Cluster. 356 Note: To prevent possible damage to your hard disk, see "Checklist: Creating a server cluster" in Windows 2000 Help or "Planning and preparing for cluster installation" in Windows Server 2003 Help before connecting a disk to a shared bus. After you successfully create the Exchange System Attendant resource, Exchange System Attendant creates the following additional resources for the Exchange Virtual Server automatically (Figure 3): Exchange Information Store Instance Exchange Message Transfer Agent Instance Exchange Routing Service Instance SMTP Virtual Server Instance Exchange HTTP Virtual Server Instance Exchange MS Search Instance 357 For improved security, the Windows IMAP4 and POP3 protocol services are no longer enabled by default on servers that are running Windows Server 2003. Similarly, the IMAP4 and POP3 protocol resources are no longer created by default upon creation of an Exchange Server 2003 Virtual Server. For information about adding IMAP4 and POP3 resources, see "Managing Exchange Clusters," in the Exchange Server 2003 Administration Guide (http://go.microsoft.com/fwlink/?LinkId=47617). Note: The Message Transfer Agent Instance resource is created only in the first Exchange Virtual Server added to a cluster. All Exchange Virtual Servers in the cluster share the single Message Transfer Agent Instance resource. 358 Figure 3 Exchange Virtual Server resources Repeating Step 3 for the Next Exchange Virtual Server For each Exchange Virtual Server you want to create, repeat all the procedures in "Step 3: Creating the Exchange Virtual Servers." For example, if you are creating a four-node active/passive cluster with three Exchange Virtual Servers, repeat this step two more times. If you are creating a two-node active/active cluster, you would repeat this step one more time. 359 Supporting Multiple SMTP Domains in a Front-End and Back-End Topology If you run Exchange Server 2003 in a front-end and back-end topology that includes multiple SMTP namespaces, you must create additional HTTP virtual servers in the Exchange Virtual Server for each domain namespace. For example, if contoso.com hosts Exchange Server 2003 for both tailspintoys.com and wingtiptoys.com, three virtual servers are necessary—the default virtual server, a virtual server for tailspintoys.com, and a virtual server for wingtiptoys.com. This configuration provides maximum flexibility in determining which resources are available to each hosted company. For information about front-end and back-end server architecture, see "Upgrading Front-End and Back-End Servers" in Upgrading from Exchange 2000 Server to Exchange Server 2003. For information about planning a front-end server and for more conceptual information about configuring front-end and back-end servers running Exchange Server 2003, see the guide Planning an Exchange Server 2003 Messaging System (http://go.microsoft.com/fwlink/?LinkId=47584) To configure a clustered back-end server to support multiple SMTP domains, you must map each front-end server to the nodes of your cluster, so that any node can accept proxy requests from any front-end server in your organization. 360 For detailed steps, see How to Support Multiple SMTP Domains in a Front-End and Back-End Topology. Figure 4 illustrates a front-end/back-end configuration that uses Exchange clustering. Figure 4 Front-end and back-end configuration that uses Exchange clustering . back-end servers running Exchange Server 2003, see the guide Planning an Exchange Server 2003 Messaging System (http://go .microsoft. com/fwlink/?LinkId=47584) To configure a clustered back-end server. back-end server architecture, see "Upgrading Front-End and Back-End Servers" in Upgrading from Exchange 2000 Server to Exchange Server 2003. For information about planning a front-end server. default on servers that are running Windows Server 2003. Similarly, the IMAP4 and POP3 protocol resources are no longer created by default upon creation of an Exchange Server 2003 Virtual Server.