Pretty much. There are a few other issues with Terminal Services (like running a Terminal Services Licencing server, which you can do on the same box). Also, make sure your win2k3 box is not SBS (which won't do terminal service lic. server, etc.)
:) -----Original message----- From: "Thane Sherrington (S)" [EMAIL PROTECTED] Date: Wed, 07 Dec 2005 14:23:36 -0600 To: hardware@hardwaregroup.com Subject: [H] Windows 2003 CALs > Ok, I'm sure this is really stupid (or at least uneducated.) > > I have a client with Windows 2003 server OEM with 5 CALs. He wants to use > Terminal Server, and I understand from talking to MS that one needs > Terminal Server CALs on top of the Windows CALs that come with 2K3. (But > according to MS, Terminal Server is part of 2K3, so that's a bit confusing > to me.) > > From talking to MS, this is how I think things work: > > 2K3 with Windows CALs allows a user or a device to connect (since a user > must be using a device to connect to the server, I don't understand the > difference between users and devices, but anyway) and use the server as a > file server. To run applications on the server and share those, or for > remote file sharing access, one needs Terminal Server, and needs CALs for > that. Of course, one needs 1 Windows CAL for every Terminal Server CAL. > > Am I understanding this right? > > T >
