In order to install the front end
server, we need to have following two components
installed on the server:
Microsoft Windows Server 2003 SP1 or SP2
(Enterprise, Standard or Datacenter edition)
IIS 6.0
Microsoft Visual C++ 2005
SP1 (OCS Setup will install it)
.Net framework 2.0 (OCS Setup will install it)
PC with
2.4 gigahertz (GHz) or faster dual processor
3 × 15 GB
disk array (One disk for the operating system, page
file, and application software, one disk for the SQL
database, and one disk for SQL transactions
2 SCSI
channels (split backplane)
1 MB
cache
2 GB of
RAM
1 gigabit
per second (GB/s) network adapter
PC with
2.8 GHz or faster quad processor
1 × 15 GB
for operating system, page file, and application
software, in addition to a storage area network
(SAN), or a 5 x 15 GB disk array
2 SCSI
channels (split backplane)
2 MB
cache
4 GB of
RAM
1 GB/s
network adapter
Fiber
channel host bus adapter (HBA) for SAN connectivity
Incoming Ports:
TCP
port 80 (HTTP) or
TCP
port 443 (HTTPS), depending on how the virtual
server (Web access server) is configured
Dynamic
port for incoming traffic from Office Communications
Server 2007 (Communicator Web Access listens on a
random port)
Outgoing Ports:
TCP
port 3268 (LDAP) on the global catalog server
TCP
port 389 (LDAP) on the domain controller
TCP
port 5061 (MTLS) on the Office Communications Server
2007 server or pool
Note: Never Install the CWA service
on the Front End Server. Microsoft doesn't support
this configuration.
Communicator Web Access deployed
outside the internal network, including the perimeter
network, is not supported. to provide CWA feature to the
external users, configure reverse proxy and publish
the internal CWA link to the external registered
domain..
