Running Terminal Services on a Domain Controller is *not* a
recommended setup, for a number of reasons:
* security reasons: remember that a Terminal Server is just a
multi-user workstation. So your users will do all of their work on
the Terminal Server (= your DC), including surfing the web, trying
to install and play games, etc). Would you like them to do that on
the console of your DC?
* performance: when you install Terminal Services, the server is
tuned differently, to accomodate multiple user sessions. 60 user
sessions on a single TS can already be too much (depending on the
kind of applications they are going to use). Combining this with DC
tasks will lead to performance problems.
* configuration: running TS on a DC will diminish your
possibilities to secure the user sessions and configure the server
with TS-specific Group Policies
Do yourself a favour and do the following:
* buy a book about Terminal Services, or download and read the
White Papers that you can find on Microsofts site:
Windows Server 2003 Terminal Services Technology Center
http://support.microsoft.com/default.aspx?scid=fh;EN-
US;winsvr2003term
* then create a test Terminal Server (doesn't have to be very
powerful) and install it as a member server in your domain.
* test, test, and test again. Terminal Services can be a very
powerful way to make applications available to your clients, but
there are a number of pitfalls. Especially test all of your
applications (do they support multi-user functionality? Can they
run with normal user priviledges?), printing (are there native
drivers for your printers?) and how to configure and manage user
profiles.
