If they are not, you must rehost your license files with the correct capitalization of the names. Host names in license files are case-sensitive therefore, the client access point names must be the same case as the host names in the license file. If not, then rehost your license files with the new name of the License Server cluster. If you already deployed Citrix Licensing and you want to migrate your deployment to a cluster-enabled server, keep the following points in mind:īecause you already generated license files that reference a specific server name, you must give the client access point the same name as the original License Server. Only one node can use the resources in a cluster at any given time. The following diagram illustrates a cluster-enabled licensing deployment:Ĭommunications in a clustered licensing environment: If the connection is interrupted, the nodes try to reconnect by the private network first, then the public network. Like most clusters, a private network is used to send heartbeats, commands, and state information between the nodes of the cluster. Web Services for Licensing port number is 8083Ĭitrix Licensing in a clustered environment.Create an exception for each of the following ports:
UNINSTALL IMPACT CLIENT WINDOWS
To work around this issue, create exceptions for Licensing components on the Exceptions tab of the Windows Firewall panel. Exception rules for CITRIX.exe and lmgrd.exe are created during the installation of Licensing, but do not work after a cluster failover. Connecting remotely to the console or checking out licenses works until failover occurs in the cluster. If Citrix Licensing is installed in a clustered environment and Windows Firewall is enabled, connections can fail. The product might briefly enter the licensing grace period and an event might be written in the product’s event log. When the active node of a clustered License Server fails, there is no impact on users connected to the Citrix product. Typically, users cannot detect when one server in a cluster fails over to another. When the active server in a cluster fails, the ownership of the resources in the cluster are transferred to another node in the cluster. Resources are available again in a few seconds.Ī typical cluster configuration has, at a minimum, one active and one passive (backup) server. When the active node in a cluster-enabled License Server suffers from hardware failure, failover occurs automatically. Clustering the License Server lets users continue working during failure situations without interrupting their access to critical applications. (Esclusione di responsabilità))Ĭluster servers are groups of computers that are combined to increase availability, reliability, and scalability. Questo articolo è stato tradotto automaticamente. (Aviso legal)Įste artigo foi traduzido automaticamente. (Clause de non responsabilité)Įste artículo ha sido traducido automáticamente. (Haftungsausschluss)Ĭe article a été traduit automatiquement. This article has been machine translated.ĭieser Artikel wurde maschinell übersetzt. Questo contenuto è stato tradotto dinamicamente con traduzione automatica. (Aviso legal)Įste texto foi traduzido automaticamente.
(Clause de non responsabilité)Įste artículo lo ha traducido una máquina de forma dinámica.
(Haftungsausschluss)Ĭet article a été traduit automatiquement de manière dynamique. This content has been machine translated dynamically.ĭieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde.
0 kommentar(er)
