Adding Terminal Service server

By bsit ·
I manage a SBS2003 system. They have been using RDP for a couple of remote connections using the built in 2 connections available. Now they need to expand. They have another server I will use and it has Server2003 and they have a 5 User Cal TS license from a previous life. I have never set one of these up. I need some tips.

The current SBS server has all the apps on it. I will install the TS licenses on this box. I will setup the Server 2003 box as a Terminal Services Server. The SBS server has two NICS so it connects to the internet and LAN.
1/ When I setup the TS server do I just put it on the LAN and the SBS server will direct remote connections to the TS box?
I plan to put Office on the TS box. The only other app required will remain on the SBS server but it can easily be setup for the TS server so I know about that part. Currently the RDP printing works fine on the SBS server.
2/ When I set up the TS server do I need to put the remote printer drivers on the TS server?
As you can see I don't know much and the documents I have read don't explain much about this. There is no info about the physical setup for LAN and Internet connections and other stuff, like about which servers connect to what etc.
Any extra practical info or references to practical setup manuals/documents etc would be greatly appreciated I need to try this this coming weekend, I'll up late reading I think. Anything on security setups for both servers too.

All help appreciated greatly.

thanks in advance

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Lets hope for first thumbs up

by Iankf In reply to Adding Terminal Service s ...

When you set up terminal server you will need to redirect the remote desktop connection on each computer to connect to that computer name or IP address.

Printing, as you know you need to allow local resources such as the printer to connect to the terminal server, you also need to install the drivers for any printers that you plan on using.

The way I do this is installing a fake printer with any IP address and then installing each printer driver I might use. You also need to check if the printers work with windows 2003 server.

Before installing any software you must install the terminal server and the license server, the you HAVE to use add/remove programs to install your applications on top. (this is just a extra step you may just run setup.exe.)

1) install base system with plenty of space for application and user profiles
2) Install terminal services and terminal services licencing from add/remove components.
3) Install any programs through add/remove
4) Install printers drivers
5) Lock down the system using group policy when everything is working

Collapse -

thanks but...

by bsit In reply to Lets hope for first thumb ...

Thanks for your help. I have most of that concept. What I am hoping to find out and what is never explained is the physical stuff. Installing the apps using the Add/Remove is fine although you also say just using setup.exe is OK too, is that true? At this stage I am only installing Office 2007. Only about 10 users profiles for now although no more than 5 log in at any given time. There will be a 3rd party app that will only need a shorcut with specific .ini files in each user, the app stays on the main server.

What I want to know is, does the TS server simply go on the LAN? Or does the Interent NIC have to move to the TS server or can it stay where it is on the main server? Not even MS have covered such basics as this.

When some one logs in by TS (they are all remote not local - no thin clients) they log in to the main server over the Internet using RDP. The main server is the License server for TS. I assume the main server redirects the connections to the TS server. Users log in using the fixed IP of the company obviously. If the Internet NIC must be on the TS server how do local users on the main server get to the internet and how does Exchange (on the main server too) get affected by all this?

I'm setting this up tomorow Saturday so any info before then will be greatly appreciated. Thanks.

Collapse -


by Iankf In reply to thanks but...

If it is only your internal users then put your LAN cable in and plug the other end into your switch/hub.

You should be using a ISP supplied router with the internet cable attached there and cable going from the router to your switch.

If however you are using your main server with routing and remote access and that server is your router then on the Terminal server put the static entries of the IP in and the default gateway as the main server IP.

Some applications are terminal services aware. But I would use add/remove either way.

Collapse -

Still unsure

by bsit In reply to LAN

Thanks again. Yes all the TS users are/will be offsite, not local. Current setup is the main server has been set as RRA and 2 users can login for remote use. This server has 2 NICs, 1 for the local LAN and LAN switches, 1 for Internet via an ADSL modem - fixed IP to the Internet.

The new setup will be a TS Server and the Main server which is also the License Server for TS. The TS server will have Office and access to the Main server 3rd party app. I wanted to know should the Internet connection remain on the Main server as is? So I am guessing that RDP requests from remote users will come in through the Main server and be redirected to the TS server, is that so? There is no clear info about any of this physical connections between servers and Internet and why/how.

Also there are references to setting up users on the WS2003 TS server but since it is not DNS and DHCP no AD is setup and no obvious user setup process is there. The remote users are some of the same users on the Main server. What can be done about this? How can users be setup on the TS server? I need specific info for this setup.

Much appreciated.

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums