DrRez: Microsoft Lync Server Technical Reference Hub

Brought to you by the Microsoft Lync Server Resource Kit team

DrRez: Microsoft Lync Server Technical Reference Hub

  • Using Asterisk to Supply Standardized On-Hold Music for Office Communications Server 2007 R2

    This article describes how to use Asterisk to supply standardized, company-wide, on-hold music for all your Microsoft Office Communications Server 2007 R2 end-points (softphone or Voice over Internet Protocol (VoIP) phones). Configuring each end-point...
  • Limit Media Ports in Office Communications Server 2007 R2 Devices

    Administration of Office Communications Server 2007 R2 often involves configuration of clients, such as enabling voice and conferencing features and sending additional settings to clients. Frequently, the ability to limit media ports used by Communications...
  • Resolved—Known Issue with Response Group Service CDR Queries

    Microsoft Office Communications Server 2007 R2 introduced the new Response Group Service and as a result added a few new queries to the Call Detail Record (CDR) reporting tool that is included with the Microsoft Office Communications Server 2007 R2 Resource...
  • Split-Brain Domain Name Services for Communications Server

    There is much to think about in the design of your network perimeter for Office Communications Server-several services are offered in the perimeter network through the Edge Servers. The primary goal when implementing a split-brain DNS solution is to provide...
  • Upgrading Tanjay in Communications Server 2007 R2

    This article provides instructions for upgrading Office Communicator Phone Edition devices from build 199 to 522 and then to 6907 by using the Office Communications Server 2007 R2 Device Update Service. There is also a brief description of the naming...
  • Specifying the SQL Instance when Creating an Enterprise Pool

    When running Office Communications Server Setup to create an Enterprise pool, the Create Enterprise Pool Wizard requires a SQL Server instance as shown in Figure 1. This is a database instance that the Enterprise pool uses as its back-end server. After the SQL Server instance field, the wizard provides an example that can be confusing. The reason is that unless you plan to reuse an existing instance, most installations are new installations. The language in the wizard might make you think that you need to specify a database instance name that is to be created or that you have to create the instance yourself.