Terminal server requirements

[m***@gmail.com]

Hello
I just want to know if my terminal service setup is right

-I have a Windows 2000 server (not a domain controller) that has
terminal services installed
-All my clients are either Windows 2000 or Windows XP, connected
through the LAN
-I have one or two clients who want to connect over the Internet

Do I have to install Licensing server? If yes, why?

Any comment is highly appreciated.

Thanks

[Vera Noest [MVP]]

Yes, you have to install and activate a TS Licensing server on your
Domain Controller (assuming that your TS is a member server in a
W2K domain). You do *not* have to buy or install TS licenses on the
TS Licensing Server.

The reason that you need a TS LS is that the free TS CALs which
your W2K Pro and XP Pro clients are entitled to are issued by the
TS Licensing Server.
Without a TS Licensing Server, your clients can connect for 90 days
(the TS grace period), and then they will be refused.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by m***@gmail.com
Hello
I just want to know if my terminal service setup is right
-I have a Windows 2000 server (not a domain controller) that has
terminal services installed
-All my clients are either Windows 2000 or Windows XP, connected
through the LAN
-I have one or two clients who want to connect over the Internet
Do I have to install Licensing server? If yes, why?
Any comment is highly appreciated.
Thanks

[m***@gmail.com]

Thanks for your fast reply.
My computer is a stand alone server, it is not a domain member for some
environmnt issues. Is it still OK to install LS on it?


Also, when I add license server on that machine and try to activate it,
it prompts me for some already purchased licenses. Am I doing anything
wrong to activate it?

[Vera Noest [MVP]]

No problem, you can install the TS Licensing Service on the same
server that is running TS. You don't need it to be in a domain.

You only have to install and activate the TS Licensing service. Be
sure to choose the correct Licensing program (probably "Other",
unless you have a Volume Licensing Agreement).

This shold help:

How to Activate a Terminal Services License Server and Install CALs
Over the Internet
http://support.microsoft.com/kb/237811/EN-US/

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by m***@gmail.com
Thanks for your fast reply.
My computer is a stand alone server, it is not a domain member
for some environmnt issues. Is it still OK to install LS on it?
Also, when I add license server on that machine and try to
activate it, it prompts me for some already purchased licenses.
Am I doing anything wrong to activate it?

[m***@gmail.com]

I have the same situation. Win2k stand alone server with terminal
server installed. All clients local or remote are XP pro. I have
activated License server over the internet with a pin. Under Licensing,
I choose Per Seat first but changed to Per Server, then Per Seat again
(this time it told me that I am violating agreement or something). My
questions are:
1. Under Terminal server licensing, beside the build in win2000
license, the other two are Temp licenses. Is this right?
2. Would Per Seat or Per Server matter in this case, especially to me,
do have to reinstall?

Thanks

[m***@gmail.com]

I have the same situation. Win2k stand alone server with terminal
server installed. All clients local or remote are XP pro. I have
activated License server over the internet with a pin. Under Licensing,
I choose Per Seat first but changed to Per Server, then Per Seat again
(this time it told me that I am violating agreement or something). My
questions are:
1. Under Terminal server licensing, beside the build in win2000
license, the other two are Temp licenses. Is this right?
2. Would Per Seat or Per Server matter in this case, especially to me,
do have to reinstall?

Thanks

[Vera Noest [MVP]]

You are mixing server CALs and Terminal Services CALs!
Every client that connects to your TS needs both a server CAL and a
TS CAL.

Per Seat versus Per Server is about how you license the server OS,
and how you handle your server CALs. This is managed with the
Licensing applet in Control Panel, and has nothing to do with
Terminal Services Licensing.

Your Terminal Services licesing seems to be OK. The *first*
connection from every client is made with a temporary license, so
that shouldn't worry you. But check if your clients have received
one of the "Existing Windows 2000 Per Device TS CAL Tokens" in TS
Licensing Manager (which happens when they connect for the second
time).

And check the EventLog.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by m***@gmail.com
I have the same situation. Win2k stand alone server with
terminal server installed. All clients local or remote are XP
pro. I have activated License server over the internet with a
pin. Under Licensing, I choose Per Seat first but changed to Per
Server, then Per Seat again (this time it told me that I am
1. Under Terminal server licensing, beside the build in win2000
license, the other two are Temp licenses. Is this right?
2. Would Per Seat or Per Server matter in this case, especially
to me, do have to reinstall?
Thanks