Re: Terminal Service License Server in sbs 2003

Correct. You can also get free TS CALs for 2003 for every XP Pro for which
you had a license prior to April 24, 2003. See
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/tscaltransfaq.mspx



Gregg Hill


"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:O$ZYHGoJHHA.1912@xxxxxxxxxxxxxxxxxxxxxxx
I think I understand it now. If my clients are XP pro or w2k, then they can
connect to
a Terminal Server running windows 2000 without have to have purchase a TS
CAL. But
if these same client machines have to connect to a Terminal Server running
windows 2003, then YES
they would have to purchase a TS CAL to connect to the TS server. This TS
CAL is in addition
to the CAL that they need to access (connect) to the SBS 2003 box.

Thanks,
Thomas Kroljic

"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:%23o3iCckJHHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
Without a licensing server available, they will have 120 days before the
temp license expires, which is why your clients work...for now.

XP Home requires a TS CAL in order to connect to a 2000 TS, but 2000 Pro
and XP Pro do not. The license is not built into the client OS, either.
The 2000 TS just knows to issue one from its built-in pool of licenses. A
2003 TS requires a CAL from all OS that connect.

Gregg Hill



"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:uHPG0UhJHHA.4848@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the quick reponse.
My two terminal servers are running windows 2000 SP4.

Based on your reply, I should install the TS Licensing server. On which
machine should I install it on?
The SBS 2003 box or one of the two terminal servers?

Not sure if you can answer this, but since I do not have a TS License
Server running, how are 99% of
my users connecting to the terminal servers?

Thank you,
Thomas Kroljic

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ezUMvJhJHHA.816@xxxxxxxxxxxxxxxxxxxxxxx
You don't mention the version of Windows Server used for the TS's, 2000
Pro and XP Pro (not sure about Home, don't care enough to look) come
with a 2000 TS CAL, they do not include a 2003 TS CAL.

But yes, TS Licensing should be activated on the SBS 2003 and will
corrrectly handle licensing for both 2000/2003 TS's.

"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:OF0tfUfJHHA.1064@xxxxxxxxxxxxxxxxxxxxxxx
All,

We recently installed SBS 2003 R2 on a new computer. We also have two
other servers running in Terminal Server Application mode connected to
the SBS server. All my user are able to connect to the TS servers to
access their business applications.

I noticed that in our old environment (SBS 2000) we had a Terminal
Service License Server running on the SBS2000 box. The two terminal
server servers then would point back to the SBS2000 box to access a
Terminal Server License Server. Since we swapped out the SBS 2000 box
with a new SBS 2003 box, all user are able to connect except one. This
one user has a new machine as of two days ago (OS = XP professional,
firewall exceptions allow Remote Desktop Connections).

When the user goes to connect to one of the terminal servers, they
receive an error: "Error with License Protocol". My understanding is
that if you have the appropriate CAL for the OS (SBS 2003) and the
client is running XP professional, then you do not need to issue a TS
CAL. Is this correct? If this is correct, do I still need to install
the Terminal Service License Server? If so, can I install this on the
terminal server machines or do I need to install this on the SBS 2003
box?

Thank you,
Thomas j. Kroljic











.

Relevant Pages

  • RE: local computer client access license error
    ... the Terminal Server Licensing server only has Per User CALS. ... Windows Server 2003 does not manage User CALs. ... even though there is a User CAL in the license server database, ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Changing TS Licensing Mode
    ... 822134 - The Function of Terminal Server CALs in Windows Server ... MCSE, CCEA, Microsoft MVP - Terminal Server ... One question I do have is that on the License ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Confused about CALs
    ... You mention that the 5 CALs that come with the server do not ... Terminal Services client connection. ... License Server must be activated within 120 days of using the ...
    (microsoft.public.windows.terminal_services)