Professional Documents
Culture Documents
Citrix Q&a
Citrix Q&a
Citrix allows you to install, publish and manage applications from one central location. These
published applications can then be securely access from anywhere in the world using any
client device over any connection (ex. Web Interface, Program Neighborhood, and Citrix
Program Neighborhood Agent) using the Citrix ICA client, which requires minimal bandwidth
and can virtually be installed on any Operating System.
Provide secure connection using various levels of encryption (128 bit, 128 bit login only, 56 bit,
40 bit or Basic encryption) and SSL using Secure Gateway or SSL Relay.
2. What is Datastore
Datastore is the place where all static information are stored (i.e Farm configuration
information, Published Application details, Server configurations info., Policy configuration,
Administrator accounts, and Printer configurations details etc.)
4. What is a Farm?
A Farm is a group of Citrix servers which provides published applications to all users that can
be managed as a unit, enabling the administrator to configure features and settings for the
entire farm rather than configuring each server individually. All the servers in the farm share a
single data store.
A server farm is a grouping of servers running Citrix Presentation Server that can be manage
as a unit, similar in principle to a network domain. When designing server farms, keep in mind
the goal of providing users with the fastest possible application access while achieving the
degree of centralized administration and network security that you need.
5. What is LHC?
The IMA service running on each Presentation Server downloads the information it needs from
the central data store into a local MDB database called the local host cache, or “LHC.” (The
location of the local host cache is specified via a DSN referenced in the registry of the
Presentation Server, at HKLM\SOFTWARE\Citrix\IMA\LHCDatasource\DataSourceName.
By default this is a file called “Imalhc.dsn” and is stored in the same place as MF20.dsn.)
Each Presentation Server is smart enough to only download information from the data store
that is relevant to it, meaning that the local host cache is unique for every server. Citrix
created the local host cache for two reasons:
1. Permits a server to function in the absence of datastore connectivity.
2. Improves performance by caching information used by ICA Clients for enumeration and
application resolution.
The LHC is critical in a CPS environment. In fact, it's the exclusive interface of the data store to
the local server. The local server's IMA service only interacts with the LHC. It never contacts
the central data store except when it's updating the LHC. If the server loses its connection to
the central data store, there's no limit to how long it will continue to function. (In MetaFrame
XP, this is limited to 48 or 96 hours, but that was because the data store also store license
information.) But today, the server can run forever from the LHC and won't even skip a beat if
the central connection is lost. In fact now you can even reboot the server when the central
data store is down, and the IMA service will start from the LHC with out any problem. (Older
versions of MetaFrame required a registry modification to start the IMA service from the LHC.)
The LHC file is always in use when IMA is running, so it's not possible to delete it or anything.
In theory it's possible that this file could become corrupted, and if this happens I guess all sorts
of weird things could happen to your server. If you think this is the case in your environment,
you can stop the IMA service and run the command "dsmaint recreatelhc" to recreate the local
host cache file, although honestly I don't think this fixes anything very often. Local Host Cache
is synchronised with the Data Store by the Zone Data Collector for every 30 minutes and it can
also be configured through registry
6. What is Zone?
Zone is subset of Farm. It is a grouping of Presentation Servers that shares the common Data
Collector. Zones are very helpful in controlling traffics. It collects data from member servers
and distributes changes to all servers in the farm. A zone in the Presentation Server farm
elects a zone data collector for the zone and it is responsible to communicates between other
ZDCs in the farm. It is used to redirect the users to least busy server. The ZDC maintains all
load and session information for every server in the zone. ZDCs keep open connections to
other ZDCs changes in the member servers of a zone and are immediately propagated to the
other ZDCs in the farm. Zone has server members and one of them is ZDC (Zone Data
Collectors) in each zone. These ZDCs communicate between zones. Zones are very help full in
controlling traffic. We can move the servers among the zones and after moving the servers
from one Zone to another the servers must be restarted to get settings and configurations
from the DataStore.
We can get Citrix Load levels from QSERVER /APP and QFARM /APP at the command prompt.
Load values can be inbetween 0-10000.
The following are explanations of the load levels:
9999 : No load balancing installed
0 to 9998 : “normal” load level
10000! : Application is disabled for this server
10000 : Load is at 100%
10001 : Out of licenses
10002 : Indicates that no ICA connections, listener is disabled, are available on that
server.
8. What are the default tests available in Health Monitoring & Recovery Tool?
XenApp Health Monitoring and Recovery Tool have the following default tests.
1. Citrix IMA Service test
2. Logon Monitor test
3. Terminal Service test
4. XML Service test
Health Monitoring & Recovery in the farm-wide configuration allows us to select the maximum
percentage of servers that HMR can exclude from load balancing. The default value is 10% of
server.
17. What is CtxHide? How to solve CtxHide.exe Causing Citrix Session’s to Hang on
Logon?
CtxHide.exe is responsible for hiding the DOS window in which UsrLogon.cmd is running.
Workarounds
1. Remove CtxHide.exe from the appsetup key in the registry
Use the registry editor to navigate to the following value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\AppSetup
Double Click on the AppSetup value and remove the CtxHide.exe entry as the example shows
below. Note that your AppSetup value may contain more than the following example.
Windows Registry Editor Version 6.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon]
"AppSetup"="CtxHide.exe UsrLogon.Cmd,cmstart.exe"
The result of removing CtxHide.exe is that users can see usrlogon.cmd running on logon.
2. Swap CtxHide.exe for Runh.exe
Runh.exe has been used to hide usrlogon.cmd script from the user experience prior to
Metaframe Presentation Server 3.0. It performs the same function as CtxHide.exe. For more
information on runh and to download the executable go to:
http://thin.msterminalservices.org/runh.cfm.
Download runh.exe from the above link and place the runh.exe in the server’s system32
directory. In Windows registry navigate to the AppSetup key, remove CtxHide.exe and replace
with runh. Runh will now call and hide usrlogon.cmd.
Windows Registry Editor Version 6.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon]
"AppSetup"="runh UsrLogon.Cmd,cmstart.exe"
To return to the original configuration navigate to the AppSetup value, remove runh and add
CtxHide.exe.
Each server in the zone has a rank assigned to it. The administrator can configure such that
the servers in a zone can be ranked to make the server as the most desired to serve as the
zone master or ZDC. The ties between servers with the same administrative ranking are
broken by using the HOST IDs assigned to the servers.
When a Presentation Server starts or when the IMA service starts, the IMA service starts trying
to contact other servers via the IMA protocol on port 2512 until it finds one that’s online. When
it finds, it queries it to find out which server is acting as the data collector. The winner of this
Zone Data Collector election is determined by the newest version of the IMA service. We can
control which server will act as data collector by keeping that server the most up-to-date.
Data Collection Election Priority
Whichever server has the most recent version of the IMA Service running. (This may include
hotfixes) and the server with the highest preference set in the data store
Basically data collectors and data store are not really related. The data store holds permanent
farm configuration information in a database, and the data collector tracks dynamic session
information in its RAM.
In addition to their primary role to provide dynamic farm information for admin consoles or for
incoming connection requests, data collectors also take part in the distribution of configuration
changes to Presentation Servers in the farm. When we make a changes in a presentation
server that change is written to the local host cache of whichever server we connected to, and
then immediately replicated to the data store. Presentation Server only looks for changes in
the central data store every 30 minutes. Whenever a change is made to the data store, that
change is sent to the data collector for the zone.
The data collector then distributes that change (via IMA port 2512) to all of the servers in its
zone, allowing each server to update its own local host cache accordingly. Furthermore, if we
have more than one zone, the initial data collector contacts the data collectors in the other
zones. It sends its change to them, and in turn those data collectors forward the change to all
of the servers in their zones.
Coolest part is if the change is larger than 64k, the data collectors don't send the actual
change out to its zone. Instead they send out a notification which causes the servers in the
zone to perform an "on demand" sync with the central data store. However it's rare for a single
change to be more than 64k in size.
The data collector election priority settings in the management console
Presentation Server Java Management Console > Right-click on farm name
>Properties > Zones > highlight server > “Set Election Preference”
We can totally control which server is our data collector by manually setting the preferences in
the Java console. We can manually configure four levels of Zone's Data Collector election
preference options
Most Preferred
Preferred
Default Preferred
Not Preferred
The important thing to remember is that these preferences will be ignored if a newer server is
up for election.
“Independent Management Architecture” is a term Citrix uses to describe the various back-end
components that make up a CPS environment. In the real world, IMA consists of three
components that we actually care about.
It is a database (called the “IMA Data Store”) used for storing Citrix Presentation server
configuration information, such as published applications, load balancing configuration,
security rights, policies, printer configuration, etc.
A Windows service (called the “IMA Service”) that runs on every Presentation Server that
handles things like server-to-server communication.
A protocol (called the “IMA Protocol”) for transferring the ever-changing background
information between Presentation Servers, including server load, current users and
connections, licenses in use, etc.
In Presentation Server, the IMA protocol does not replace the ICA protocol. The ICA protocol is
still used for client-to-server user sessions. The IMA protocol is used for server-to-server
communication in performing functions such as licensing and server load updates, all of which
occur “behind the scenes.”
If we open IMA data store database with SQL Enterprise Manager, we'll see it has four tables:
DATATABLE
DELETETRACKER
INDEXTABLE
KEYTABLE
IMA data store is not a real relational database. It’s actually an LDAP database. IMA Data Store
Size 1MB per server.
We can’t access the IMA data store directly through SQL Enterprise Manager. (technically you
can, but if you run a query you’ll get meaningless hex results.) If we try to edit any of the
contents of the data store directly in the database, it will be definitely corrupt.
There’s a tool on the Presentation Server installation CD called “dsview.” There is another tool
called “dsedit” a “write-enabled” version of dsview.
dsmaint
dsmaint config [/user:username] [/pwd:password] [/dsn:filename]
dsmaint backup destination_path
dsmaint failover direct_server
dsmaint compactdb [/ds] [/lhc]
dsmaint migrate [{ /srcdsn:dsn1 /srcuser:user1 /srcpwd:pwd1}]
[{/dstdsn:dsn2 /dstuser:user2 /dstpwd:pwd2}]
dsmaint publishsqlds {/user:username /pwd:password}
dsmaint recover
dsmaint recreatelhc
dsmaint verifylhc
-----------------------------------------------------------------------------------------------------------------------------------
driveremap
driveremap /drive:M
driveremap /u
driveremap /noreboot
driveremap /IME
-----------------------------------------------------------------------------------------------------------------------------------
dscheck
dscheck [Options] [ /full | /clean]
[ Servers | Apps | Printers | Groups | MSLicense | Folders | Licenses ]
dscheck /full Servers [Options] Verify/Clean or Delete the server. May be left blank.
Defaults to all servers.
/Clean - Modify the data store to correct the errors.
/DeleteAll - Delete the server entries from the data store.
/DeleteMF - Delete the MetaFrame Server entry from the data store.
/DeleteComSrv - Delete the Common Server entry from the data store.
dscheck /full Apps [Options]
< AppName> - Verify/Clean or Delete the application. May be left blank. Defaults to all
applications.
/Clean - Modify the data store to correct the errors.
/ServerCheck - Verify that all applications are hosted by valid servers.
/DeleteMF - Delete the MetaFrame Application entry from the data store.
/DeleteComApp - Delete the Common Application entry from the data store.
dscheck /full Printers [Options]
/purge_replications - Removes all printer replications from the data store.
/purge_client_printers - Removes all Client Auto-Create printers pending deletion from the
data store.
/purge_drivers - Removes all drivers that are not associated with any servers from the data
store.
dscheck /full Groups [Options]
/Clean - Removes the group object. GroupName is the relative DN from the Context.
/Clean -Removes the group from the parent group.
Use the output of DSCHECK.exe GROUPS /verify" for both ParentGroupName and GroupName.
dscheck /full MSLicense [Options]
/purge_licenses - Removes all Microsoft Licenses from the data store.
/list - Lists all Microsoft Licenses in the data store.
dscheck /full Folders /clean - Collapse orphaned folders in the data store.
dscheck /full Licenses /clean - Removes all corrupt licenses from the data store.
-----------------------------------------------------------------------------------------------------------------------------------
altaddr
altaddr [/server:servername] [/set alternateaddress ] [/v]
altaddr [/server:servername] [/set adapteraddress alternateaddress] [/v]
altaddr [/server:servername] [/delete] [/v]
altaddr [/server:servername] [/delete adapteraddress] [/v]
-----------------------------------------------------------------------------------------------------------------------------------
query
query view information about server farms, processes, servers, ICA sessions and users
query farm shows the servername, protocol and ip address
query farm /app shows the published applications
query farm /disc shows the disconnected session data for the server farm
query farm /load displays server load information
query user displays the current connections
queryhr is used to display info about the member servers in the farm. Executing queryhr with
no parameters lists all servers in the farm.
-----------------------------------------------------------------------------------------------------------------------------------
chfarm is used to change the farm membership of a Citrix server
icaport is used to query or change the TCP/IP port number used by the ICA protocol
imaport is used to change the IMA port used by the server
ctxxmlss is used to change the XML service port
enablelb is used to re-enable the server back to load balancing after it fails
twconfig confgure ICA display settings
auditlog is used to view the report of users logoff and logon activity. With auditlog /time we
can get time the users spent in the servers
Recreating the Local Host Cache after a minimum of SP1 has been installed
1. Stop the IMA service. This can be done via the command line, net stop imaservice or from
services.
2. From the command line run: dsmaint recreatelhc which renames the existing LHC
database, creates a new database and modifies the 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 datastore 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.
Recreating the LHC database on servers that do not have a minimum of SP1
installed
1. Stop the IMA service, if it is started. This can be done via the command line, net stop
imaservice, or from services.
2. Go to %ProgramFiles%\Citrix\Independent Management Architecture and rename
the imalhc.mdb to imlhc.mdb.bak
3 Launch the ODBC Data Source Administrator:
• On Windows Server, choose Control Panel > Administrative Tools > Data Sources (ODBC).
4. Select the File DSN tab and browse to %ProgramFiles%\Citrix\Independent
Management Architecture.
5. Select the imalhc.dsn file and click Configure.
6. In the Database area, click Create. The New Database dialog box appears.
7. In the Database Name box, type the name imalhc.mdb for the new local host cache
database.
8. Click OK to create the database, and then click OK to close the ODBC Data Source
Administrator.
9. Open regedt32 and navigate to the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\RUNTIME and modify the value of
PSRequired (REG_DWORD): 0x1
10. Restart the IMA service. This can be done via the command line, net start imaservice, or
from services.
31. How to disable print drivers from automatically updating the DataStore?
When a new printer or printer driver was installed on a MetaFrame server, a substantial
amount of traffic (in the order of 8 to 10MB per second) occurred between the IMA Service and
the data store the IMA Service was using. This occurred because the IMA Service needed to
update the Management Console for MetaFrame XP with the information about the new printer
or printer driver, which caused the huge amount of network traffic.
To resolve this problem, navigate to the following registry key and change the value of
fDisablePrinterWorkerThread to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMAPrinter
Type: REG_DWORD
Value: fDisablePrinterWorkerThread = 1
After making this change to the registry, restart the IMA Service for the change to take effect.
When the registry switch is set to 1, the IMA Service does not automatically update printer or
printer driver information to the Management Console. You need to update this information
manually. To do this, click Printer Management in the left panel of the Management Console
and then double-click Update Printer and Driver.
Note: Ensure the latest MfPrintSs.dll is installed on the server.
34. How to install XenApp client in command prompt and apply policies?
Run the XenAppHosted.msi in command prompt
"c:\>msiexec /a xenapphosted.msi"
This will launch "Client Packager Installation". We can create a pre-configured client package
with the answer file for the questions asked by the installer, so that we can have silent
installation of the client in various systems in the environment.
There is another way to create client installation package.
Type the command "msiexec.exe /I path/XenAppHosted.msi [Options]"
To add Group Policy to manage the client we need to add the .ADM by Citrix to the existing
Administrative Template of the Group Policy Management. This is available where Citrix Clients
have been already installed. It is located in "c:\program files\Citrix\ICA
Client\Configuration\icaclient.adm"
We can manage Citrix Client connectivity by the Windows Group Policy
35. How to change the Citrix XML Service Port on Metaframe Servers ?
Un-registering the XML Service
1. Open a Command Prompt window and run ‘ctxxmlss /u’ (This command will un-register the
Citrix XML service and mark it for deletion)
2. Reboot the server
Registering the XML on a port other than sharing with IIS
1. Un-register the service using the instructions above.
2. Open a ‘Command Prompt’ window and run ctxxmlss /r[Port Number] (Notice that there
is no space between the switch “/r” and the port number.
3. Reboot the server or open the service control manager and manually start the Citrix XML
Service
Registering the XML Service to share the port with IIS on Windows Server 2003
running IIS 6.0
By default when installing IIS 6.0, the virtual Scripts Folder is not created
1. Un-register the service using the instructions above.
2. Navigate to the ‘\Inetpub’ folder and create a new folder with the name of ‘Scripts’
3. Open the IIS Manager MMC Snap-in
4. Right click on the ‘Default Web Site’ and select New | Virtual Directory…
5. Click Next
6. Under Alias: type the name ‘Scripts’ and click Next
7. Under Path: type C:\Inetpub\Scripts and click Next
8. Under Allow the following permissions: make sure that the following are selected
a. Read
b. Run Scripts (such as ASP)
c. Execute (such as ISAPI applications or CGI)
9. Click Next and click Finish
10. Right click on the Scripts virtual directory and go to Properties
11. Under the Virtual Directory tab make sure that the Execute Permissions: field is set to
Scripts and Executables
12. Under the Directory Security tab click on Edit… under Authentication and Access Control
and make sure that the Enable anonymous access check box is checked
13. Now copy the files ctxxmlss.txt, clm.dll, wpnbr.dll to the newly create Scripts folder under
the Inetpub folder.
Note: The file ‘ctxxmlss.txt’ is located in the ‘Program Files\Citrix\System32’ folder and the files
‘clm.dll’ and 'wpnbr.dll' are located in the ‘%SYSTEMROOT%\System32’ folder
If Microsoft IIS is installed, the administrator of the MetaFrame XP installation is given the
option to install the Citrix XML Service and share a port with IIS.
In fact, no separate XML service is running. IIS serves the XML data using an ISAPI filter named
Wpnbr.dll located in the \Inetpub\Scripts folder. To remove the Citrix XML Service functionality
from your MetaFrame server, simply rename or delete the Wpnbr.dll file.
Once the XML Service port is changed on the Metaframe Servers you will need to change
NFuse or WI to point to the new port.
Citrix Secure Gateway provides secure access to Citrix Presentation Server from the
untrusted domain. Citrix Secure Gateway has evolved into the Citrix Access Gateway
solutions. The best thing about Citrix Access Gateway appliance is it is not a Windows based.
CAG is a hardened Linux appliance whereas CSG is installed over a Windows server. CSG can
only proxy ICA traffic, but including that CAG in the DMZ to provide full SSL VPN access or
more tailored filtering of access to applications and services. CAG Enterprise edition provides
High Availability, native end point scans and load balance between several WI servers. TS
Gateway from Microsoft is same as Citrix Secure Gateway that it allows access to internal
Terminal Servers from external non trusted devices through SSL
Licensing
CSG comes as a part of Presentation Server and does not require any additional licensing. The
CAG uses concurrent user licenses that are purchased separately to your Presentation Server
licenses. We need to purchase the CAG hardware as it prohibits us from running the CAG
software on any devices which are not purchased from Citrix.
Presentation Server Integration
Presentation Server is not integrated into CAG as well as CSG, though they both provide an SSL
relay function to Presentation Server. User interface access to published applications is
provided via Web Interface (WI) or Advanced Access Control (AAC, a component of Access
Gateway Advanced Edition). What the CAG has over the CSG is integration with AAC. AAC
makes it simple to control what users can do in their ICA sessions and what applications are
available externally. In this sense, it’s easier to manage application access via AAC than it is
via CAG and WI or CSG and WI alone.
Other Features
Secure Gateway does not offer any of the below advanced features of the Access Gateway
such as:
SSL: this is essentially a Winsock redirector client that’s improves on an L2TP/IPSec or PPTP
VPN by not relying on routes and using SSL only;
Web Application Access: users can access internal web applications including integration
with SharePoint Server;
Web-based File Share Access: users are able to access internal file shares via a web
browser with access to features such as uploading files control. Word, Excel, PowerPoint, Visio
and PDF files can also be viewed directly in the browser without the requirement for local
applications;
Web-based E-mail: provide users integrated access to Outlook Web Access or iNotes. Citrix
also provides a custom interface which allows the administrator to define what users can do in
their session such as downloading attachments
37. How to modify the Citrix License Port Number and Vendor Deamon Port
Number ?
By default in License Server Version 11.5 Citrix License Manager Deamon communicates over
port 27000 and the Citrix Vendor Daemon runs in 7279. You should not change this port
number unless you have a firewall that uses another port number, or if this number is already
in use.
Note: In previous versons of Citrix Licensing, the port on which the Citrix vendor daemon
communicated changed dynamically. The Citrix Licensing service chose a new port every time
it restarted.This can be changed. If you need to change the port number, you must specify the
new number in all license files on the server and in the firewall. By default, no port number is
listed in the license file. When the License Manager daemon does not find a port number listed
in the license file, it uses port 27000.
Citrix recommends that you back up your license files (files end with the .lic extension) before
you change any port numbers. License files are stored in "C:\Program
Files\Citrix\Licensing\MyFiles". Citrix License Server Version 11.5 or later provides the LS Port
Updater service that monitors the MyFiles directory and replicates the port numbers in the
license files for you automatically.
Note: Do not restart the services until all license files on the license server have the same port
number. If the License Manager daemon encounters different port numbers in the license files,
the license server stops running. The text shown above many vary slightly depending on which
version of Citrix Licensing you are running
From the Citrix License server version 11.5, Citrix provides an LS Port utility that you
can use to change the port numbers in your files. If you need to change the License Server
port or Vendor Daemon port numbers, run the License Server Port utility to enter the new
numbers and update the license files.
1.At the license server, open a command window and navigate to "C:\Program
Files\Citrix\Licensing\LS".
2.Type: lsportutil /set /lsport num /vendor num where num is the new port number. For
example, if you want to change the vendor daemon number to 24000, type: lsportutil /set
/lsport 27000 /vendor 24000
3.Restart the Citrix Licensing service.
Note: Even if you change only one port number, you must specify both of the numbers in the
command. To find out which port numbers are currently defined, type: lsportutil /query
40. What you will check when any user is not able to launch citrix application.
a) First try to launch same application from Citrix server(on which you installed and published)
e) Verify that user is having correct proxy settings to connect to your Citrix network (for
remote users)
42. What is the difference between 2k & 2k3 terminal server licensing
Server-based computing (SBC) is finally achieving an accepted status as the preferred method
for managed access and delivery of applications and desktops. This is due in part, to advances
in networking infrastructure, as well as in the Microsoft Windows® operating system itself.
1494: This port is used by any client using the TCP protocol to communicate with the
Presentation Server. You will need to open this port on your firewall for inbound connections
unless you are using some form of encapsulation or encryption. You can change the port using
the ICAPORT command but I find it to be more trouble than it is worth.
1604: Called the ICA Browser port this is a UDP port that can be used by the Program
Neighbourhood to enumerate applications. You probably won t use this though.
80: This is the default port used by the XML service and is used by clients who enumerate
applications with the TCP+HTTP or XML protocol. You will thus need to open this port on your
firewall for inbound connections if clients will be using it to locate servers. You can change the
port easily enough using the CTXXMLSS command.
443: This is the default SSL. The SSL Relay will use it to secure communications between the
Web Interface and the server farm. You could also use it to secure client communication to the
web Interface or use it for client connections to the Presentation Server.
5000: The Presentation Server uses this port to communicate with the IBM Db2 server hosting
the data store.
1521: This port is used to communicate with the Oracle data store.
1433: The port used to communicate with a Microsoft SQL data store.
2512: This port is used for server to server communication such as when load information is
communicated. The port used to access the data store is saved in the
HKLMSOFTWARECITRIXIMAIMAPORT key on the server containing the data store. All other
servers use the port number saved in HKLMSOFTWARECITRIXIMAPSSERVERPORT key in the
registry to access the data store. Have a look at IMAPORT to see how to change it.
2513: This port is used by the Presentation Server Console when connection to a server. Have
a look at IMAPORT to see how to change it.
2598: This is the session reliability port number and needs to be opened on your firewall if the
ICA Clients will be using session reliability when communication with the server.
27000 and a random port number: This is the port used for communication between the Citrix
License server and the Presentation Servers. Remember that the Citrix vendor daemon
running on the license server uses a random port. It tracks license usage.
Port 1494.
The server will respond to the client on 1494 and assign it a port number in the "high port"
range (1023-65534)
443 or 80 for Https or http
45. What you will check when any user is not able to launch Citrix application?
1) First try to launch same application from Citrix server(on which you installed and published)
5) Verify that user is having correct proxy settings to connect to your Citrix network (for
remote users)
46. Citrix Installation Manager - What is the requirement of Installation Manager and
wht kind of extension its support
Installation Manager is a powerfull feature in Metaframe XPe that facilitates the rapid
installation of applications and other software componenets.
Installation manager let you install applications other software components to any or all
available servers in your farm-attended or unattended-using any metaframe XP server on the
network regardless of physical location network connection type or hardware set up.
=========================================================
===
2. Why are Session Printers not recommended for slow WAN connections?
The print job is spooled across the WAN to the Citrix server and back again. It will cause an
already slow link to become slower.
3. What group policy file would you edit to add custom drive letters for the purpose of hiding
them from users when they login to a XenApp server?
User Configuration | Administrative Templates | Windows Explorer | "Hide these specified
drives in My Computer"
and "Prevent access to drives from My Computer"
4. Client Package MSI File - How do you create a custom ICA client package using the MSI file
from the Citrix download site?
msiexec /a ica32pkg.msi This Will run the client packaging tool.
5. Java Client - A customer has a single Citrix XenApp 4.5 server with WI installed on this Citrix
server. They are not running CSG and they do not have a CAG. The Java client has been
installed successfully and WI works
6. GP Processing Mode - What group policy processing mode is usually configured on group
policies that are applied to XenApp servers?
Loopback processing
7. Citrix Licensing - How the licensing works in Citrix and difference in Citrix Licensing version
wise
b) Then you have to purchase the concurrent licences depending on the no of users this can be
downloaded from the website .LIC file depending on the hostname of the server which is case
sensitive.
9. What is a ZDC and why is it recommended to have a dedicated one when there are more
than 5 XenApp servers?
RDP works only under TCP/IP while ICA works on many protocols.
Each performs the same virtualization channels to the end user clients.
1. Farm Level
2. Citrix Server Level
3. Policy.
15. What is Printer terminology in Citrix?
Citrix Printing can be configured 3 ways (types)
1.Local Printing.
2.Network Printing
3.Client Printing
Client Printer: The printer connected to the Workstation & the drivers are installed on the citrix
server for printing.
Network Printer: The Printer connected to the print server & the drivers should be available on
the citrix server.
Local Printer: The printer connected to locally to the citrix server & the drivers are installed for
the print operation.