Re: Terminal Server 2000 in Workgroup to 2003 Domain

Vera,

Thank you for the clarification. I admire your confidence. Unfortunately,
the windows xp pro remote client was pulling a CAL. I believe that was
because of the initial setup. The change that MS Support made eliminated
that and he successfully logged on without pulling a CAL. Another XP Pro
remote client logged on without pulling a CAL. The people in the out of
state office kept logging on without pulling CALS or Built In Licenses.
Everything was beautiful until...a remote client in England was issued a
Temporary License. He is running XP, but it may be home edition.

The MS Support person was not able to fix the problem of XP Pro clients
pulling licenses. His solution was to just avoid the issue completely with
per user mode. Now we have an existing client with a temporary license. I
am worse off then before the ms support that was paid for. This is why we
all love Microsoft so much.

Ron C.

"Vera Noest [MVP]" wrote:

Ron,
the situation is simple. There are 2 possibilities:

1) if you have only W2K Pro and XP Pro clients, then you don't need
these TS CALs at all. Money wasted, but I understand that the
License pack was bought before you took over the job.

2) if you have down-level clients, running Windows 9x, NT, linux,
Macintosh, thin clients (I still don't know if you have), then
these client need a purchased TS CAL and they will be refused a
connection when their temporary license expires. Your W2K TS can
and will not use the Per User TS CALs which you installed.

You also write:
Since TS 2000 does not recognize per user, the clients are na.

This is incorrect. The N/A status of your Per User TS CALs has
nothing to do with your W2K TS. It means that Per User licenses on
2003 are currently unmanaged. But managed or unmanaged has no
bearing on your situation, because you have no terminal server
which can use these licenses.

The connections are allowed, but not tracked.
This would only be true if you used a 2003 TS, which you don't.

So the 100$ question is: do you have down-level clients or not?
I recommend that you check the TS Licensing Manager, it's easy
enough to see if it issues temporary or permanent Per Device TS
CALs.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?cm9ud2NocmlzdGVuc2Vu?=
<ronwchristensen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 23 jun 2006
in microsoft.public.windows.terminal_services:

Vera,

I am glad you feel this way because I was skeptical and it took
a while for the ms support supervisor to talk me into it. We
are rdp'ng into the ip address of the windows 2000 server
running terminal server 2000. We do have two windows 2003
servers with built in administrative terminal server, but I
don't believe that they are grabbing the link. One of the 2003
servers has the license server activated. Since TS 2000 does
not recognize per user, the clients are na. The connections
are allowed, but not tracked. Our problem client connects fine
as well as our remote office and new test connections (XP 64).
This was suggested as a best practice for our setup of running
TS2000 in a 2003 domain.

That is pretty much all I know about it. It seems to be working
well and I feel pretty confident that we won't see any licensing
problems in the future.
Then again, maybe they are just getting temporary licenses. I
am trusting
ms support that that is not the case.

Ron C.

"Vera Noest [MVP]" wrote:

Per User???
Then I assume that you don't have any down-level clients? As I
wrote previously, a W2K Terminal Server doesn't know what a Per
User TS CAL is, and thus cannot use them.

So you will only be able to use these TS CAL when connecting to
a 2003 TS. Is that how you planned it?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?cm9ud2NocmlzdGVuc2Vu?=
<ronwchristensen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 20 jun
2006 in microsoft.public.windows.terminal_services:

Vera,

Well, we have made changes by uninstalling the license server
component in the windows 2000 server and creating a
"preferred server" key in the registry. We also reinstalled
the licenses in per user mode which should eliminate any
future problems. We have logged in remotely. It seems to be
working as expected, but we haven't logged in with the
problematic machine yet (out of town). MS support thinks
there may have been a conflict with the 2003 machines running
TS, but I think that it goes back to the original setup. We
will have to see what happens with the machine in question.

Ron C.

"Vera Noest [MVP]" wrote:

Yes, please do so, Ron, because I'm really curious.
Just to be absolutely sure: the client is running XP Pro,
right? Not XP Home Edition?

The only issue which resembled this had just the opposite
effect: XP Home and XP Embedded clients received a free TS
CAL, which they were not entitled to. This was fixed in XP
SP1. I don't think that I have ever heard of a case where an
XP Pro client takes a purchased TS CAL.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?cm9ud2NocmlzdGVuc2Vu?=
<ronwchristensen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 17 jun
2006 in microsoft.public.windows.terminal_services:

Vera,

Thanks for all your help. The License server shows two
entries.
Terminal Server 2000 built-in license CAL's Total
Unlimited,
Available Unlimited, Issued 0 and Terminal Server License
Pack Cal's Total 5, Available 4, Issued 1.

On Monday, I will do what you suggest and run the
reporting utility. After contacting MS Support I will
post the results.

Ron C.

"Vera Noest [MVP]" wrote:

So now you have only 4 purchased TS CALs available in the
Licensing Manager, is that correct? It's not just the
temporary license which is issued on first connection
that you saw being issued in the Licensing Manager?

This is really weird, and I've never heard of a similar
problem before. XP Pro should just get one of the
built-in licenses. There's no setting or anything you can
do to modify this behaviour. I would place a call to MS
Support, because this is definitively not as it should
be. I assume that there are no warnings or errors in the
EventLog on the TS?
Make sure that you run the lsview and lsreport utility
from the Resource Kit before phoning MS.

317592 - HOW TO: Use the Terminal Services Licensing
Reporter Tool (Lsreport.exe)
http://support.microsoft.com/?kbid=317592

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?cm9ud2NocmlzdGVuc2Vu?=
<ronwchristensen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 17
jun 2006 in microsoft.public.windows.terminal_services:

Well we activated the licensing server and installed
the 5 cals.
The license server shows unlimited built in licenses.
The
installed cals show 5. Our problem connection logged
on using XP Pro and took one of the 5 licenses. As I
understand this, that should not have happened because
we are running terminal server 2000 on a 2000 server.
From License Server Help under Required Licenses.
"Windows 2000 Built-in Licenses. Clients that are
running Windows 2000 Professional or Windows XP are
issued a license from the built-in pool of licenses
when connecting to a Windows 2000 terminal server.".
I was told that XP was using up licenses in the past
setup.
I am tempted to try a brand new remote log on of XP,
but I can't afford to lose any licenses until everyone
important is successfully logged on. Is there a
setting on the client side that causes this? What
should I be looking for?

Ron C.

"ronwchristensen" wrote:

Vera,

Thank you again for your quick response. I am
installing the license server this afternoon. I will
select per device. Previously, the engineering manager
provided IT support. He also insisted on windows 2000
on new computers because they were easier to maintain.
He is now retired. He has told us that only the xp
machines required a license when he installed the
license pack. I am not sure if we have macines older
than w2k doing remote access, but inventory and
purchasing, etc. is all done on a VAX. (plans to
upgrade to ERP in 2007.)

I am very much hoping to get this straightened out
this afternoon. I will let you know.

Ron C.

"Vera Noest [MVP]" wrote:

As an addition: if you do have down-level clients,
then you *must* install any TS CALs as "Per Device"
TS CALs, since your TS runs on W2K. A W2K Terminal
Server doesn't know what a Per user TS CAL is, and
thus cannot use them.

You will most likely still have to phone the
Clearinghouse to get your TS CALs reissued, because
they have already been installed before.
_____________________________________________________
___ _ Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private
email ___

"Vera Noest [MVP]"
<vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 15
jun 2006 in
microsoft.public.windows.terminal_services:

It's the OS on the *Terminal Server* which decides
what TS CAL your clients need. As long as your TS
runs on W2K, your XP Pro (and W2K Pro) clients do
not need a purchased TS CAL, they get a free TS
CAL from the TS Licensing Server. Do you have
down-level clients as well (thin clients, NT4,
linux, Macintosh, W2K Home edition, etc)? If not,
why did you ever buy any TS CALs at all?

___________________________________________________
___ ___ Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private
email ___

=?Utf-8?B?cm9ud2NocmlzdGVuc2Vu?=
<ronwchristensen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 15 jun 2006 in
microsoft.public.windows.terminal_services:

Vera,

Thanks again. We found the license information
from Nov. of 2004 and they were 2003 licenses
installed in 2000 license server. I am told that
xp machines did require a license per machine. I
understand that only xp licenses owned before
April 2003 are grandfathered in. Is there a best
way to set this 2003 license server up with
regard to device or user and w2k and xp?

"Vera Noest [MVP]" wrote:

No, you can't. There is no way to move licenses
at all. The only way to "move" them is to phone
the Clearinghouse and get them re- issued.
_________________________________________________
___ ___ __ Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup
-------------*

=?Utf-8?B?cm9ud2NocmlzdGVuc2Vu?=
<ronwchristensen@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 14 jun 2006:

Vera,

Thanks for the quick response. If I can't
find the paperwork, can I move back to the
workgroup and start license services and then
transfer the licenses to the new license
server? I haven't dealt with terminal server
licenses before.

Ron C.

"Vera Noest [MVP]" wrote:

What happened when you joined the W2K TS to
the domain is that it started looking for a
TS Licensing Server on the DC. A W2K TS
*must* connect to a TS Licensing Server
running on the DC, only exception is when the
W2K TS is a member of a workgroup or NT4
domain.

.

Relevant Pages

  • 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: Terminal Service License Server in sbs 2003
    ... You can also get free TS CALs for 2003 for every XP Pro for which ... a Terminal Server running windows 2000 without have to have purchase a TS ... temp license expires, which is why your clients work...for now. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems with the Windows 2003 License Server
    ... CALs Tokens)". ... since you have no clients who need them. ... server) is started. ... I got a temporary license on the Windows 2003 Server, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing
    ... a 2nd LS on another server, and then my primary license server ... clients, in which case a dedicated LS could be wise. ... Permanent TS CALs expire after 52-89 days, ...
    (microsoft.public.windows.terminal_services)
  • 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)