Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)
I have been running terminal services on a WIn 2000 server
for 5 home users for a year now and have purchased 5
terminal services CAL's.
However one of my users has now got a new PC with the
latest version of Win XP Home Edition. He was able to
access the server for 3 months and now he cannot connect.
This is due to the server issuing the worng (cal) tokens
(basically a temporary 3 month license)when the user tries
to connect. All 3 of my pre existing XP users are o.kand
are using both home edition and professional so in fact I
have licenses spare.
I now need to revoke the windows 98 terminal services
license to issue it to the new computer. I have not got a
clue how to do this and MS want £185.00 plus vat to tell
me. NO way as I have all the correct licenses and it is
not my fault that they have changed the versions of
software.
Please advise.
I have been running terminal services on a WIn 2000 server
for 5 home users for a year now and have purchased 5
terminal services CAL's.
However one of my users has now got a new PC with the
latest version of Win XP Home Edition. He was able to
access the server for 3 months and now he cannot connect.
This is due to the server issuing the worng (cal) tokens
(basically a temporary 3 month license)when the user tries
to connect. All 3 of my pre existing XP users are o.kand
are using both home edition and professional so in fact I
have licenses spare.
I now need to revoke the windows 98 terminal services
license to issue it to the new computer. I have not got a
clue how to do this and MS want £185.00 plus vat to tell
me. NO way as I have all the correct licenses and it is
not my fault that they have changed the versions of
software.
Please advise.