PC Review
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
TS licenses will not work for all servers?
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
TS licenses will not work for all servers?
![]() |
TS licenses will not work for all servers? |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
Hello, I have this very frustrating problem with the purchase of extra
terminal services CALs: I got a small network on a workgroup, one of the servers is a dedicated terminal license server and the activation and assignment of extra CALs worked fine. The way I understood it is that every TS-server will automatically scan its surroundings for license servers and one of the servers (a W2k3) works just like that, it automatically accepts more incoming connections. However, the rest of the servers (mainly 2k) just will not accept more than the two standard connections and setting the licens server manually according to http://support.microsoft.com/kb/239107/ does not seem to do the trick. This is very frustrating so I would appreciate all suggestions. Is there a way to monitor the actual license server discovery process of the servers? |
|
|
|
#2 |
|
Guest
Posts: n/a
|
Are you sure that these W2K Terminal Server are running Terminal
Services in Application Server mode, not in Remote Administration mode? Sounds like they are running in Remote Administration mode only. If they really are running in Application Server mode, check the following: Which EventID do you see on the W2K TS? If it's a EventID 1010 (cannot locate Licensing Server), double- check the registry entry that you made and run lsreport and lsview from the Resource Kit to see which Licensing servers are detected on your network. If you see an EventID 1004 (cannot issue license), then check the type of licenses on your Licensing Server. It sounds like the LS is running on a 2003 server, is that correct? Which type of TS CALs did you install on it? Note that a W2K TS can *not* use 2003 Per User TS CALs, only Per Device TS CALs. Which OS are your clients running? _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------* "Anders Biro" <anders.biro@remove.ascade.se> wrote on 19 dec 2005: > Hello, I have this very frustrating problem with the purchase of > extra terminal services CALs: > I got a small network on a workgroup, one of the servers is a > dedicated terminal license server and the activation and > assignment of extra CALs worked fine. > The way I understood it is that every TS-server will > automatically scan its surroundings for license servers and one > of the servers (a W2k3) works just like that, it automatically > accepts more incoming connections. > > However, the rest of the servers (mainly 2k) just will not > accept more than the two standard connections and setting the > licens server manually according to > http://support.microsoft.com/kb/239107/ does not seem to do the > trick. > > This is very frustrating so I would appreciate all suggestions. > Is there a way to monitor the actual license server discovery > process of the servers? |
|
|
|
#3 |
|
Guest
Posts: n/a
|
As a matter of fact I was not the one installing the servers so is there an
easy check to see whether they run in Remote Admin or Application server mode? /Regards Anders "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message news:Xns9731A9117610Fveranoesthemutforsse@207.46.248.16... > Are you sure that these W2K Terminal Server are running Terminal > Services in Application Server mode, not in Remote Administration > mode? > Sounds like they are running in Remote Administration mode only. > > If they really are running in Application Server mode, check the > following: > > Which EventID do you see on the W2K TS? > > If it's a EventID 1010 (cannot locate Licensing Server), double- > check the registry entry that you made and run lsreport and lsview > from the Resource Kit to see which Licensing servers are detected > on your network. > > If you see an EventID 1004 (cannot issue license), then check the > type of licenses on your Licensing Server. > > It sounds like the LS is running on a 2003 server, is that > correct? Which type of TS CALs did you install on it? Note that a > W2K TS can *not* use 2003 Per User TS CALs, only Per Device TS > CALs. > > Which OS are your clients running? > > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > *----------- Please reply in newsgroup -------------* > > "Anders Biro" <anders.biro@remove.ascade.se> wrote on 19 dec 2005: > >> Hello, I have this very frustrating problem with the purchase of >> extra terminal services CALs: >> I got a small network on a workgroup, one of the servers is a >> dedicated terminal license server and the activation and >> assignment of extra CALs worked fine. >> The way I understood it is that every TS-server will >> automatically scan its surroundings for license servers and one >> of the servers (a W2k3) works just like that, it automatically >> accepts more incoming connections. >> >> However, the rest of the servers (mainly 2k) just will not >> accept more than the two standard connections and setting the >> licens server manually according to >> http://support.microsoft.com/kb/239107/ does not seem to do the >> trick. >> >> This is very frustrating so I would appreciate all suggestions. >> Is there a way to monitor the actual license server discovery >> process of the servers? |
|
|
|
#4 |
|
Guest
Posts: n/a
|
Check under Start - Programs - Administrative Tools - Terminal
Services Configuration - Server settings - Terminal Server mode. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------* "Anders Biro" <anders.biro@remove.ascade.se> wrote on 20 dec 2005: > As a matter of fact I was not the one installing the servers so > is there an easy check to see whether they run in Remote Admin > or Application server mode? > /Regards > Anders > > "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote > in message > news:Xns9731A9117610Fveranoesthemutforsse@207.46.248.16... >> Are you sure that these W2K Terminal Server are running >> Terminal Services in Application Server mode, not in Remote >> Administration mode? >> Sounds like they are running in Remote Administration mode >> only. >> >> If they really are running in Application Server mode, check >> the following: >> >> Which EventID do you see on the W2K TS? >> >> If it's a EventID 1010 (cannot locate Licensing Server), >> double- check the registry entry that you made and run lsreport >> and lsview from the Resource Kit to see which Licensing servers >> are detected on your network. >> >> If you see an EventID 1004 (cannot issue license), then check >> the type of licenses on your Licensing Server. >> >> It sounds like the LS is running on a 2003 server, is that >> correct? Which type of TS CALs did you install on it? Note that >> a W2K TS can *not* use 2003 Per User TS CALs, only Per Device >> TS CALs. >> >> Which OS are your clients running? >> >> _________________________________________________________ >> Vera Noest >> MCSE, CCEA, Microsoft MVP - Terminal Server >> TS troubleshooting: http://ts.veranoest.net >> *----------- Please reply in newsgroup -------------* >> >> "Anders Biro" <anders.biro@remove.ascade.se> wrote on 19 dec >> 2005: >> >>> Hello, I have this very frustrating problem with the purchase >>> of extra terminal services CALs: >>> I got a small network on a workgroup, one of the servers is a >>> dedicated terminal license server and the activation and >>> assignment of extra CALs worked fine. >>> The way I understood it is that every TS-server will >>> automatically scan its surroundings for license servers and >>> one of the servers (a W2k3) works just like that, it >>> automatically accepts more incoming connections. >>> >>> However, the rest of the servers (mainly 2k) just will not >>> accept more than the two standard connections and setting the >>> licens server manually according to >>> http://support.microsoft.com/kb/239107/ does not seem to do >>> the trick. >>> >>> This is very frustrating so I would appreciate all >>> suggestions. Is there a way to monitor the actual license >>> server discovery process of the servers? |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

