Windows Forum

Ask something
Discussion Locked

Terminal Services

0 helpful
7 replies

by johnmiles_98

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

First let me say, This question has nothing to do with Windows XP Remote Assistance. Thanks

I currently use Terminal Services to run remote Windows 2000 Server sessions for administration purposes.

A co-worker has recently told me that youcould use a version of terminal server to run remote Windows 2000 Professional sessions (accessing Workstation's for end users). We have been using VNC for this, but at times this can be choppy and slow and requires alot of coordination with users. Thus this tool falls into the hit and miss category. Has anyone else heard of using Terminal Services to access Remote Windows 2000 Professional Machines? And if so, where do I get some data for this?

7 replies

by johnmiles_98

Thanks. I have had all the Windows XP solution that I can handle for one lifetime (most people say what you did), however this is a Windows 2000 Professional specific answer I am looking for.. Our originization has decided not to move forward to XP hoping for a better showing from Microsoft in the .net release of Windows. Thanks for your efforts

by samuelbrooks

RPC - Remote control is only with Windows XP. Windows 2000 Pro does not have any method to do what you are asking. The option in a Windows 2000 environment is to setup a single Windows 2000 SERVER and enable Terminal Services in application mode.Then setup your users for roaming profiles and they will be able to log into the Terminal Server and get their standard desktop.

Setting up Terminal Services in application mode requires a little bit of planning but if you purchase the following book. Windows NT Thin Client Solutions ISBN 1-57870-065-5 it will get you started and explain what to look out for.

It is very fast and works over dial-up well.

The only catch is that if your user will connect to the system from home computerswith anything that is not Windows 2000 Pro or Windows XP Pro they will need a terminal services cal per pc connecting. This will run you about $70.00 per pc.

The advantage of this over pcAnywhere is that you only poke one hole in your firewall for the Terminal Server and only for the ports needed for RPD where using VNC you have to setup each user with a seperate firewall path or have each user with a VPN.

Terminal Server Sizing.
I also use Citrix but this would not be required if you are not running very many users.
I have four server that are Dual PIII 500Mhz, with 512MB Ram and a single 9GB SCSI HD. Remember the servers only do the processing all your data should be on your main network servers and if you are using roaming profiles then these settings will also be pulled from your network servers. The only thing installed on the Terminal Server would be the applications that your users need to run.

My servers have a load of 10-15 users per server all day long and average a server utilization of 15% so I have alot of room for burst of activity.

The other quick but expense route is gotomypc.com.

Good Luck.

by jeff

The only thing I can think of is the remote desktop sharing capability built into Netmeeting. It's free and it's in all versions of windows back to windows 95. This can run all the time in the background.

This discussion is closed to new replies.