What do I need to do to install Terminal Services on a server that is running SQL 2000 and another application?

Terminal Services can be installed via Control Panel > Add/Remove Programs > Add/Remove Windows Components.

But I HIGHLY recommend you don't do this...  In the same manner that you wouldn't have SQL Server running on a workstation, a Terminal Server is a special "workstation" (that allows concurrency of multiple workstations on a single box).  There is performance, security, best practices, support, etc., concerns trying to mix these together.  It really should be a separate box with enough memory to handle the Terminal Services concurrent connections.

Now, if using Windows 2003, you just want to be able to RDP in as administrator, that is a different story (Terminal Services is not needed).

We need to have this Server running Terminal Services because the application is on the Server and we have the need to only run the application from that server instead of installing on all workstations.  We have Terminal Services running on other servers, but this is the first one that is already running programs and I just need to know if I will have to re-install SQL and the third party application to get them to work after installing Terminal Services?

Jo Ann

No re-installs...

Installing terminal services does not wipe the server.

You do have two 'special' remote desktop connections already - but that might not be enough users...

I have about 25-30 users that will be running the third party application from this server and that is why we are looking at using Terminal Services so we don't have to go to each desktop all the time.  I just wanted to make sure I didn't have to re-install the application, because I thought I it said that I would need to reinstall any applications when I started to install Terminal Services.

Jo Ann

Ouch, 25-30, thats quite a hit in terms of memory and resources. SQL is a hungry beast and doesn't like to share it's toys... Haven't got another box somewhere - anywhere - or a couple of grand for a new little blade or something ?

No, unfortunately no additional box or money.  

So, is it not a good idea to run SQL on a terminal services server?  

Jo Ann

Another example (and the previous ones mentioned are well said by everyone): local users will have an easier time impacting applications on the same box than if they were one separate boxes.  This is because of memory, their access (such as the possible option of shutting down the server), etc.

If an appropriate amount of effort is taken, it can be done successfully.  Just understand the risks/rewards.

Thanks for all your help.  I think I will try to avoid using terminal services on this server.  I appreciate your comments.