How to recover a lost password for your Citrix License Server(CLS) Administration Console user-

How to recover a lost password for your Citrix License Server(CLS) Administration Console user-

1. Open the “server.xml” file in C:\Program Files\Citrix\Licensing\LS\conf. If on Win2k8 you will need to open your editor as an admin. (Take a copy of the file first – if anything goes wrong you can simply copy the file back to restore the original settings).
2. Find the entry that looks something like this:
<user firstName=”System” id=”admin” lastName=”Administrator” password=”(ENC-01)LKJ338u98uxkllS(*U+ljljlja-$78923ghJgs” passwordExpired=”false” privileges=”admin”/>;
3. Erase the contents between the double quotes after “password=”
4. Enter a plain text password , for example password=”TemporaryPassword”
5. Change the passwordExpired value to be “true” and save the server.xml file.
6. Restart the licensing services or, at a push, reboot the server.
7. Log into the licensing console using user name “admin” and the password set above.
8. You will be prompted to change your password. The new password will be encrypted in the server.xml file.

Troubleshooting Cluster-Enabled License Servers

 If any of the licensing services fail to start, the cluster detects that licensing is offline and attempts to restart the service three times (by default). If these attempts are unsuccessful, fail-over to the next node is initiated and the cluster attempts to start the services on the second node. If the attempts fail on the second server, the process may enter into an infinite loop. In this case, the computers running Citrix products fall into the grace period. During the grace period, client connections are not affected.

When troubleshooting a cluster-enabled license server, try the following:

• If you move the resources to the other node, do you still see the issue?
• Does your license file have the cluster HOSTNAME in uppercase? The cluster hostname is always uppercase.
• For Windows Server 2003:
  1. In the Cluster Administrator, under the cluster name, expand Cluster Configuration > Resource Types.
  2. Verify that ctxlsclustres is a valid resource type (appears in green).

• For Windows Server 2008 and Windows Server 2008 R2:
  1. In the Failover Cluster Management window, from the left pane, select the cluster. In the middle pane, the summary information for the cluster appears.
  2. Click the Cluster Core Resources title to expand the section.
  3. Verify that the cluster resources are all online (green arrow).

Troubleshooting Slow Logon in Citrix Xenapp

Logons to Citrix Xenapp environment can be divided into following phases-

PHASE 1: USER PROFILE LOADING
PHASE 2: APPLYING GROUP POLICY OBJECTS (GPOS)
PHASE 3: USER ENVIRONMENT INITIALIZATION AND ACTIVE SETUP
PHASE 4: LOGON SCRIPT EXECUTION
PHASE 5: CITRIX APPLICATION INITIALIZATION

 

PHASE 1: USER PROFILE LOADING
Reasons for slow logon phase are:-
•  issues with network and profile storage availability,
•  high network load,
•  big profile size,
•  first time use of this profile on the server (the cached version of the roaming profile does not
exist), or
•  the corrupted profile

PHASE 2: APPLYING GROUP POLICY OBJECTS (GPOS)
Reasons for the slow logon phase are:
•  issues with required infrastructure (required services and components are either not running
or configured as expected),
•  issues with network and domain controller availability,
•  system time is not configured correctly,
•  high network load, or
•  the high amount of policy settings

PHASE 3: USER ENVIRONMENT INITIALIZATION AND ACTIVE SETUP
Reasons for the slow logon phase are:
•  issues with restoring the network connection(s),
•  the corrupted profile, or
•  first time use of this profile on the server (Active Setup hasn't been applied yet).

PHASE 4: LOGON SCRIPT EXECUTION
Reasons for the slow logon phase are:
•  issues with application compatibility scripts,
•  legacy applications, or
•  custom profile initialization.


PHASE 5: CITRIX APPLICATION INITIALIZATION
Reasons for the slow logon phase are:
•  issues with the client printer (usually third party printer drivers) or
•  issues with retrieving ICA client version and the rest of the update process. 

Process Diagram showing logon -