Article
01/30/2017

Communicator Web Access

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

Communicator Web Access (2007 release) requires a supported Office Communications Server 2007 deployment prior to installation. The Communicator Web Access server does not support collocation with any Office Communications Server 2007 server role. Two or more physical (as opposed to virtual) Communicator Web Access servers behind a hardware load balancer are supported.

Physical separation of internal and external user traffic by using different physical Communicator Web Access server computers is strongly recommended but not required. Separation of internal and external user traffic by using application isolation mode in IIS 6.0 is also supported.

Communicator Web Access supports the following internal client configurations:

Internal clients with or without Windows operating systems
Internal clients with and without the Windows Internet Explorer® Internet browser
Internal clients that are not domain members, as well as those that are domain members

The following server configurations are supported:

A single Communicator Web Access server
Two or more Communicator Web Access servers behind a hardware load balancer for internal clients
Office Communicator Web Access (2007 release) deployed side-by-side with an Office Communicator Web Access (2005 release) server that is collocated with Microsoft Office Live Communications Server 2005 with SP1 Standard Edition
Office Communicator Web Access (2007 release) deployed side-by-side with an Office Communicator Web Access (2005 release) server that is collocated with a Live Communications Server 2005 with SP1 Enterprise Edition server in an Enterprise pool

Communicator Web Access supports the following external user scenarios:

SSL Web publishing of the external Communicator Web Access virtual server by using a reverse proxy (recommended)
Direct access to the external Communicator Web Access virtual server by using SIP over TLS without SSL Web publishing of the external Communicator Web Access virtual server instance by using a reverse proxy (supported but not recommended)

IIS 6.0 Virtual Server/Isolation Configuration

The following Communicator Web Access virtual server configurations are supported:

Internal virtual server instance only (no external virtual server instance)
- One internal Communicator Web Access virtual server instance only for internal users. (VPN users are considered internal users.)
- No external Communicator Web Access virtual server instances with no remote users. (VPN users are considered internal users.)
- Multiple internal Communicator Web Access virtual server instances on the same computer or on different computers, all of which support only internal users. (VPN users are considered internal users.)
Both internal and external virtual server instances
- One or more external Communicator Web Access virtual server instances on a computer that also has one or more internal virtual server instances.
- One or more external Communicator Web Access virtual server instances on a different computer from one that is running one or more internal Communicator Web Access virtual server instances.
- One external Communicator Web Access virtual server instance on one computer with one or more internal Communicator Web Access Server virtual server instances on one or more different computers.

SSL Web Publishing Configuration

Using a reverse proxy with SSL to publish an external Communicator Web Access virtual server instance to the Web for remote users is recommended but not required.