Showing posts with label Citrix Xenapp. Show all posts
Showing posts with label Citrix Xenapp. Show all posts

Wednesday, 19 November 2014

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).

Requirements for Clustered License Servers

The following list outlines the requirements for setting up a license server in a Microsoft Cluster:
  • Before configuring Citrix Licensing for Microsoft clustering, you must have a fully-functional active/passive cluster environment. Citrix Licensing does not support active/active clusters.
  • To cluster the license server, you must follow the following cluster requirements in addition to any requirements from Microsoft for hardware and clustering in general.
  • You must install licensing on the cluster by starting the licensing setup program using a command line.
  • When you install Citrix Licensing on a cluster, you must specify the name of the cluster when prompted for the name of the license server during product installation.
  • Citrix recommends that you use identical license server hardware for both nodes in the cluster. In particular, Citrix recommends two network adapters on each node and the servers have one drive configured as a shared drive.
  • Each node should have two network adapters—one for connection to the public network and the other for the node-to-node private cluster network. Citrix does not support using one network adapter for both connections.
  • The public and the private IP address must be on different subnets because the Cluster Service will recognize only one network interface per subnet.
  • A name resolution method, such as DNS, WINS, HOSTS, or LMHOSTS, is necessary to resolve the cluster name.
  • Both servers that form the cluster must be in the same domain.
  • The hostname of both servers must be ALL UPPERCASE.
  • Set static IP addresses for the private network connector.
  • When you generate a license file at citrix.com, use the name of the license server cluster when prompted for the host name.
  • After you download a license file, you must copy it to the F:\Program Files\Citrix\Licensing\MyFiles folder (where F: is the shared drive for the cluster) on the license server and reread it. Alternatively, use the License Administration Console to download, copy, and reread the file.

Clustering CITRIX License server with Microsoft Clustering for High Availability



Clustering CITRIX License server with Microsoft Clustering for High Availability-


Cluster servers are groups of computers that are combined to increase availability, reliability, and scalability. Microsoft clustering functionality exists in Windows Server 2003 and Windows Server 2008. Clustering the license server lets users continue working during failure situations without interrupting their access to critical applications. When the active node in a cluster-enabled license server suffers from hardware failure, fail-over occurs automatically. Resources are available again in a few seconds to a few minutes.

Citrix Licensing supports clustering the license server with two servers in a cluster and a shared drive. That is, you can cluster the license server in a two-node Microsoft Cluster in an Active/Passive Microsoft clustering configuration.

The following steps describe how to set up your clustered Citrix License Servers:-

1.  Start your installation on the active node of the cluster (ensure that node 1 is your
active node and has all the shared resources).

2.  Run the command prompt as administrator (right-click on the shortcut and click on
Run as Administrator).

3.  Use the following command to start the Citrix License Server installation wizard:
msiexec.exe /i ctx_licensing.msi CTX_CLUSTER_RESOURCE_DLL_
PATH="C:\ctxlic" REGISTER_CTX_LS_CLUSTERING="No" /log "clsinstall.
log"

4.  Accept the license agreement and click on Next.

5.  Select the cluster-shared drive as the drive for the destination folder path on the
Change Destination Folderpage.

6.  Accept the default port numbers for the Citrix License Server services on the
Configurationpage.

7.  Finish the installation.

8.  Use the Cluster Administrator console to activate the second node as the active
cluster node.

9.  Run the command prompt as administrator (right-click on the shortcut and click on
Run as Administrator on the second node).

10. Use the following command to start the Citrix license server installation wizard:
msiexec.exe /i ctx_licensing.msi CTX_CLUSTER_RESOURCE_DLL_
PATH="C:\ctxlic" REGISTER_CTX_LS_CLUSTERING="Yes" /log
"clsinstall.log"

11. Repeat step 4 to step 7 for other Node.


Keep the following points in mind:-
·        Because you already generated license files that reference a specific server name, you must either give the cluster the same name as the original license server or rehost your license files with the new name of the license server cluster.
·        Cluster names are always ALL UPPERCASE. Host names in license files are case-sensitive; therefore, the cluster names must be all uppercase in the license file. If they are not, you must rehost your license files with the correct capitalization of the names.

Open the License Administration Console in a cluster by browsing to:
http://clustername:web service port
Where clustername is the name of the cluster and web service port is the port number for console communications (the default port number is 8082).



Tuesday, 18 November 2014

Installing Citrix License server files manually



Installing Citrix License server files manually-
  1. From a Web browser, go to http://www.citrix.com.
  2. Click Log In and enter your user ID and password.
  3. Select All Licensing Tools.
  4. From the main menu, select Allocate.
  5. Follow the process to allocate and generate your file.
  6. Select the licenses you want to download, click Download and save the file to a directory (remember the location where you downloaded the file; you will need this location). This is the suggested location:
    • C:\Program Files\Citrix\Licensing\MyFiles on a 32-bit computer
    • C:\Program Files (x86)\Citrix\Licensing\MyFiles on a 64-bit computer
  7. At the license server, copy the license file from the directory where it was saved to the MyFiles directory (C:\Program Files\Citrix\Licensing\MyFiles on a 32-bit computer, C:\Program Files (x86)\Citrix\Licensing\MyFiles on a 64-bit computer).
Imp : Ensure that the license file retains the ".lic" file extension. Some copy processes do not recognize a file type for that extension and add a ".txt" file extension during the copy. License files with the wrong file extension cannot be imported.
  1. At a command prompt, navigate to:
    • C:\Program Files\Citrix\Licensing\LS on a 32-bit computer
    • C:\Program Files (x86)\Citrix\Licensing\LS on a 64-bit computer
