Article ID: 327270 - View products that this article applies to.
This article was previously published under Q327270
Microsoft SQL Server does not support the installation or use of SQL Server Failover Clustering on Microsoft Windows Server 2003-based server clusters if the server clusters have Terminal Server installed. This configuration was known as Application Mode in Microsoft Windows 2000. However, SQL Server 2000 instance installation is supported as a stand-alone instance for Windows Server 2003 Terminal Services Mode (Application Mode).
For Windows Server 2003 or Windows Server 2008 Terminal Server Remote Desktop for Administration Mode, SQL Server 2000 installation is fully supported as both a clustered instance and a stand-alone instance.
Note Cluster instances for the versions of SQL Server that are listed in the "Applies To" section are currently not supported on Windows Server 2003 or Windows Server 2008 Terminal Server Server Cluster installations.
Terminal Server provides remote computers with access to Windows-based programs running on the following systems:
Remote Desktop for Administration is another part of the Terminal Services technology that is offered in Windows Server 2003 or in Windows Server 2008. You can enable remote administration of servers with Remote Desktop for Administration on any computer that is running the Windows Server 2003 or Windows Server 2008 family of products, even if Terminal Server is not installed.
Note In Microsoft Windows 2000 Server, the Terminal Server component is named Terminal Services in Application Server mode. In Microsoft Windows 2000 Server, the Remote Desktop for Administration component is named Terminal Services in Remote Administration mode.
To determine whether the Terminal Server service is running on the computer, follow these steps:
(http://support.microsoft.com/kb/313037/ )Upgrading SQL Server clusters to Windows Server 2003
Example log behavior if Terminal Server is installedIf Windows Server 2003 Terminal Server is installed and you try to install SQL Server, no log files exist in the %windir% folder. However, the log files are stored in the %userprofile%\Windows folder. When you check the log files and you compare the log to the system variables, you see results that are similar to the following in the Sqlstp.log file:
Note This example does not apply to servers that are running Windows 2003 Service Pack 1 (SP1) or a later version. We recommend that you check manually for a Windows directory in the %USERPROFILE% directory.
19:41:44 Begin Action: SetupInstall 19:41:44 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ... 19:41:44 CommonFilesDir=C:\Program Files\Common Files 19:41:44 Windows Directory=C:\Documents and Settings\<user_name>\WINDOWS\ 19:41:44 Program Files=C:\Program Files\ 19:41:44 TEMPDIR=C:\DOCUME~1\<user_nam~1>\LOCALS~1\Temp\1\ From system variables - USERPROFILE=C:\Documents and Settings\<user_name> windir=C:\WINDOWS
For more information about Terminal Server, visit the following Microsoft Web sites:
Terminal Services running on Microsoft Windows Server 2003
http://technet.microsoft.com/en-us/library/cc737856(WS.10).aspxRemote Desktop Services (Terminal Services) running on Microsoft Windows Server 2008
Article ID: 327270 - Last Review: August 13, 2010 - Revision: 15.0
Contact us for more help
Connect with Answer Desk for expert help.