Re: Licencing on replacement Hardware question

As far as I can remember, the TS Licensing Manager in
Administrative tools does *not* mean that you installed TS
Licensing. The tool is always there, because you can use it to
connect to a TS Licensing Service on a remote computer.

So you'll simply have to install the TS Licensing Service, in
Add/Remove programs - Add Windows components.

_________________________________________________________
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?R1JX?= <GRW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 04 jun
2007 in microsoft.public.windows.terminal_services:

New box was a fresh install. TS licensing server was already
installed/running on it (or at least the icon was in admin
tools). When I click on it, it opens but I am unable to do
anything (connect to a server, activate, etc). I am thinking I
might try to reinstall WTS on the old W2K box then reinstall TS
Licencing on the nex box (SBS). Any other ideas? Thanks much for
the help and the time.


"Vera Noest [MVP]" wrote:

How did you recreate the new box? Fresh install? If so, did you
install the Terminal Services Licensing Server? Did that give
any errors?
If you used backups to recreate your environment:
is the TSLS service running? Any errors in the EventLog?

_________________________________________________________
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?R1JX?= <GRW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 04
jun 2007 in microsoft.public.windows.terminal_services:

Pulling my hair out on this one, any help appreciated.

Replaced a SBS box with new hardware, recreated the domain
environment successfully. Everything works great except WTS
that is running on a W2K server on the same domain. WTS
licencing server was installed on the old SBS box so I am
trying to install it on the new hardware and hopefully get
remote access back up. However....when I get into Terminal
Server licencing app I dont see any servers I can add - I
cant browse to or type in by name. Not sure how to proceed if
I cant get the WTS licencing program to see any servers. Once
I can connect to a server I have plenty of documentation on
how to configure. ANY advice appreciated. Thank you
.

Relevant Pages

  • Re: SBS on two systems
    ... The following is a direct copy and paste from the Microsoft Licensing Product Use Rights Documents found at: ... Running Instances of the Server Software. ... the second SBS to boot will see the first (in my ... The same SBS install, ...
    (microsoft.public.windows.server.sbs)
  • Re: XP Home User Temp Licence from W2K TS Box
    ... you have to install the TS Licensing Service on the 2003 Domain ... A 2003 TS Licensing Server can handle TS CALs for both ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Understanding Installation/Use of Programs on TS
    ... Since the fat clients only use the server as a file server, ... By not installing the application in "install mode" ... Microsoft Volume Licensing Program can be deployed. ...
    (microsoft.public.windows.terminal_services)
  • Re: XP Home User Temp Licence from W2K TS Box
    ... Note also that there are already *9* temporary Per Device TS CALs ... MCSE, CCEA, Microsoft MVP - Terminal Server ... A 2003 TS Licensing Server can handle TS ... * then you have to install the licenses on the 2003 TSLS. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Terminal server licence problem
    ... I have posted in the SBS forum for the time being to ... The only thing I know is that SBS OS licensing is different from ... MCSE, CCEA, Microsoft MVP - Terminal Server ... there does seem to be a licencing problem. ...
    (microsoft.public.windows.terminal_services)