Win2003 licensing - this is secret?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

May be again.

I want to set licence "per devices" by Microsoft concept and I want to see
that more then one user can login from the same station and only one CAL
licence will be allocated. CAL per devices network access, not terminal.
Server is simple, not a Domain Controller.

When I call by phone to Microsoft in Poland then I hear - this is not for
free support, because my client buy software by MOLP + Software Assurance.

When I look for info and help in Windows Server 2003, than I get only short
information or generality about licensing.

On Microsoft internet page i get information about concept, like:

Licensing Overview for Windows Server 2003
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx

Windows Server 2003 Pricing and Licensing: Frequently Asked Questions
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/priclicfaq.mspx


Windows Server 2003 Client Access Licensing Overview
http://www.microsoft.com/uk/windowsserversystem/windowsserver2003/how-to-buy/cal-overview.mspx

In this information I read, that Terminal Server Licencing Management (TSLM)
is not to report access network CAL and only to Terminal Session access or
Internet access.
I know, I see this earlier in another system, that activated Terminal Server
Licencing Management (TSLM) in Terminal Server on application mode correct
register and report devices (stations). But from another information like
looks that I can't use this utils to manage licence when server is only
access like file server, by network, not Terminal.

Than how to legal use earlier buying licences CAL devices? How to use
Licensing from Control Panel to manage devices, not users? Add group licence
in Advanced mode not resolve it or I don't know how to see this.

May by we must bury (hide) this CAL licence to wardrobe, generate system
with system licence "per server", not "per site", and forget this problem?

May be this concept will be full ready in the future? But now how to resolve
it, still in Simple Server (not Domain Controller) and not activating
Terminal Services in Application mode?

Artur Zgadzaj
artur.zgadzaj@xxxxx


.

Relevant Pages

  • Re: Win2003 licensing - this is secret?
    ... Microsoft Certified Professional ... Microsoft MVP [Windows] ... | licence will be allocated. ... | Server is simple, not a Domain Controller. ...
    (microsoft.public.win2000.general)
  • Re: Single Windows 2003 TS server in Windows 2000 domain.
    ... If you logon to the console of the TS, are you able to use Remote Desktop to logon to itself, or do you still get the TS Licensing error? ... You don't have TS Licensing running on any other machine except for your Windows 2003 TS Server, ... Upon starting TS Licencing I am told "No Terminal Server Licence ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Licensing over Citrix issuing problem
    ... Why would the fact that it affects both server mean that it can't be Citrix licensing? ... Im sure its the TS Licensing as we have TWO Citrix Servers and BOTH dont allow connections more than one licence? ...
    (microsoft.public.windows.terminal_services)
  • Re: Licence manager and class scheduling
    ... Yes, Galaxy is great, but not cheap I'm sure! ... class scheduler and server consolidation .. ... never take over more than x% of the cpu resources on the system. ... > coupling class based scheduling with the licence manager. ...
    (comp.os.vms)
  • Single Windows 2003 TS server in Windows 2000 domain.
    ... "Could I have your 6 digit key" ... "I've been passed to you because the licence key I have will not function ... I have a single Windows 2003 Server running purely terminal services. ... We are trying to register the 2003 CALs into the 2000 Licencing Server. ...
    (microsoft.public.windows.terminal_services)