Re: Terminal Server Licensing issues

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

There should be an email address for support from Jeff
I know he's traveling right now but he should be picking up email and such
and if it existed before the swing...I'm sure he'll probably know right off what to look at

--
CRIS HANNA [SBS-MVP]
----------------------------------------
Please only communicate in the newsgroup. Please do not contact me directly.
----------------------------------------
Sent via Windows Mail on Windows Vista, Business Edition RC 2

"TR" <tsomething@somewhere> wrote in message news:O1NtC%23k8GHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
Cris,

Yes, the new server has the same computer name. The swing migration process did a very good job of preserving the Active Directory. This is the only big issue I am experiencing after the upgrade. I have also posted on Jeff's site but no response yet. I posted here because it may be an issue with a W2K Terminal Server in a W2K3 environment that I may not know about and not necessarily a swing migration issue.

TR

"Cris Hanna[SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A09C3978-52C4-400B-9B26-7BCAA3A12D18@xxxxxxxxxxxxxxxx
Does the new SBS server had the same computer name as the original?
You might want to touch base with Jeff M since this a swing

--
CRIS HANNA [SBS-MVP]
----------------------------------------
Please only communicate in the newsgroup. Please do not contact me directly.
----------------------------------------
Sent via Windows Mail on Windows Vista, Business Edition RC 2

"TR" <tsomething@somewhere> wrote in message news:%23bnKsCi8GHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
Hello all,

I recently migrated an SBS2000 network to an SBS2K3 Premium using the swing method. This network has a member server that is a W2K Terminal server. I have installed Terminal Services licensing on the new SBS2K3 box and reactivated the W2K Terminal CAL's for my terminal clients. The problem is that the W2K Terminal server can no longer locate the Terminal Licensing Server which is on the new SBS2K3 box. It has stopped issuing licenses to the client terminals and the client terminals are now being denied log on access. The new SBS2K3 box shows Terminal Server licensing as active with licenses but non of them have been used.

Thanks
TR






.

Relevant Pages

  • Re: Windows CE Clients not connecting
    ... Resetting the terminals to default hasn't helped, ... I now don't think it's a licensing problem since they are no longer liste in ... > MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: virtual consoles
    ... the Console to a few Terminal servers, ... ethernet connection, or whatever. ... I was thinking of using a terminal server to connect several terminals ...
    (comp.os.vms)
  • Re: virtual consoles
    ... the Console to a few Terminal servers, ... I was thinking of using a terminal server to connect several terminals ... the serial connections are going to printers or console connections, ...
    (comp.os.vms)
  • Re: Terminal Services Licenses
    ... call Microsoft Support again. ... > Open Licences are installed on a Terminal Server in Terminal ... They are per devices licences. ... > That means we reset about 45 terminals every 3 months. ...
    (microsoft.public.windows.terminal_services)
  • Dumb terminal connection now telnet
    ... I have some more info concerning the terminal server problem! ... 2048 enables me to telnet into the prime terminal server from our ... I am sure this is the crux of the problem and why all my dumb terminals no ... > confidential use of the above named recipient. ...
    (SunManagers)