Re: New to Terminal Services

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

First a general remark: saving on licensing costs is *not* one of
the benefits of using Terminal Services. If you only look at the
immediate investments in terms of hardware and software, you miss
the point. Advantages of TS are the lower management costs, ease of
deploying software to remote workstations, etc. But saving on
licensing is *not* one of them.

That said, here is is what you need:

* 1 Windows 2003 server license (usually comes with the OS)
* 1 server CAL for every client or user (for authentication, file
and print services, etc)
* 1 Terminal Services CAL for every client or user (for running a
terminal services session.

Note that 2003 CALs and TS CALs come in 2 flavours: Per User and
Per Device. Choose what is cheapest for your organisation: if you
have more clients than users, buy Per User. If you have more users
than clients, buy Per Device.

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pricl
icfaq.mspx

Now for Office:
the rule here is very simple: you need one Office license for every
workstation that uses Office. It doesn't matter if Office is
installed locally on the workstation, or if each workstation
connects to a terminal server and runs Office inside a terminal
server session.
Details here:

Licensing Microsoft Office in a Windows Terminal Server Environment
http://www.microsoft.com/windows2000/server/howtobuy/pricing/licens
office.asp
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

Andrew Mallette <andrewm2@xxxxxxxxxxxxx> wrote on 03 jun 2005 in
microsoft.public.windows.terminal_services:

> I'm very new to terminal services and have no clue as to
> the licensing
> requirements other than i need a windows 2003 Server license,
> then Terminal services Cals for everyone i want to connect to
> this server. If i want them to access ms office on this server
> do i need one license for office for everyone that can access
> this server? or is one copy of Office sufficient? I need to
> understand just what benifit i can gather from this to justify
> the costs. Can i get a server license verses individual
> licenses? Microsoft changes this so often i am very confused..
.

Relevant Pages

  • Re: Does Terminal Server Licensing turn off Remote Desktop for Adm
    ... Why would you keep Terminal Server Licensing Service, ... There is no need whatsoever for TS Licensing in this situation. ... Remote Desktop for Administration does *not* need any TS CALs, ... a license after I have installed Terminal Services?" ...
    (microsoft.public.win2000.termserv.apps)
  • Re: No terminal service license is available.
    ... Remote Desktop for Administration. ... without the need to install a TS Licensing Server ... As soon as you install full-blown Terminal Services (in Control ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services Licensing --- An opinion
    ... we'll change the licensing as you suggested. ... > express an opinion about Terminal Services Licensing. ... A large chunk of that cost is, ... > the CALs for the Server Operating system. ...
    (microsoft.public.windows.server.general)
  • Re: Licensing - Remote Desktop for Administration
    ... So this sentence says that TS licensing is independent from OS ... It is not possible to have more than one console session (for ... If you use Terminal Services, *all* normal connections need a TS ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services or Remote Desktop?
    ... I'm wondering - how does the TS Licensing Server actually keep track of the users when using the Per User CAL's? ... Once you install Terminal Services, you leave Remote Desktop ...
    (microsoft.public.windows.terminal_services)