Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Why PAY for Terminal Services ?????

Status
Not open for further replies.

roytheboy

Programmer
Aug 18, 2002
58
GB
I was just wondering because I am about to purcahse kit for a client of mine.

He wants the ability to runcertain progs email and internet etc... and custom access databases over a VPN and using broadband.

Terminal Services costs about £500.

Why should you pay for it when you can simply config your server (2003) for remote desktop connections and allow bog standard users to lon on locally using TS.

What do you get for £500.. Apart from a big headache with all the tools and licensing and then the spend :)

Cna someone please clarify.. WHAT ...if any .. are the benefits.

I dont believe you need to pay for the licensing of remote deskotp users.. so in other words its free. :)

Thanks in Advance Guys and Gals

R
 
ts is for application accessing

not just a remote dekstop
also its multiuse

rdp isnt
 
but I dont see what you cant do using RDP that you can in TS...

for normal email itnernet files / custom databases use

i know i SHOULD get TS..

but i dont see why ...

can i do the job with RDP? thansk dinopio .... it seems i can..

regards

R
 
Applications are not enabled for multi-user use when you use RDP for remote administration.

Not to mention you can only have two simultaneous connections with remote desktop on 2003.
 
ah...

ive only connected 2 ..

that explains it..

So.. for my scenario of one individual

over vpn .. with broadband ...

email / internet and custom access databases and files..

do you think RDP is enough... it appears to be..

thanks MLICH

Rgds

R
 
RDP is the protocol used by TS - remote desktop for administration is what you're talking about which yes is fine if you're OK with the 2 user maximum. Not sure where the £500 for TS figure comes from though, TS CALs are pretty cheap and full TS comes as part of the OS. The only hassle is you need to set up and manage TS licensing.
 
RDP (Remote Desktop Protocol) is used regardless of connection method. (TS or Remote Desktop for Admin).

Remote Desktop is provided server side for remote administration.
Terminal Services is for mutliple users to use. This way only the one copy of an application needs to be installed on the server, therefore lowering the cost of licencing for all of your other apps. (E.G. Sage, POS, Office etc.)

As per the other posts, Remote Desktop has a maximum connection limit of just two concurrent connections.

Steve.
 
Just because an application is running on Terminal Services, does not mean that only one license is required. In most cases, licenses are PER USER.

As far as the OP is concerned though, if only one person wants to connect, then Remote Desktop Connect is fine. I use it over a VPN to adminster our network from home, and it works a treat.
 
Do you want this one user to have full control of the server? Terminal Services and it's licenses allow you to limit what users can do. If you use the current remote administration, the user is in effect an administrator and can do anything. If this is acceptable, go for it.
 
thanks for your feedback everyone.

Looks like the client is going to go for the RDP option instead of TS as they dont want to purchase another server.

i will use 2003 SBS on one box with RDP.

The user is the MD and they cant get full control over the server as tey do not have th rights to do so. I have set that they can log on with terminal services locally but they are still a domain user.

Even if they can add access the admin tools, they get access denied when they attempt to sue them...

:)

thanks for all your feedback.
 
Hmm, I thought if you are in running Remote Desktop in Administration mode, only users within the administrators group is allowed to login... I remember if I tried to login as a regular user, I would get a message You do not have access to logon to this computer... Maybe I had forgot to add the user to the RDP group... Don't remember.
 
you can change the policy to let normal uaers login too.
 
I agree with that post ^ .. Someware in the local or domain controller security policy, you can set which user groups, or users can use the remote access service.
 
You can actually do it on the machine itself, without having to go through the local or the security policy. On the remote tab of the system properties, you can add whoever you would like to have access. I don't necessarily agree with skirting the "technicalities" of the licensing this way, but it can be done.
 
However the above ^ solution doenst normally work unless you have TS licensing is my understanding.

I have done this several times but you canot get a non-administrator person to be able to RD to the server.

It only works when that use is added ot the policy.

tfg13. Please confirm that you have succesfully done this because i have attempted to but not got it to work.

Im hoping its a yes and it will make my life easier :)

thanks everyone
 
I have done this before, and yes, it did work. I don't like doing it, but I have done it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top