ben wrote:
|| bonjour,
||
|| admettons que j'ai 3 serveur TSE, combien de gestionnaire de licence
|| j'aurais ?
|| merci
Bonjour,
Il est préférable d'avoir un seul serveur de licence (sur un DC de
préférence)
--
Eric Perromat
http://pameri.chez.tiscali.fr et http://eperromat.free.fr/forum
ben wrote:
|| bonjour,
||
|| admettons que j'ai 3 serveur TSE, combien de gestionnaire de licence
|| j'aurais ?
|| merci
Bonjour,
Il est préférable d'avoir un seul serveur de licence (sur un DC de
préférence)
--
Eric Perromat
http://pameri.chez.tiscali.fr et http://eperromat.free.fr/forum
ben wrote:
|| bonjour,
||
|| admettons que j'ai 3 serveur TSE, combien de gestionnaire de licence
|| j'aurais ?
|| merci
Bonjour,
Il est préférable d'avoir un seul serveur de licence (sur un DC de
préférence)
--
Eric Perromat
http://pameri.chez.tiscali.fr et http://eperromat.free.fr/forum
pour 2003 : http://support.microsoft.com/?id'9561
pour 2000 : http://support.microsoft.com/?id#9107
ben wrote:
|| Salut eric,
||
|| je crois que je suis tombé sur le pro, j'ai vu ton site super.
||
|| dis moi :
|| et si j'en voulais deux ?
|| comment faire ?
|| pourquoi je ne vois pas mon deuxieme serveur dans le gestionnaire de
|| licence ? tt laisse a croire que je ne peux avoire qu'un seul
|| gestionnaire de licence.
2 serveurs de licences pourquoi faire ? tu veux faire du Load Balancing ?
C'est du 2003
Il est tout à fait possible de faire du load balancing avec les serveurs de
licences TSE
extrait de
http://www.microsoft.com/windowsserver2003/community/centers/terminal
============================================================= >
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.
=========================================================== > Si tu ne veux pas faire de Load Balancing, il faudra forcer le
processus de découverte des serveurs de licences sur les TS.
pour 2003 : http://support.microsoft.com/?id'9561
pour 2000 : http://support.microsoft.com/?id#9107
--
Eric Perromat
http://pameri.chez.tiscali.fr et http://eperromat.free.fr/forum
pour 2003 : http://support.microsoft.com/?id'9561
pour 2000 : http://support.microsoft.com/?id#9107
ben wrote:
|| Salut eric,
||
|| je crois que je suis tombé sur le pro, j'ai vu ton site super.
||
|| dis moi :
|| et si j'en voulais deux ?
|| comment faire ?
|| pourquoi je ne vois pas mon deuxieme serveur dans le gestionnaire de
|| licence ? tt laisse a croire que je ne peux avoire qu'un seul
|| gestionnaire de licence.
2 serveurs de licences pourquoi faire ? tu veux faire du Load Balancing ?
C'est du 2003
Il est tout à fait possible de faire du load balancing avec les serveurs de
licences TSE
extrait de
http://www.microsoft.com/windowsserver2003/community/centers/terminal
============================================================= >
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.
=========================================================== > Si tu ne veux pas faire de Load Balancing, il faudra forcer le
processus de découverte des serveurs de licences sur les TS.
pour 2003 : http://support.microsoft.com/?id'9561
pour 2000 : http://support.microsoft.com/?id#9107
--
Eric Perromat
http://pameri.chez.tiscali.fr et http://eperromat.free.fr/forum
pour 2003 : http://support.microsoft.com/?id'9561
pour 2000 : http://support.microsoft.com/?id#9107
ben wrote:
|| Salut eric,
||
|| je crois que je suis tombé sur le pro, j'ai vu ton site super.
||
|| dis moi :
|| et si j'en voulais deux ?
|| comment faire ?
|| pourquoi je ne vois pas mon deuxieme serveur dans le gestionnaire de
|| licence ? tt laisse a croire que je ne peux avoire qu'un seul
|| gestionnaire de licence.
2 serveurs de licences pourquoi faire ? tu veux faire du Load Balancing ?
C'est du 2003
Il est tout à fait possible de faire du load balancing avec les serveurs de
licences TSE
extrait de
http://www.microsoft.com/windowsserver2003/community/centers/terminal
============================================================= >
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.
=========================================================== > Si tu ne veux pas faire de Load Balancing, il faudra forcer le
processus de découverte des serveurs de licences sur les TS.
pour 2003 : http://support.microsoft.com/?id'9561
pour 2000 : http://support.microsoft.com/?id#9107
--
Eric Perromat
http://pameri.chez.tiscali.fr et http://eperromat.free.fr/forum