Install Standard Edition Server
Topic Last Modified: 2009-05-06
You install Microsoft Office Communications Server 2007 R2 Standard Edition by running the Deployment Tool. You can install Standard Edition from the Office Communications Server 2007 R2 CD or from a network share.
Note
Before you install Office Communications Server Standard Edition, ensure that Internet Information Services (IIS) is installed. IIS is a required component for Web Components Server.
If you want to install Office Communications Server 2007 R2 on the Windows Server 2008 operating system, we strongly recommend that you ensure Windows Firewall is running when you install and activate Office Communications Server 2007 R2. If Windows Firewall is not running when Office Communications Server 2007 R2 is installed, you must start it after installation and then run the activation procedure that follows to open the required ports. Alternatively, you can open the ports in the Windows Firewall manually by referring to the Configure Windows Firewall for SQL Server 2008 Access.
When you run the Deployment Tool, Setup automatically installs Microsoft SQL Server 2005 Express Edition with SP2 for the back-end database. You do not need to install this component separately.
The Microsoft Visual C++ Redistributable Package, Microsoft .NET Framework 3.5, and the Windows Media Format Runtime must also be installed on the computer for Office Communications Server 2007 R2 to run correctly. If these prerequisites are not already installed on the computer, Setup prompts you for them and, if you choose, installs them automatically. (You are required to install these components in order to continue Setup.)
Important
To install the Office Communications Server snap-in, the Communicator Web Access snap-in, the Response Group Service snap-in, and the deployment command-line tool, LcsCmd.exe, click Administrative Tools in the Deployment Wizard. These tools are not installed by default in Office Communications Server 2007 R2.
To deploy Office Communications Server Standard Edition
Log on to the server where you want to install Standard Edition server as a member of the DomainAdmins and the RTCUniversalServerAdmins groups or with equivalent user rights.
Do one of the following:
- Insert the Microsoft Office Communications Server 2007 R2 CD, and then click Standard Edition.
- Install from a network share by browsing to the \setup\amd64\ folder and double-clicking setupSE.exe.
Click Deploy Standard Edition Server.
At Deploy Server, click Run.
On the Welcome to the Deploy Server Wizard page, click Next.
Review the license agreement, click I accept the terms in the license agreement to proceed, and then click Next.
On the Location for Server Files page, do one of the following:
- To install the files at the default location, 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 Application Configuration page, do the following:
To activate the Conferencing Attendant application, select the Conferencing Attendant check box.
To activate the Conferencing Announcement Service, select the Conferencing Announcement Service check box.
To activate the Response Group Service, select the Response Group Service check box.
To activate the Outside Voice Control, select the Outside Voice Control check box.
Note
For details about the applications on this page, see the New Server Applications topic in the Office Communications Server 2007 R2 Getting Started documentation.
On the Main Service Account for Standard Edition Server page, type the name of a new or existing service account that will run the core Office Communications Server service on this computer, type the password for the account, 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.
When you create a new account, activation might fail until the account has been replicated in Active Directory Domain Services (AD DS). If activation fails, wait until the account has been replicated, and then try again.On the Component Service Account for this Standard Edition Server page, 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 computer, type the password for the account, 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 AD DS password requirements.
On the Web Farm FQDNs page, do one or more of the following:
- Verify that Internal web farm FQDN displays your server fully qualified domain name (FQDN). This FQDN is used by internal users for client download of Web conferencing content, distribution group expansion, and Address Book information.
- If you plan to 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 information. It is also used by anonymous and federated users to download Web conference content. For details about external user access, see the External User Access section in the Office Communications Server 2007 R2 Planning and Architecture documentation and also the Office Communications Server 2007 R2 Edge Server Deployment Guide documentation.
Important
If you plan to deploy Edge Servers for external user access, we recommend that you configure the external URL during your Standard Edition server deployment. If you create this URL later, you need to use the LcsCmd.exe command-line tool. For details, see the “Before You Begin” section of the Configure a Reverse Proxy topic in the Deploying Edge Servers for External User Access documentation.
When you are finished, click Next.
On the Location for Database Files page, to accept the default directories for 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.
On the Ready to Deploy Server page, review the settings that you specified, and then click Next.
When the files are installed and the wizard has completed, select the View the log when you click Finish check box, and then click Finish.
In the log file, verify that <Success> appears under the Execution Result column, look for <Success> Execution Result at the end of each task, and then close the log window.