To ensure that your copied license files are reread by the CLS, you can run the
following command:-
c:> lmreread -c @localhost -all

Wednesday, 29 October 2014

Local Host Cache (LHC)



Each XenApp server stores a subset of the data store in the Local Host Cache (LHC). The LHC performs two primary functions:
·        Permits a server to function in the absence of a connection to the data store.
·        Improves performance by caching information used by ICA Clients for enumeration and application resolution.

The LHC is an Access database, Imalhc.mdb, stored, by default, in the <ProgramFiles>\Citrix\Independent Management Architecture folder.
The following information is contained in the local host cache:
·        All servers in the farm, and their basic information.
·        All applications published within the farm and their properties.
·        All Windows network domain trust relationships within the farm.
·        All information specific to itself. (Product code, SNMP settings, licensing information)

On the first startup of the member server, the LHC is populated with a subset of information from the data store. In future, the IMA service is responsible for keeping the LHC synchronized with the data store. The IMA service performs this task through change notifications and periodic polling of the data store.

If the data store is unreachable, the LHC contains enough information about the farm to allow normal operations for an indefinite period of time, if necessary. However, no new static information can be published, or added to the farm, until the farm data store is reachable and operational again.
Note: Prior to the release of Presentation Server 3.0, the LHC had a grace period of only 96 hours; this was due to farm licensing information being kept on the data store. Once the 96 hour grace period ended, the licensing subsystem would fail to verify licensing, and the server would stop accepting incoming connections.

When a change is made to the farm’s data store, a notification to update the local host cache is sent to all the servers in the farm. However, it is possible that some servers will miss an update because of network problems. Member servers periodically query the data store to determine if changes were made since the server’s local host cache was last updated. If changes were made, the server requests the changed information..

Refreshing the Local Host Cache

If the IMA service is currently running, but published applications do not appear correctly in ICA Client application browsing, force a manual refresh of the local host cache by executing dsmaint refreshlhc from a command prompt on the affected server. This action forces the local host cache to read all changes immediately from the data store.
A discrepancy in the local host cache occurs only if the IMA service on a server misses a change event and is not synchronized correctly with the data store.

Recreating the Local Host Cache

·        If the IMA service does not start, the cause may be a corrupt LHC.
·        If you have made extensive changes to the farm data store, such as publishing various applications, adding or removing servers from the farm, or creating new policies.
·        If you must clean the farm data store, using the DSCHECK utility, you should then rebuild the LHC on each of the servers in your farm, once the data store has been cleaned.

Steps to Recreate the Local Host Cache

1.     Stop the IMA service on the XenApp server, if it is started. This can be done using the command: net stop imaservice, or from services.
2.     Run dsmaint recreatelhc, which renames the existing LHC database, creates a new database, and modifies the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime\PSRequired key to 1.
Setting the value PSRequired to 1 forces the server to establish communication with the data store in order to populate the Local Host Cache database. When the IMA service is restarted, the LHC is recreated with the current data from the data store.
3.     Restart the IMA service. This can be done via the command line, net start imaservice, or from services.
Note: For XenApp 6 or later the registry key path is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\IMA\ RUNTIME\PSRequired to 1.
There is also an available built-in utility to check the Local Host Cache called LHCTestACLsUtil.exe file located in C:\Program Files (x86)\Citrix\System32 of the XenApp server. To run this utility, you must have local administrator privileges.


Tuesday, 28 October 2014

Difference’s between ICA (HDX new name for ICA) and RDP (RDS)



ICA stands for Independent Computing Architecture. It is a proprietary protocol for an application server system, designed by Citrix Systems. ICA/HDX is a protocol that the Citrix platform uses for transmitting keystrokes, mouse movements, and screen updates between clients and the Citrix Presentation Server.

ICA/HDX can run on top of many operating systems including Windows, Linux, iOS. ICA/HDX is designed to run over industry-standard network protocols, such as TCP/IP, NetBEUI, IPX/SPX, and PPP and industry-standard transport protocols, such as async, ISDN, Frame Relay and ATM.

Within the ICA protocol, virtual channels are used to designate the various functionalities, such as client drive mappings, video, keyboard strokes, etc. Layer 3 (IP) and Layer 4 (TCP). You can have up to 32 virtual channels.

Citrix Xenapp ICA/HDX and Microsoft’s RDP are very similar, but there are definitely differences, especially when it comes to latency and unstable connections, which ICA is able to handle better, as well as many options on how to handle those types of connections. Based on the Remote Desktop Protocol (RDP), Terminal Services was first introduced in Windows NT 4.0 (Terminal Server Edition).

Main difference’s between ICA and RDP –

ICA/HDX – Independent Computing Architecture:
-        Application publishing is supported by ICA.
-        Low bandwidth is sufficient for ICA.
-        Encryption is possible in ICA.
-        Keyboard and Mouse inputs are present in ICA.
-        ICA ensures session reliability.
RDP – Remote Desktop Protocol:
-        RDP works only under TCP/IP.
-        RDP does not support applications to run in a browser.
-        Only 128-bit encryption, using the RC4 encryption algorithm, as of Version 6.
-        Session reliability is not ensured by RDP.



Performance Differences between RDP and ICA test result –






































Like Oscar Pistorius, Microsoft might not always finish first – but you can bet on them to be a gold medalist and the inspiration for a lot of the competition.