Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Phase 6: Install Communicator Web Access (2007 R2 release)

Communications Server 2007 R2

Topic Last Modified: 2009-07-01

Office Communications Server 2007 R2 Communicator Web Access is required for all reach capabilities as well as public switched telephone network (PSTN) dial-in conferencing. Live Communications Server users who attempt to use the Communicator Web Access (2007 R2 release) server URL will be redirected to the existing Live Communications Server 2005 Communicator Web Access server. The Office Communications Server 2007 R2 Communicator Web Access server cannot support direct log on by users who are still homed on Live Communications Server. Note that the Communicator Web Access (2007 R2 release) server cannot be directed to communicate directly with the Live Communications Server pool. The Communicator Web Access (2007 R2 release) server must be directed to communicate with the Office Communications Server 2007 R2 pool. For details about installing Communicator Web Access (2007 R2 release), see Office Communicator Web Access (2007 R2 Release) Deployment Guide.

You need to modify your Domain Name System (DNS) records for Communicator Web Access (2007 R2 release). Because both Live Communications Server and Communicator Web Access (2007 R2 release) installations may exist in the same organization, you can change your DNS record to point users at the new server running Communicator Web Access (2007 R2 release).

If you intend to operate both versions of Communicator Web Access to provide access during coexistence, you can create separate internal and external DNS records to support each Communicator Web Access version. Or, you can point both versions at the server running Communicator Web Access (2007 R2 release) after you configure the Communicator Web Access (2007 R2 release) server to redirect Communicator Web Access (2005 release) users to the server running Communicator Web Access (2007 R2 release). Live Communications Server users that attach to the Office Communications Server 2007 R2 Communicator Web Access will be redirected if you specify a redirection URL. For details about DNS requirements, see Configuring Communicator Web Access DNS Records in the Deploying Communicator Web Access (2007 R2 Release) documentation.

  1. Verify Communicator Web Access system requirements. For details, see Verifying Communicator Web Access Requirements in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  2. Prepare certificates. Plan your certificates for Communicator Web Access (2007 R2 release). For details about the certificate requirements, see Preparing Certificates for Communicator Web Access in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  3. Install and activate Communicator Web Access (2007 R2 release). After meeting system requirements and planning for the certificate needs, install and activate Office Communications Server 2007 R2 Communicator Web Access. For details, see Installing and Activating Communicator Web Access in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  4. Create a Communicator Web Access virtual server. Next, you must create a virtual server for Communicator Web Access (2007 R2 release). For details, see Creating a Communicator Web Access Virtual Server in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  5. Publish Communicator Web Access URLs. Following the creation of the first virtual server, you must publish the Communicator Web Access URLs. Communicator Web Access 2007 R2 offers expanded functionality and you must publish four different URLs to enable full utilization of your new Communicator Web Access server. For details, see Publishing Communicator Web Access URLs in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  6. Configure a redirect URL. To ensure that Communicator Web Access (2005 release) users who inadvertently access the new Communicator Web Access (2007 R2release) server are redirected to the Communicator Web Access (2005 release) server, you need to specify a redirect URL. For details, see Redirecting Users of Previous Releases in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  7. Install Communicator Web Access snap-in. You must install the Communicator Web Access snap-in on the Communicator Web Access server or on a client computer. For details, see Installing the Communicator Web Access Snap-in in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  8. Configure Communicator Web Access reverse proxy. If you intend to allow external access to the Communicator Web Access (2007 R2 release) server, you should configure a reverse proxy to allow external access to the service. Alternatively, you can reconfigure the existing reverse proxy to direct just the Communicator Web Access (2007 R2 release) clients to the new Communicator Web Access (2007 R2 release) service. If you do this, you need to configure two paths: one for the existing Communicator Web Access (2005 release) and one for the new Communicator Web Access (2007 R2 release). Failure to do this may result in the legacy user redirection not functioning properly for external users. For details, see Using a Reverse Proxy to Enable Remote User Access in the Deploying Communicator Web Access (2007 R2 Release) documentation.
  9. Configure the new settings in Communicator Web Access (2007 R2 release) Office Communicator Web Access (2007 R2 release) offers enhanced functionality and a greater feature set than Communicator Web Access (2005 release). For details, see Configuring New Communicator Web Access Settings in the Deploying Communicator Web Access (2007 R2 Release) documentation.

For details about the user experience during this phase, see User Experience during Phase 6 of Migration.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.