After you configure a pool, you need to add servers to the pool. Before you add a server to the pool, ensure that you have met the requirements described in the Office Communications Server Infrastructure Requirementssection of the Office Communications Server 2007 R2 Supported Topologies and Infrastructure Requirements documentation. Some requirements apply to specific server roles. For a chart of server roles that can be collocated on a single physical computer, see Supported Server Role Collocationin the same section.

Add a Server

When you add an Office Communications Server 2007 R2 to a consolidated topology, all the server roles are installed and activated on the server.

Important:
If you plan to use Windows Firewall, we strongly recommend that you enable and configure it before you install and activate Office Communications Server 2007 R2. If Windows Firewall is running when Office Communications Server is installed, the activation process automatically adds the exceptions needed for Office Communications Server. If Windows Firewall is not running when Office Communications Server is installed, you must start it after installation and then run the activation procedure to add the necessary exceptions. Alternatively, you can manually add the necessary exceptions to Windows Firewall. To identify the exceptions, search the installation log for "firewall exceptions."

Important:

If you plan to use Windows Firewall, we strongly recommend that you enable and configure it before you install and activate Office Communications Server 2007 R2. If Windows Firewall is running when Office Communications Server is installed, the activation process automatically adds the exceptions needed for Office Communications Server. If Windows Firewall is not running when Office Communications Server is installed, you must start it after installation and then run the activation procedure to add the necessary exceptions. Alternatively, you can manually add the necessary exceptions to Windows Firewall. To identify the exceptions, search the installation log for "firewall exceptions."

To install and activate an Enterprise Edition server in a consolidated configuration

Log on to the Office Communications Server where you will install all the server roles as a member of the Administrators group, the DomainAdmins group, and the RTCUniversalServerAdmins group.
Do one of the following:
- Insert the Microsoft Office Communications Server CD, and then click Enterprise Edition.
- If you are installing from a network share, browse to the \setup\amd64 folder on the network share, and then double-click setupEE.exe.
In the deployment tool, click Add Enterprise Edition Server to Pool.
At Add Server to Pool, click Run.
On the Welcome to the Add Server To Pool Wizardpage, click Next.
Review the license agreement, click I accept the terms in the license agreement, and then click Next.
On the Location for Server Filespage, do one of the following:
- To accept the default location where the files will be installed, click Next.
- To install the files at another location, click Browse, browse to the location where you want the files to be installed, and then click Next.

On the Ready to Install Componentspage, review the installation location and then click Next.

Note:
The Front End Server, Web Components Server, Web Conferencing Server, Audio/Video Conferencing Server, Application Sharing Conferencing Server, and four new unified communications applications are installed.

On the Select a Poolpage, select the pool that you created, and then click Next.
On the Select Main Service Accountpage, type the name of a new or existing service account to use to run the core Office Communications Server service on this server, type the account password, and then click Next.

Note:

The default account is RTCService. For a new account, ensure that you use a strong password that meets your organization’s Active Directory password requirements.
On the Select Component Service Accountpage, type the name of a new or existing service account that will run the Audio/Video Conferencing Server and Web Conferencing Server components on this server, type the account password, and then click Next.

Note:

The default account is RTCComponentService. For a new account, ensure that you use a strong password that meets your organization’s Active Directory password requirements.
On the Select Guest Accountpage, type the name of a new or existing account that you will use with Internet Information Services (IIS) for anonymous and external user access to Web conference content, type the account password, and then click Next.

Note:

The default account is RTCGuestAccessUser. For a new account, ensure that you use a strong password that meets your organization’s Active Directory password requirements.
Review the settings that you have configured, and then click Next.
When the wizard is finished, select the View the log file when you click ‘Finish’check box, and then click Finish.
In the log, verify that <Success>appears under the Execution Resultcolumn for each task, and then close the log window.

Note:
The default account is RTCService. For a new account, ensure that you use a strong password that meets your organization’s Active Directory password requirements.

Note:
The default account is RTCComponentService. For a new account, ensure that you use a strong password that meets your organization’s Active Directory password requirements.

Note:
The default account is RTCGuestAccessUser. For a new account, ensure that you use a strong password that meets your organization’s Active Directory password requirements.

Note:
If you added a server to a computer that did not already have the Windows Media Format Runtime installed, Setup installs the runtime automatically. After the runtime is installed, you might receive a message requiring you to restart the computer. If so, you must restart the computer right away and rerun the installation.

When you are finished, you are ready to configure certificates.