Terminal Services ( per user or per device )

TeddyTed · Post by **TeddyTed** » Tue Jun 12, 2007 1:13 am

Got a little question on using Terminal Services in a small workgroup.
Win 2K3 Server standard with 15 workstations.
I've purchased 6 TS CALS for users to connect to the server remotely and i'm getting ready to put em to work.
I'm just not sure if it makes sense to use "per user" or "per device" option.

My thought is that if I had a domain controller then it would make sense to use TS in " per user" option. But since this is a simple workgroup i'm not sure if this is still possible.
I'm assuming TS uses the windows user information to authenticate and in a workgroup users are pretty much locked into one machine.

Can anyone shed some light on this?

Thanks

TB

ErikD · Post by **ErikD** » Tue Jun 12, 2007 6:21 am

Why run a server in a workgroup? You have everything needed to setup a domain, so why not do it? Will make everything easier.

As to the licensing model, the general MS rule is if you have users with multiple devices then per user, if you have machines with multiple users then per device. Basically you choose whichever way would be cheaper for you and makes more sense in your situation. If you only have a handful of users each with one device it probably doesn't make much difference.

Post by **YeOldeStonecat** » Tue Jun 12, 2007 7:16 am

Adding that it's not good practice to run Terminal Server on a domain controller..especially if made public for remote users. So if you want to upgrade your network to active directory...it would be wise to get a second server..and use the beefier one for your TS.

twwabw · Post by **twwabw** » Tue Jun 12, 2007 7:28 am

In workgroup mode, you'll have to create and replicate each user onto the TS, which while akward, will work. Or, you could even create new unique logons, really doesn't matter. But like YOSC said, do NOT make this a DC and install TS on it!

TeddyTed · Post by **TeddyTed** » Tue Jun 12, 2007 1:02 pm

Actually, I have been thinking of using a DC because this 2k3 server is replacing another box running server 2k. So logically the older box can become the DC. That would be perfect, however, the only issue they will have to purchase another 2k3 server license and I'm not sure if the boss would want to do anymore spending at the moment.
There was a license issue with the 2k server and hence the new 2k3 server.
I'll see if i can do the DC, and if not, I’ll look into twwabw’s advice on creating unique logons.

Post by **YeOldeStonecat** » Tue Jun 12, 2007 8:16 pm

Since you're under 75 nodes...consider Microsoft Small Business Server.

You get more than just a server...you get Exchange mail, shared fax, remote access through Remote Web Workplace, etc. And...it's very aggressively priced.