Thanks for staying with me on this one. The KB 239107 worked. As
soon as I pointed the TS at the LS, the user was able to log in.
Post by Vera Noest [MVP]OK, now that the TS Licensing is properly installed, it's time
to delete the locally stored license from the XP client once
more. You XP client should receive one of those built-in
"Existing... " TS CALs (assuming that it runs XP Pro).
If that doesn't help, check the EventLog on the Terminal Server
(not on the TS Licensing Server). If it records an EventID
1010, you might have to hardcode the address of the TS
Licensing Server into the registry of the Terminal Server.
239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Post by TomHTS has been installed on the SBS through Add/Remove
components. After installing it, it shows "All Servers", then
<server name>, under that it created a line with Product Name
of "Existing Windows Server 2000 - Terminal Services CAL
Token (per device)", Type of "Built-In", Total = "Unlimited",
Available = "Unlimited", and Used = "0". It still didn't
work, so I went to "Install Licenses", used the original
authorization code and agreement number and eventually
created the following line with Product Name of "Windows 2000
Server - Terminal Services CAL Token (per-device)", Type is
"Open", Total = "1", Available = "1", and Used = "0".
The user still can't log in to Terminal Services. Do I need
to tell the TS server to get the licenses from the SBS or
will it automatically seek it out?
If I go into "Licensing" on the TS server, I get an error
message that the "License Logging Service is not running on
\\<SBS server>.<domain>.local, or \\<SBS
server>.<domain>.local is not accessible.
Thanks again for your help,
Tom
Post by Vera Noest [MVP]Did you *install* the TS Licensing Services on the SBS?
I'm not sure what you are trying to do at that website. Did
you install the License Pak on the SBS = Licensing Server?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
wrote on 17 aug 2005 in
Post by TomHThanks for the quick response. When I go to the SBS and
choose Admin Tools -> TS Licensing, it says "NO TS license
server is available..." I click OK and then click Action
-> Activate Server and nothing happens. I don't see any
errors in the Event Viewer either.
Also, I plugged the client's license authorization # and
agreement # into eopen.microsoft.com and the TS Licensing
says no key required. I was expecting to have to type in
the 25 letter/number code to get TS working.
Thanks,
Tom
Post by Vera Noest [MVP]Yes, you've "blown away" your TS Licensing Server, which
was running on the old DC (that's the only server where
it can run under W2K).
You have to install the TS Licensing Service on the new
DC, your SBS2003 server. And then activate it. It will be
able to handle W2K (and 2003) TS CALs.
If you had any purchased TS CALs, you have to phone the
Clearinghouse to get them re-issued for installation on
your new LS.
The other clients can still connect, because they still
have a valid license, which they received from the
previous LS. As soon as those licenses expire (52-89 days
after issueing), also these clients will be refused.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
wrote on 12 aug 2005 in
Post by TomHWe had 2 servers - one was a W2K server domain
controller and the other had W2K server and was used
for Terminal Services in app mode. A SBS 2003 was
added, so the original DC was demoted (SBS has to be
king of the hill). After that, remote users could still
log into TS fine. I replaced one of the W2K remote
desktops with a new WXP computer and now I get the
following error on it. The other remote users are still fine.
"The remote computer disconnected the session because
of an error in the licensing protocol."
Did I blow away the TS Licensing when I demoted the
server? How come the others are still working? I've
deleted the MSLicensing key and subkeys on the XP
computer, but that didn't fix it. Which server should
be handling the TS Licensing? I didn't purchase TS
licenses for the SBS, since you can't use it for TS in
app mode.
Any suggestions are much appreciated.
Tom