Server Platform Requirements
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.
Hardware for Standard Edition and Enterprise Edition Servers
Hardware requirements vary according to server role, configuration, and storage requirements. This topic summarizes the requirements for the following server configurations. Server roles not listed in this section are addressed in subsequent sections for the following server configurations.
Standard Edition Server configured as one of the following:
Front End Server, Web Conferencing Server, and A/V Conferencing Server
Director
Web Conferencing Edge Server or Access Edge Server
Enterprise Edition Server configured as one of the following:
Consolidated Enterprise Edition Server (Front-End Server, Web Conferencing Server, A/V Conferencing Server, and IIS collocated on server)
Front End Server in expanded configuration (conferencing servers and IIS installed on separate computers)
Web Conferencing Server in the expanded configuration
IIS Server in the expanded configuration
Archiving and CDR Server
CPU |
Dual processor, dual core 2.6 GHz + |
Disk |
2 x 18 GB For collocated Standard Edition Server, add: 2 x 36 GB, 15K RPM, RAID 0, for database log files 2 x 36 GB, 15K RPM, RAID 0, for database data |
Cache |
1 MB L2 per core |
Memory |
2 GB (4 GB for Standard Edition Server or Consolidated Enterprise Edition Server) |
Network |
GBit NIC |
Hardware for A/V Conferencing Servers and A/V Edge Servers
The following hardware requirements are required for A/V Conferencing Servers in an expanded pool configuration and all standalone A/V Edge Servers.
CPU |
Dual processor, dual core 3.0 GHz |
Disk |
2 x 18 GB |
Cache |
1 MB L2 per core |
Memory |
4 GB |
Network |
GBit NIC (for A/V Conferencing Server) 2 GBit NIC (for A/V Edge Server) |
Hardware for Archiving and CDR Database
For the Archiving and CDR database server, the recommended hardware is as follows if only CDRs are enabled:
CPU |
Dual processor, dual-core 2.6 GHz + |
Disk |
Drive 1 (2 x 18 GB) for OS and Page File Drive 2 (4 x 36GB, 15K RPM, RAID 0+1) for database log file Drive3 (4 x 36GB, 15K RPM, RAID 0+1) for database file |
Cache |
2 MB L2 per core |
Memory |
4 GB (CDR only) |
Network |
GBit NIC |
Additional memory and disk capacity is required if CDRs and IM archiving are enabled:
CPU |
Dual processor, dual-core 2.6 GHz + |
Disk |
Drive 1 (2 x 18 GB) for OS and Page File Drive 2 (6 x 72GB, 15K RPM, RAID 0+1) for database log file Drive3 (6 x 72GB, 15K RPM, RAID 0+1) for database file |
Cache |
2 MB L2 per core |
Memory |
16 GB (CDR and Archiving) |
Network |
GBit NIC |
Note
The disk recommendations for the Archiving Server are based upon a disk write rate of 140 writes/sec for the database file, 910 writes/sec for the log file, or the equivalent of 1430 IMs/sec. Disk reads are effectively zero through in-memory caching provided by the SQL server. Alternative disk configurations may be possible to sustain the same I/O rate and reliability. Consult your storage solution vendor for more information.
Hardware for Small to Medium Size Back-End Database for an Enterprise Pool
For an Enterprise Edition Server deployed as a small to medium size (up to 50,000 users) Back-End Database server, the recommended hardware is as follows:
CPU |
Dual processor, dual-core 2.6 GHz + |
Disk |
Drive 1 (2 x 18 GB) for OS and Page File Drive 2 (36GB, 15K RPM) for database log file Drive 3 (36GB, 15K RPM) for database log file Drive 4 (8 x 36GB, 15K RPM, RAID 0+1) for database files |
Cache |
2 MB L2 per core |
Memory |
8 GB |
Network |
GBit NIC |
Hardware for Large Back-End Database for an Enterprise Pool
For an Enterprise Edition Server deployed as a large size (up to 125,000 users) Back-End Database, the recommended hardware is as follows:
CPU |
Quad processor, dual-core 2.6 GHz + |
Disk |
Drive 1 (2 x 18 GB) for OS and Page File Drive 2 (4 x 36GB, 15K RPM, RAID 0+1) for database log file Drive 3 (4 x 36GB, 15K RPM, RAID 0+1) for database log file Drive 4 (8 x 36GB, 15K RPM, RAID 0+1) for database files |
Cache |
2 MB L2 per core |
Memory |
16 GB |
Network |
GBit NIC |
The disk recommendations for the backend database server are based on the following I/O pattern for a 125,000 user deployment. Alternative disk configurations may provide equivalent scalability and reliability. Consult your storage hardware vendor for more information.
Table 38 Performance Counter Values
| Performance Counter | Average Value |
|---|---|
Transactions/sec (RTC) |
2700 |
Transactions/sec (rtcdyn) |
1000 |
Transactions/sec (tempdb) |
11000 |
Log Flushes/sec (RTC) |
170 |
Log Flushes/sec (rtcdyn) |
600 |
Log Flushes/sec (tempdb) |
80 |
Disk Transfers/sec (read+write) - RTC db |
50 |
Disk Transfers/sec - RTC log |
170 |
Disk Transfers/sec - rtcdyn db |
90 |
Disk Transfers/sec - rtcdyn log |
600 |
Hardware Requirements and Scaling Numbers for Mediation Server
The following table indicates minimum hardware requirements for Mediation Server based on the required transmission standard (T1 or E1) and the desired number of T1 or E1 interfaces.
Table 39 Mediation Server hardware requirements
| Hardware | T1 | E1 |
|---|---|---|
Single processor, dual core, 2 GHz, Memory: 2GB RAM 2 x 1 GBit NIC |
4 |
3 |
Single processor, dual core, 3 GHz Memory: 2GB RAM 2 x 1 GBit NIC |
5 |
4 |
Dual processor, dual core, 3 GHz Memory: 2GB RAM 2 x 1 GBit NIC |
10 |
8 |
Dual Proc/ Quad Core 2.66 GHz, Memory: 2GB RAM 2 x 1 GBit NIC |
18 |
14 |
CPU utilization is assumed to be 75 percent of the capacity, a conservative estimate that allows sufficient performance capacity for traffic and bandwidth spikes.
Operating System
The minimum and recommended operating system platform requirements for all Office Communications Server 2007 server roles are as follows:
Minimum: Microsoft Windows Server® 2003 SP1.
Recommended: Windows Server 2003 R2 with SP2.
Support for 64-bit Operating Systems
Office Communications Server 2007 supports the following tested 64-bit configurations:
The 64-bit edition of SQL Server® 2005 SP2 on the Back-End Database of an Enterprise pool or the Archiving and CDR database.
Running the 32-bit version of the Access Edge Server on 64-bit hardware with WOW (Windows on Windows) 64 mode on the 64-bit edition of Windows Server 2003 SP1 and later.
Running the 64-bit kernel driver component of the A/V Edge Server natively on 64-bit hardware plus the A/V Edge Server service component with WOW64 mode on the 64-bit edition of Windows Server 2003 SP1 and later.
Running the 32-bit version of Standard Edition server on 64-bit hardware with WOW64 mode on the 64-bit edition of Windows Server 2003 SP1 and later.
Active Directory
For all servers requiring Active Directory® Domain Services, the minimum supported configuration is the Microsoft Windows® 2000 SP4 operating system in Windows 2000 Native Mode.
SQL Server
For all servers requiring SQL Server, the minimum and recommended versions are as follows:
Minimum: SQL Server 2000 SP4 or SQL Server 2005, SP1 (32-bit or 64-bit versions of SQL Server SP1 or later are supported)
Recommended: SQL Server 2005, SP2
IIS
For all servers running IIS, the required version is 6.0.
.NET Framework
Office Communications Server 2007 requires .NET framework 2.0.
See the Release Notes for additional recommended updates to the .NET Framework.
Supported Clients
The supported clients for Office Communications Server 2007 are as follows:
Required: A version of Microsoft Office Communicator
Minimum: Office Communicator 2005 for IM and legacy presence.
Recommended: Office Communicator 2007 for IM, group IM, multimode conferencing, and enhanced presence.
Required: Microsoft Office Live Meeting 2007 client for meetings.
Required: the Conferencing Add-In for Microsoft Office Outlook for scheduling meetings. The add-in is compatible with Microsoft Office Outlook 2002, 2003, and 2007
Optional: Communicator Web Access for Office Communications Server 2007 for IM and enhanced presence.
Warning
If you deploy Office Communications Server and Communicator 2007, and configure users for enhanced presence, when a user logs into Office Communications Server using Communicator 2007, this account can no longer use previous versions of Communicator. The user can also not log on to Communicator Web Access (2005 release) or Communicator Mobile (2005 release). Additionally, Communicator 2007 clients cannot log on to Live Communications Server 2005. Verify that any user whose client is upgraded to Communicator 2007 is hosted on an Office Communications Server.