Check out the most comprehensive, actively managed Lync blog roll in the known universe, your one-stop source for links to over 100 of the very best Lync blogs. Here you will also find weekly blog highlights and a feed for a dozen of the top blogs.
Lync Server Support Home
Top Lync Solutions RSS Feed
Microsoft Senior Support engineers walk you through real-life support cases, giving you an insider’s view into the systematic approach they use to troubleshoot Lync Server issues.
The DrRez and Lync PowerShell blogs are now retired, and we migrated their awesome content to NextHop. No worries, all your favorite articles from these two ground-breaking blogs are now available here. And DrRez on FaceBook and Twitter will continue his stellar work as the Voice for NextHop on those social media channels. Thanks for your support!
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.