1. Do one of the following:

   • If you are using a 32-bit version of SQL Server, log on to your Office Communications Server Back-end Database server as a member of the Domain Admins group.
     
   • If you are using a 64-bit version of SQL Server, create the pool by using a computer with a 32-bit processor, such as the computer that you plan to use as the Front End Server. Log on to the 32-bit processor computer as a member of RTCUniversalServerAdmins and Domain Admins group and with user rights to create and modify SQL Server databases.
     

     Note:

     To create a pool on a server other than the Back-End Database, you must install SQL database management objects (SQL DMO) on the computer. To install SQL DMO, do one of the following:    If you are using SQL Server 2000 SP4, you can install SQL DMO by running SQL Server 2000 Setup and installing the client tools.    If you are using SQL Server 2005 SP1, you can install SQL DMO by using the SQL Server Setup CD and running SQLServer2005_BC.msi (for the 32-bit version). SQL Server 2005 DMO is backward compatible with SQL Server 2000.

     Note:
     If you want to use a Windows 2000 Server for your Back-End Database, verify that the Windows Script Host 5.6 is installed on the server. You can download this version at http://r.office.microsoft.com/r/rlidLCS?clid=1033&p1=2&p2=library&p3=updatewsh. By default, Windows Script Host 5.1 is installed on Windows 2000 Servers. Ensure that you have the latest version.

2. Insert the Microsoft Office Communications Server CD. The deployment tool starts automatically. If you are installing from a network share, go to the \Setup\I386 folder, and then double-click setup.exe.

3. In the deployment tool, do one of the following:

   • Click Deploy Pools in a Consolidated Topology.
     
   • Click Deploy Pools in an Expanded Topology.
     

4. At Create Enterprise Pool, click Run.

5. On the Welcome to the Create Enterprise Pool Wizard page, click Next.

6. On the Pool Name, Domain, and Back-End page, do the following:

   • Click Pool name, and then type a name for the new pool. The pool name cannot be the same as the server name.
     
   • Verify that Domain shows the FQDN of the domain where you will install the Office Communications Server Enterprise Edition server roles.
     
   • Confirm that Pool FQDN is the pool name followed by the domain that you specified.
     
   • Click SQL Server instance, and then enter the name of the SQL Server that will host the Office Communications Server Back-End Database and the name of the database instance. If you are using the default instance, specify only the name of the SQL Server. Otherwise, enter the SQL Server name and instance by using the following syntax: <servername>\<instance>.
     

     Note:
     The SQL Server instance must already exist before you run this step.

7. When you are finished, click Next.

8. On the Web Farm FQDNs page, do one or more of the following:

   • In an Enterprise pool with multiple Enterprise Edition Servers and one logical load balancer, click Internal Web farm FQDN, and then type the FQDN of the load balancer. This FQDN is used by internal users for client download of Web conferencing content, distribution group expansion, and Address Book files.
     
   • In an Enterprise pool with multiple Enterprise Edition servers and two logical load balancers, click Internal Web farm FQDN, and then type the FQDN of the load balancer that is used by the Web Components Server. This FQDN is used by internal users for client download of Web conferencing content, distribution group expansion, and Address Book files.
     
   • In an Enterprise pool with only one Enterprise Edition server and no load balancers, click Internal Web farm FQDN, and then type an internal FQDN. This FQDN is used by internal users for client download of Web conferencing content, distribution group expansion, and Address Book files. This FQDN must resolve to the IP address of this Enterprise Edition Server. We recommend that you use a dedicated FQDN for this purpose, rather than using the FQDN of your Enterprise Edition Server. Using a dedicated FQDN for this purpose allows you to scale your pool by adding a load balancer and additional servers, while keeping this URL unchanged.
     

     Note:
     In an expanded configuration, the internal Web farm FQDN is not necessarily the same as the FQDN of the Enterprise pool.

   • If you enable external user access or federated user access to Web conferences, under External Web farm FQDN (optional), type the FQDN that resolves to the external IP address of your reverse proxy. This FQDN is used by external users for client download of Web conferencing content, distribution group expansion, and Address Book files. It is also used by anonymous and federated users to download Web conference content. For more information about external user access, see the Microsoft Office Communications Server 2007 Edge Server Deployment Guide.
     

     Important:
     If you plan to deploy edge servers for external user access, we recommend that you configure the external URL during your Enterprise pool deployment. If you create this URL later, you will need to use the LcsCdm.exe command-line tool. For more information, see the Microsoft Office Communications Server 2007 Edge Server Deployment Guide.

