Lync Server Support Home
Top Lync Solutions RSS Feed
Get your Lync Server 2010 Resource Kit, your one-stop-shop, under-the-hood, technical reference for Lync Server 2010. With 19 chapters, you will find the in-depth, nitty-gritty information you need to deploy, configure, support, and troubleshoot Lync Server 2010. For a detailed summary of each chapter, see the Lync Server 2010 Resource Kit Overview. To download your FREE chapters, see the Microsoft Lync Server 2010 Resource Kit.
These short videos focus on specific tasks and show you how to accomplish them for Microsoft Lync Server 2010.
This article describes how to correctly configure the Microsoft Office Communications Server Edge Server role on the Microsoft Windows Server 2008 platform when three or more network interfaces are used. In a basic Edge Server deployment, only two network interfaces are used (one is internal-facing and the other is external-facing). But when multiple interfaces are dedicated for external-facing communications, changes in the networking behavior of Windows Server 2008 R2 and Windows Server 2008 can limit proper traffic routing, preventing Web and A/V Conferencing features from working for external Microsoft Office Communicator clients.
Due to recent discoveries in the July 2010 Cumulative Update for Office Communications Server 2007 R2, it is necessary to remove this update from the download site until it can be patched. The primary concern is an issue with the Response Group Service. When the cumulative update is applied, changes in agents and agent groups are not applied until after the Response Group Service is restarted. This, of course, is not acceptable in the quality of our products.
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.