[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 207
  • Last Modified:

Windows 2003 Terminal services plan

I am planning to setup Windows 2003 server with SQL running an application which runs on the back of SQL.  The software company has advised setting up terminal services and let the ten clients connect in this way for running the sql application and probably file sharing and office.

I have little experience of Terminal services, Can anyone tell me how troublesome this type of setup is, I'm also concerned with what spec of server I would need, so any advise is appreciated.

1 Solution
Terminal Services is pretty straight forward.  The main issues people run into are not understanding the application setup under SQL and mistakes on security.

Application Setup for the application itself should be done AFTER the system is set up as a Terminal Server.  The setup is done using the Add/Remove programs in the registry.  Basically windows wants to see what keys and directories are modified so that it can set appropriate security permissions.  If you are running the SQL on the same box as the TS, that should be fine to set up before the terminal services are added to the box.  Also, Terminal Services Licensing you should consider setting up a domain TS Licensing box on another server if you are using a domain.  Last, but not least, it is possible under the Administrative Tools / Terminal Services Configuration to set the properties for the connection.  You can set the timeouts for users and the like.  You can even set up that the user gets not a full desktop, but JUST your SQL application which can be good for security.  

Here is an article on setting the security on the server:

As for Spec of server, terminal server is actually pretty efficient on usage.  It largely depends on the app and how much umph it requires.  Since this is a production box I would certainly give it some sort of raid.  Usually the more ram the better as well.  For a moderate application with 10 users you could use a dual core 2.8, 2-4 gigs of ram, and 3 hdd's connected to a 3ware raid controller.  For a heavier cpu useage app you could change that to dual xeon's.

Hope that helps!
Sid_FAuthor Commented:

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now