9. When you are finished, click Next.

10. On the Reuse Existing Database page, click Next. We recommend that you leave this check box cleared. If you have an existing database and you select this option, you will lose existing data.

11. On the Locations for User Database page, to accept the default installation directories for the user database and transaction log files, click Next.

    Note:
    Setup automatically detects the best location for the files. If possible, place each database and transaction log file on a separate physical disk to improve performance. Do not place these files on the system disk or page file disk.

12. On the Meeting Content and Archive Location page, do the following:

    • Under Meeting content location, enter the address of the share that you created for storing Web conference presentations as described earlier in Storage Requirements, in Infrastructure Requirements and Prerequisites in Microsoft Office Communications Server 2007 Enterprise Edition. Use the format \\<computer name>\<Presentation>. You must specify a remote UNC path.
      
    • Under Meeting metadata location, enter the address of the share that you created in order to store metadata used by the pool’s Web Conferencing Server for the pool as described earlier in Storage Requirements, in Infrastructure Requirements and Prerequisites in Microsoft Office Communications Server 2007 Enterprise Edition. Use the format \\<computer name>\<Metadata>. You must specify a remote UNC path.
      
    • To enable archiving of Web conference data, select the Enable meeting archiving check box. Click Meeting archive location, and then enter the address of the share that you created in order to store Web conference compliance information as described earlier in Storage Requirements, in Infrastructure Requirements and Prerequisites in Microsoft Office Communications Server 2007 Enterprise Edition. Use the format \\<computer name>\<MeetingCompliance>. You must specify a remote UNC path.
      

      Note:

      The Create Pool Wizard accesses these shares and attempts to give read/write permission to the service accounts and groups used by Office Communications Server (for a complete list of these permissions see Appendix B: Permissions Created During Create Pool Task). If for some reason, the wizard cannot access any of these shares or cannot grant the correct permissions, the wizard fails. If you encounter this issue, ensure that the account you are using has permissions to administer the shares. As a last resort, you can bypass this step by using LcsCmd.exe with the /force switch. If you do this, you must grant the appropriate permissions on these shares manually. For more information, see the Microsoft Office Command Line Reference Guide.

13. When you are finished, click Next.

14. On the Address Book Server page, click Address Book Server file store, and then enter the UNC path of the share that you created for storing Address Book information as described earlier in Storage Requirements, in Infrastructure Requirements and Prerequisites in Microsoft Office Communications Server 2007 Enterprise Edition. Use the format \\<computer name>\<AddressBook>. You must specify a remote UNC path. When you are finished, click Next.

    Note:
    In Office Communications Server 2007, the Address Book Server is configured automatically. To change Address Book Server settings, see the Microsoft Office Communications Server 2007 Administration Guide.

    • To enable archiving, select the Archive instant messages check box.
      
    • To enable call detail recording, select the Archive call detail recording check box.
      

      Note:
      For more information about how to enable archiving and CDR, see the Microsoft Office Communications Server 2007 Planning Guide and the Microsoft Office Communications Server 2007 Archiving and CDR Guide.

15. When you are finished, click Next.

16. On the Ready to Create Enterprise Pool page, review the settings that you specified. If you are satisfied with them, click Next to begin installation.

17. When the files have been installed and the wizard is complete, select the View the log when you click Finish check box, and then click Finish.

18. In the log file, verify that <Success> appears under the Execution Result column. Look for <Success> Execution Result at the end of each task to verify pool creation completed successfully. Close the log window when you finish.

To create additional pools, repeat these procedures.

For a summary of the permissions that are granted during pool creation, see Appendix B: Permissions Created During Create Pool Task.