I don’t like posting mails to my blog, but the following extract from a “Good news” e-mail which I picked up earlier today, was explicitly marked as sharable and didn’t need rephrasing.
The RTC Product Group has now completed testing of Live Communications Server 2005 SP1 with SQL Server 2005 SP1, and is pleased to announce that LCS 2005 SP1 Enterprise Edition can now be deployed using either SQL 2000 or SQL 2005 SP1. We’re also able at this time to communicate support for LCS 2005 SP1 (both Standard and Enterprise Editions) on Windows Server 2003 R2.This means that customers who have standardized on SQL 2005, or beginning to deploy Windows Server 2003 R2, can now more readily deploy Live Communications Server.
LCS 2005 system requirements and supported environments will be updated to reflect these changes.
A Knowledge Base article about these changes will be posted.
Knowledge Base article #911996 details the pre-requisite steps required prior to deploying SQL 2005 SP1.
CSS/PSS/Premier will be notified of the changes.
Supported Scenarios: LCS 2005 Enterprise Edition and LCS 2005 SP1 Enterprise Edition
Database requirements: Installation of Live Communications Server 2005 Enterprise Edition requires a separate server running SQL Server 2000 Standard Edition, SQL Server 2000 Enterprise Edition with service pack 3a, SQL Server 2005 SP1 Standard Edition, or SQL Server 2005 SP1 Enterprise Edition.
Archiving service requires: SQL Server 2000 Standard Edition, SQL Server 2000 Enterprise Edition, SQL Server 2005 SP1 Standard Edition, or SQL Server 2005 SP1 Enterprise Edition.
No changes have been made to the supported scenarios for LCS Standard Edition with respect to SQL 2005.
Product groups don’t like making these changes because they have to test their products on all the supported permutations of operating system/database and so on. My experience with the RTC group means I’m not surprised that they responded to customer demand and made this change, even though I’m sure they would have preferred not to.
This post originally appeared on my technet blog.