Re: Need your help

From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 12/03/04 

Date: Thu, 02 Dec 2004 23:28:58 -0800

Hendry, do you realize that by writing:

> ... usually when the 90 days term
> have been expired, we just removed the MSLicensing key in the
> Win9x's registry

you actually write that you are systematically violating the EULA
(End User License Agreement)?

Windows 2003 Terminal Servers need a 2003 TS Licensing Server. You
have to buy and install 2003 TS CALs (Per User or Per Device) on
the 2003 LS.

 --
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
 --- please respond in newsgroup, NOT by private email ---

=?Utf-8?B?SGVuZHJ5?= <Hendry@discussions.microsoft.com> wrote on
03 dec 2004 in microsoft.public.windows.terminal_services:

> Dear all,
>
> Currently I have a Terminal Service Licensing Server installed
> in Windows 2000 Server. We just new setup a Terminal Service
> Server in Windows Server 2003 1 month ago to let some of the
> client workstations to access in for the application usage
> purpose. Before that all are working fine and no problem occur
> at all, but suddently I don't know why just happen yesterday
> that if those client workstaions whoever were already log off
> from the Windows Server 2003's Terminal Service Server, they no
> longer log in again thru Terminal Service.
>
> I feel that that's because of the licensing expired in Windows
> Server 2003, is it?
>
> For those client workstations access to the Terminal Service
> Server in Windows 2000 Server, usually when the 90 days term
> have been expired, we just removed the MSLicensing key in the
> Win9x's registry then we still able to renew another 90 days
> term for the Terminal Service.
>
> But for this time Windows Server 2003 act as a Terminal Service
> Server, are there any ways to renew the licensing period in
> Win9x after expired? If no, please provide me some
> documentations for support and review. Please feedback to me as
> soon as possible.
>
> Thnks you and have a great day.
>
> Best regards,
> -Hendry Khoo-

Relevant Pages

  • Re: additional license
    ... Terminal Server licensing is *never* per concurrent usage. ... licensed limit for product Windows Server 2003 has been exceeded" ... errors related to licensing or refused connections? ...
    (microsoft.public.windows.terminal_services)
  • Re: Please Help!
    ... Windows 2000 Terminal Services Licensing FAQ ... Q. What licenses are required to run Terminal Services in Windows ... required to run applications on a Windows 2000 Server via Terminal ...
    (microsoft.public.win2000.termserv.apps)
  • Re: additional license
    ... Are you sure that you installed Terminal Services, in Add/Remove Windows ... And what *exactly* is the error message that you get when the third ... Have you checked the EventLog on the server for warnings and errors ... I checked for "licensing mode" ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing, CALs and Server 2003
    ... What is true about SBS is that it has to be the holder of all the FSMO roles, unlike a standard Windows Server farm where the roles can be distributed. ... As for the licensing questions, best to speak with a licensing specialist at MS: ...
    (microsoft.public.windows.server.sbs)
  • Re: Could Not Establish A Connection To The Remote Computer...
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... The TS Licensing Server was not activated. ... since it is listed the the TS client computer name ... and the both the Terminal Service server and the Terminal ...
    (microsoft.public.win2000.termserv.apps)
Loading