G
Guest
Does anyone know if a Terminal Licensing server 2003 can be installed on a Windows 2003 server cluster? Thanks
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Matthew Harris [MVP]
It shouldn't be a problem, but just remember that the TS
licensing service needs to be run on a domain controller
if you are in a Windows 2003 domain.
-M
licensing service needs to be run on a domain controller
if you are in a Windows 2003 domain.
-M
be installed on a Windows 2003 server cluster? Thanks-----Original Message-----
Does anyone know if a Terminal Licensing server 2003 can
G
Guest
Matthew, is this something specific to cluster configurations? Otherwise the TSLS can run on any 2003 server in the domain, even the TS, howeverif it's NOT running on a DC you must configure the TS License Service Discovery Override. With 2000 TS in an AD Domain the TSLS must be on a DC.
http://support.microsoft.com/?kbid=279561
Patrick Rouse
Microsoft MVP - Terminal Server
www.workthin.com
----- Matthew Harris [MVP] wrote: -----
It shouldn't be a problem, but just remember that the TS
licensing service needs to be run on a domain controller
if you are in a Windows 2003 domain.
-M
http://support.microsoft.com/?kbid=279561
Patrick Rouse
Microsoft MVP - Terminal Server
www.workthin.com
----- Matthew Harris [MVP] wrote: -----
It shouldn't be a problem, but just remember that the TS
licensing service needs to be run on a domain controller
if you are in a Windows 2003 domain.
-M
be installed on a Windows 2003 server cluster? Thanks-----Original Message-----
Does anyone know if a Terminal Licensing server 2003 can
M
Matthew Harris [MVP]
Dang...brain isn't working this late on a Friday night...
Yeah, I forgot that this was a Windows _2003_
configuration. Anyway...just putting that registry entry
in should be good enough to get the cluster up and working
with the TS Licensing Server. Sorry for the confusion.
-M
server in the domain, even the TS, howeverif it's NOT
running on a DC you must configure the TS License Service
Discovery Override. With 2000 TS in an AD Domain the TSLS
must be on a DC.
Yeah, I forgot that this was a Windows _2003_
configuration. Anyway...just putting that registry entry
in should be good enough to get the cluster up and working
with the TS Licensing Server. Sorry for the confusion.
-M
configurations? Otherwise the TSLS can run on any 2003-----Original Message-----
Matthew, is this something specific to cluster
server in the domain, even the TS, howeverif it's NOT
running on a DC you must configure the TS License Service
Discovery Override. With 2000 TS in an AD Domain the TSLS
must be on a DC.
G
Guest
No worries, I'm sure I've given bogus info more than once and had to go "Doh", shouldn't post help while deprived of sleep..
Patrick Rous
Microsoft MVP - Terminal Serve
www.workthin.com
Patrick Rous
Microsoft MVP - Terminal Serve
www.workthin.com
G
Guest
Thanks to you all ! The truth is that I didn't beleive that somebody would answer so I didn't check it during weekend. The scenario is as follows: I have a farm of terminal servers which is fine but I want to install TSLS in a 2-node server cluster active/passive but I haven't found any info on deploying TSLS in a cluster (how to make the resources, if any, how to configure etc.) Modifying the registry in my TSs could be ok that but how I can have recovery in my cluster and if one node is out then the other takes over? Could anyone provide me with info or a place where I can find any article relevant to it? Thanks in advance.
M
Matthew Harris [MVP]
Is the server cluster (that you are trying to load the
licensing service onto) addressible by one IP address and
one netbios name?
The most common procedure is to install the license
Tervice onto two machines for redundancy, and install a
majority of the licenses onto only one of the machine, but
have an activated licensing service on both machines. If
the main system dies and takes all the licenses with it,
the other system can then kick in and issue temporary
licenses that are good for 90 days. As long as you bring
up another server or install the licenses somewhere, you
should be good to go.
From the TS FAQ at
http://www.microsoft.com/windows2000/community/centers/term
inal/terminal_faq.mspx
Q. How do I configure Terminal Services Licensing (TSL)
servers for redundancy or high availability?
A. The recommended method to configure TSL servers for
high availability is to install at least two TSL servers
with available Terminal Services Client Access Licenses
(CALs). Each server will then advertise in Active
Directory (AD) as enterprise license servers with regard
to the following Lightweight Directory Access Protocol
(LDAP): //CN=TS-Enterprise-License-Server,CN=site
name,CN=sites,CN=configuration-container.
Each TSL server should contain 50% of your CALs for load
balancing within your environment. If a TSL server does
not have valid CALs, then that TSL server will attempt to
refer to other TSLs with valid CALs for license issuance.
(This applies to both enterprise license servers and
domain license servers.)
Please review the License Issuance matrix to see all
possible high-availability scenarios concerning temporary
and permanent license issuance.
Each client will begin a license request and upgrade seven
days prior to the license expiration date. This should
allow sufficient time to address any issues with
individual TSLs. If all TSL servers are down at the same
time, new clients or clients with expired licenses will be
denied access. In addition, TSL servers should be
separated by network subnets to ensure that a network
outage does not prevent users from connecting to a TSL
Server.
Finally, administrators should use the Terminal Server
Licensing Tool to ensure that at least 10% of their CALs
are available on each licensing server. Conversely, if
available licenses are limited to a single licensing
server that suffers an outage, clients with expired
licenses will be denied access immediately, and clients
with licenses expiring within 7 days will be denied access
as they meet their expiration dates.
-M
weekend. The scenario is as follows: I have a farm of
terminal servers which is fine but I want to install TSLS
in a 2-node server cluster active/passive but I haven't
found any info on deploying TSLS in a cluster (how to make
the resources, if any, how to configure etc.) Modifying
the registry in my TSs could be ok that but how I can have
recovery in my cluster and if one node is out then the
other takes over? Could anyone provide me with info or a
place where I can find any article relevant to it? Thanks
in advance.
licensing service onto) addressible by one IP address and
one netbios name?
The most common procedure is to install the license
Tervice onto two machines for redundancy, and install a
majority of the licenses onto only one of the machine, but
have an activated licensing service on both machines. If
the main system dies and takes all the licenses with it,
the other system can then kick in and issue temporary
licenses that are good for 90 days. As long as you bring
up another server or install the licenses somewhere, you
should be good to go.
From the TS FAQ at
http://www.microsoft.com/windows2000/community/centers/term
inal/terminal_faq.mspx
Q. How do I configure Terminal Services Licensing (TSL)
servers for redundancy or high availability?
A. The recommended method to configure TSL servers for
high availability is to install at least two TSL servers
with available Terminal Services Client Access Licenses
(CALs). Each server will then advertise in Active
Directory (AD) as enterprise license servers with regard
to the following Lightweight Directory Access Protocol
(LDAP): //CN=TS-Enterprise-License-Server,CN=site
name,CN=sites,CN=configuration-container.
Each TSL server should contain 50% of your CALs for load
balancing within your environment. If a TSL server does
not have valid CALs, then that TSL server will attempt to
refer to other TSLs with valid CALs for license issuance.
(This applies to both enterprise license servers and
domain license servers.)
Please review the License Issuance matrix to see all
possible high-availability scenarios concerning temporary
and permanent license issuance.
Each client will begin a license request and upgrade seven
days prior to the license expiration date. This should
allow sufficient time to address any issues with
individual TSLs. If all TSL servers are down at the same
time, new clients or clients with expired licenses will be
denied access. In addition, TSL servers should be
separated by network subnets to ensure that a network
outage does not prevent users from connecting to a TSL
Server.
Finally, administrators should use the Terminal Server
Licensing Tool to ensure that at least 10% of their CALs
are available on each licensing server. Conversely, if
available licenses are limited to a single licensing
server that suffers an outage, clients with expired
licenses will be denied access immediately, and clients
with licenses expiring within 7 days will be denied access
as they meet their expiration dates.
-M
that somebody would answer so I didn't check it during-----Original Message-----
Thanks to you all ! The truth is that I didn't beleive
weekend. The scenario is as follows: I have a farm of
terminal servers which is fine but I want to install TSLS
in a 2-node server cluster active/passive but I haven't
found any info on deploying TSLS in a cluster (how to make
the resources, if any, how to configure etc.) Modifying
the registry in my TSs could be ok that but how I can have
recovery in my cluster and if one node is out then the
other takes over? Could anyone provide me with info or a
place where I can find any article relevant to it? Thanks
in advance.
G
Guest
Matthew,
thanks for your prompt reply. Yes, the server cluster is a 2-node cluster having one IP and one NetBios name. (w2003 cluster microsoft solution).
Your solution is fine if I had a NLB farm which I have but mine is a Terminal Servers farm. I don't know if it's good in a production enviroment having a NLB Terminal servers farm who additionally are TSLS.
So, I was thinking install TSLS in a server cluster 2003 active/passive I have, but I couldn't find any information if TSLS is cluster-aware and in this case how to configure the resources, groups etc. You see, discarding install TSLS as cluster-aware in a 2-node server cluster where the 2 nodes are identical, you never know which node the customer will choose being active at anytime so the 90-days period might pass or other problems might occur. The more simple solution is have another PC or use an old W2k TSLS which I also can't use with Terminal servers 2003. If you have any idea, please reply. In each case, thanks a lot for your time and help.
thanks for your prompt reply. Yes, the server cluster is a 2-node cluster having one IP and one NetBios name. (w2003 cluster microsoft solution).
Your solution is fine if I had a NLB farm which I have but mine is a Terminal Servers farm. I don't know if it's good in a production enviroment having a NLB Terminal servers farm who additionally are TSLS.
So, I was thinking install TSLS in a server cluster 2003 active/passive I have, but I couldn't find any information if TSLS is cluster-aware and in this case how to configure the resources, groups etc. You see, discarding install TSLS as cluster-aware in a 2-node server cluster where the 2 nodes are identical, you never know which node the customer will choose being active at anytime so the 90-days period might pass or other problems might occur. The more simple solution is have another PC or use an old W2k TSLS which I also can't use with Terminal servers 2003. If you have any idea, please reply. In each case, thanks a lot for your time and help.
M
Matthew Harris [MVP]
Ok...lemme just get my facts straight...
You have a clustered farm of 2 terminal servers. They are
not running NLB. Now you want to load terminal services
licensing onto them?
If this is the case then I'm not sure what to tell you.
If the servers are all addessible through one IP address
and through no other way (like they don't have two IP
addresses) then you are probably going to have to setup
another license server outside of that cluster. Best
practices also indicates that running the TS licensing
service on loaded terminal servers isn't a good idea
anyways, since the license service can consume resources
that the terminal service might need.
You also might wan to check out this link for more
information:
http://www.microsoft.com/windows2000/community/centers/term
inal/tsfaq_matrix.mspx
-M
(w2003 cluster microsoft solution).
good in a production enviroment having a NLB Terminal
servers farm who additionally are TSLS.
if TSLS is cluster-aware and in this case how to configure
the resources, groups etc. You see, discarding install
TSLS as cluster-aware in a 2-node server cluster where the
2 nodes are identical, you never know which node the
customer will choose being active at anytime so the 90-
days period might pass or other problems might occur. The
more simple solution is have another PC or use an old W2k
TSLS which I also can't use with Terminal servers 2003. If
you have any idea, please reply. In each case, thanks a
lot for your time and help.
You have a clustered farm of 2 terminal servers. They are
not running NLB. Now you want to load terminal services
licensing onto them?
If this is the case then I'm not sure what to tell you.
If the servers are all addessible through one IP address
and through no other way (like they don't have two IP
addresses) then you are probably going to have to setup
another license server outside of that cluster. Best
practices also indicates that running the TS licensing
service on loaded terminal servers isn't a good idea
anyways, since the license service can consume resources
that the terminal service might need.
You also might wan to check out this link for more
information:
http://www.microsoft.com/windows2000/community/centers/term
inal/tsfaq_matrix.mspx
-M
a 2-node cluster having one IP and one NetBios name.-----Original Message-----
Matthew,
thanks for your prompt reply. Yes, the server cluster is
(w2003 cluster microsoft solution).
but mine is a Terminal Servers farm. I don't know if it'sYour solution is fine if I had a NLB farm which I have
good in a production enviroment having a NLB Terminal
servers farm who additionally are TSLS.
active/passive I have, but I couldn't find any informationSo, I was thinking install TSLS in a server cluster 2003
if TSLS is cluster-aware and in this case how to configure
the resources, groups etc. You see, discarding install
TSLS as cluster-aware in a 2-node server cluster where the
2 nodes are identical, you never know which node the
customer will choose being active at anytime so the 90-
days period might pass or other problems might occur. The
more simple solution is have another PC or use an old W2k
TSLS which I also can't use with Terminal servers 2003. If
you have any idea, please reply. In each case, thanks a
lot for your time and help.
G
Guest
Matthew you seem so confused on what I mean!
Well, I found out that it's positive that TSLS is not cluster-aware so I can't install it on my cluster(not NLB, not terminal servers).
I leave this scenario of clustering TSLS which was my original question.
Now I was thinking use my NLB terminal servers farm (other PCs not these ones nentioned above) and install TSLS in these PCs. You are right that many resources are consumed when you have terminal server plus TSLS. Can I override that if I modify the registry as you have mentioned or make another trick to help the situation? The terminal users might reach the number of 120 at most. Have you any idea on this scenario? Thanks in advance.
Well, I found out that it's positive that TSLS is not cluster-aware so I can't install it on my cluster(not NLB, not terminal servers).
I leave this scenario of clustering TSLS which was my original question.
Now I was thinking use my NLB terminal servers farm (other PCs not these ones nentioned above) and install TSLS in these PCs. You are right that many resources are consumed when you have terminal server plus TSLS. Can I override that if I modify the registry as you have mentioned or make another trick to help the situation? The terminal users might reach the number of 120 at most. Have you any idea on this scenario? Thanks in advance.