[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-18

For both Standard Edition servers and Enterprise pools, the Microsoft Communications Server 2010 installer creates virtual directories in IIS for the following purposes:

Communications Server requires the following IIS modules to be installed:

The following table lists the URIs for the virtual directories for internal access and the file system resources to which they refer..

Virtual Directories for Internal Access

Feature Virtual Directory URI Refers to

Address Book Server

https://<Internal FQDN>/ABS/int/Handler

Location of Address Book Server download files for internal users.

Client updates

http://<Internal FQDN>/AutoUpdate/Int

Location of update files for internal computer-based clients.


http://<Internal FQDN>/Conf/Int

Location of Web conferencing resources for internal users.

Device updates

http://<Internal FQDN>/DeviceUpdateFiles_Int

Location of UC device update files for internal UC devices.


http://<Internal FQDN>/etc/place/null

Location of meeting content location for internal users.

Group Expansion and Address Book Web Query service

http://<Internal FQDN>/GroupExpansion/int/service.asmx

Location of the Web service that enables group expansion for internal users. Also, the location of the Address Book Web Query service that provides global address list information to internal Communicator Mobile for Windows Mobile clients.

Phone Conferencing

http://<Internal FQDN>/PhoneConferencing/Int

Location of phone conferencing data for internal users.

Device updates

http://<Internal FQDN>/RequestHandler

Location of the Device Update Service Request Handler that enables internal UC devices to upload logs and check for updates.

Response Group Service

http://<Internal FQDN>/RgsConfig, http://<Internal FQDN>/RgsClients

Location of Response Group Service configuration tool and agent console.

For Enterprise pools in a consolidated configuration, you must deploy IIS before you can add servers to the pool.
Security Note:
You must use the IIS administrative snap-in to assign the certificate used by the Web Component Server.