Step 4. Plan Your Deployment of Communicator Web Access

  • Article

[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

This topic describes the deployment process for the 2007 R2 version of Communicator Web Access, including the permissions required in each step of deployment and the documentation you can use during deployment.

Before you deploy Communicator Web Access, you need to verify that your system infrastructure and the server on which you will install Communicator Web Access meet the requirements that are described in Server Requirements in Server Requirements. When the environment is ready, you install certificates on the server, install Communicator Web Access, on the server, and then configure user accounts in Active Directory if you have not already done so. Table 1 provides an overview of the required steps. Deploying the 2007 R2 Version of Communicator Web Access provides detailed instructions.

Table 1.  Communicator Web Access deployment process

Phase Steps Permissions Documentation

Prepare DNS records.
  1. Create DNS records for internal Communicator Web Access servers and load balancer.
  2. Optionally, create DNS records for external Communicator Web Access servers, reverse proxy, and load balancer.

Administrators group

or

DNS Admins group

Active Directory and Domain Name Service Requirements

Prepare and install certificates.
  1. Request and install the following certificates in the certificate store for the local computer:
    • A computer certificate for MTLS that specifies the FQDN of the Communicator Web Access server as the common name.
    • A Web Server certificate for SSL/HTTPS.
  2. If necessary, install the certificate chain for the CA in the Trusted Root Certification Authorities node in the certificate store for the local computer.

Administrators group

Preparing Certificates for Communicator Web Access

Installing Certificates for Communicator Web Access

Deploy Office Communications Server 2007 R2.
  1. Install Office Communications Server.
  2. Activate Office Communications Server.
  3. Configure Office Communications Server.

various

Deploying Office Communications Server 2007 R2 Enterprise Edition

Install Communicator Web Access.
  1. Install Communicator Web Access.
  2. Activate Communicator Web Access.
  3. Create an internal virtual server.
  4. Optionally, create an additional internal virtual server.

Administrators group

DomainAdmins group

Installing and Activating Communicator Web Access

Creating a Communicator Web Access Virtual Server

Enable remote user access to Communicator Web Access.
  1. Create an external virtual server.
  2. Optionally, create an additional external virtual server.
  3. Optionally, use a reverse proxy to publish Communicator Web Access for remote users.

Administrators group

DomainAdmins group

Installing and Activating Communicator Web Access

Creating a Communicator Web Access Virtual Server

Using a Reverse Proxy to Enable Remote User Access

Enable and configure user accounts.
  1. In Active Directory Domain Services (AD DS), configure user accounts by enabling them for Office Communications Server 2007 R2.
  2. Enable user accounts for remote user access.

DomainAdmins group (to enable users)

RTCUniversalServerAdmins group (to configure users for remote user access)

In the Office Communications Server 2007 R2 deployment documentation:

Test the Communicator Web Access Web site.

Sign in to Communicator Web Access using the URI https://<internalserver_ FQDN> and, if remote user access is enabled, https://<externalserver_FQDN>.

Office Communications Server 2007 R2 user

Testing the Web Site