The Situation

The Terminal Services in Application Mode component of Microsoft® Windows Server™ 2003 operating system can deliver the Windows desktop from a centralized server to virtually any desktop computing device. This component is not available in Windows Small Business Server 2003.

Improved security, an expressed desire of all customers, was the key reason for deactivating the ability to run Terminal Services in application server mode on a server running Windows Small Business Server 2003. Running Terminal Services on a domain controller may present a security risk to the network by creating the potential for denial of service attacks against Active Directory® directory service or other server application components. Windows Server 2003 and Windows Small Business Server 2003 are more secure by default than previous versions and this change was one of a number of enhancements to the overall security of the server and network.

Performance was another important consideration. Because Terminal Services is optimized for the desktop experience, it does not coexist well with the rest of the applications and services that Windows Small Business Server includes. Terminal Services and Windows Small Business Server contend for the same resources and can conflict with one another, degrading the performance of both.


Recommended Alternatives

In order to help you maximize the performance and security of your Small Business Server network, Microsoft recommends one of two alternatives for accessing network resources and applications remotely:

1. Add a second server to run Terminal Services in Application Mode. This approach will enable your customers to run line-of-applications installed on the server and host user applications in a more secure manner.
   
   • For more information on deploying Windows Server 2003 to run Terminal Services, please read the whitepaper available at: http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/adstrmsr.mspx.
   • For more information on deploying Windows 2000 Server to run Terminal Services, please read the whitepaper available at: http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/termserv2k.mspx.
   
   
2. Leverage Remote Web Workplace functionality in Windows Small Business Server 2003. This will provide mobile users in your organization with remote access to network resources and user desktops. There is no need to acquire an additional server.
   
   • For more information on Remote Web Workplace, please see the Feature Guide for Windows Small Business Server 2003.
   • For more information on securely implementing Remote Web Workplace, please read the whitepaper entitled Securing Your Windows Small Business Server 2003 Network.

Licensing Requirements on additional Windows-based servers installed in a Small Business Server network

Windows Small Business Server 2003 CALs also allow access to additional Windows-based servers in the domain. No additional CALs need to be acquired for the additional Windows-based servers. The exception to this licensing policy presents itself when an additional Windows-based server is used as a Terminal Server. Terminal Server CALs are required for each Terminal Server user in addition to the Windows Small Business Server CALs.

For more information on Windows Small Business Server licensing, please visit: http://www.microsoft.com/WindowsServer2003/sbs/techinfo/overview/licensingfaq.mspx.

For more information on Terminal Server licensing, see Licensing Terminal Server in Windows Server 2003.


Contact Us

If you have additional questions or feedback about deploying Terminal Services in a Small Business Server network, please do not hesitate to contact us at 1-877-568-2495 (select option "2" for the Microsoft Resource Centre) or email smallbiz@css.one.microsoft.com.