I agree with oDdA - don't run Terminal Services on a SBS for end-users, just for remote admin purposes. These articles mention why not:
http://www.microsoft.com/s
https://www.microsoft.com/
Using Terminal Services for Remote Administration is fine:
http://www.microsoft.com/t
Some more useful reading:
http://www.microsoft.com/t
I love SBS for small businesses - a great solution. Useful background reading...
Small Business Server 2000 Product Overview:
http://www.microsoft.com/t
Small Business Server 2000 - Getting Started Guide
http://www.microsoft.com/t
Small Business Server 2000 Best Practices
http://www.microsoft.com/t
Have fun with SBS!
Main Topics
Browse All Topics





by: oBdAPosted on 2006-07-28 at 06:14:56ID: 17200870
Don't do it. To start with, for security reasons, it's never a good idea to let users logon to a terminal server; consequently, terminal services in application mode are now disabled in SBS 2003. It's not really recommended either to install application software on a domain controller; the DC is about the most important machine in your network, and you don't want to lose it to a botched software installation. Last but not least, installing Outlook on an Exchange server isn't supported anyway: om/?kbid=2 66418
Microsoft does not support installing Exchange Server components and Outlook on the same computer
http://support.microsoft.c
Use a dedicated terminal server; if the budget is small, use desktop hardware for the beginning, but don't misuse the DC as a user workstation.