http://www.rootzones.net/2013/04/citrix-interview-questions.

html
The following list of command line utilities is available on a Citrix XenApp 6 server for
administration:
Command: Description
altaddr: Specify server alternate IP address.
app: Run application execution shell.
auditlog: Generate server logon/logoff reports.
change: client Change client device mapping.
ctxkeytool: Generate farm key for IMA encryption.
ctxxmlss: Change the Citrix XML Service port number.
dscheck: Validate the integrity of the server farm data store.
dsmaint: Maintain the server farm's data store.
enablelb: Enable load balancing for servers that fail health monitoring tests.
icaport: Configure TCP/IP port number used by the ICA protocol on the server.
imaport: Change IMA ports.
query: View information about server farms, processes, ICA sessions, and users. The query
command uses a set of extra nouns to identify which XenApp component should be queried for
data. Those nouns are: query farm, query process, query session, query termserver, and query
user.
These command line utilities are available on each server, but this version of Citrix XenApp leans
heavily on Windows PowerShell for many command line functions. PowerShell exposure for
Citrix XenApp is found in the XenApp 6 PowerShell SDK, which can be downloaded from Citrix.
4.5. Useful Citrix Commands
How do I recreate the local host cache?
dsmaint recreatelhc
How do I find all servers in the farm and see which one is the data collector?
query farm
How do I check the database consistency, and fix if required?
dscheck /full servers /clean
dscheck /full apps /clean
How do I join a server to a farm?
chfarm /joinfarm
How do I find the data store in Citrix?
Open the file located at C:\Program Files\Citrix\Independent Management Architecture\MF20.dsn

Check for the line that reads SERVER=TheSQLServerName. If the farm uses an Access DB it will state
DBQ=PathToMDB.

While managing your Citrix XenApp 6 farm from the comfort of the Citrix
Delivery Services Console GUI tool is a very powerful thing, you should know
that XenApp 6 also has a subset of command-line tools that are at your
disposal and can help with advanced farm management and troubleshooting:
1. Altaddr: If you're a Citrix old timer, you probably remember using this tool
before secure gateway was available, in order to extend the published
applications to users outside the secure network. In essence, what Altaddr
allows you to do is give your XenApp server an alternate IP address.
Traditionally this was an outside facing public IP address or some kind of a
NAT. Of course, the down side is if you have 100 XenApp servers, you would
need 100 public IP addresses. Altaddr is not in use or popular anymore, but it
is still there if you have the distinct situation where it makes sense.
2. App: Typically used for scripting or customizing an application's behavior.
You can use App in your scripts to control the application's environment or to
satisfy its prerequisites before the application runs.
3. Auditlog: A handy utility that, for the most part, dumps the security event
log from Windows and allows you to pipe that log into a text file. You can use
the output to audit who logged in or out of the server and when. This could
come in handy if you are troubleshooting, for example, if your print service
crashes; you can see who logged in during that time and if they are mapping a
bad driver, etc.
4. Change client: Allows you to change the client device mappings in an ICA
session, LOT, COM, USB mappings. etc.
5. Ctxkeytool: You can use this utility to generate an encryption key that can
be used when enabling IMA encrypted communication in the Citrix farm.
6. Ctxxmlss: This handy little utility allows you to modify the XML port on the
XenApp servers should you need to change that port for any reason.
7. Dscheck: I use this tool frequently to check for consistency on the Citrix
IMA data store. It is particularly handy in conjunction with the /clean switch,
which you would use to clear out any inconsistencies in the database.
8. Dsmaint: All interaction with your data store can be manipulated using this
tool. For example, if you want to change data store database servers, you can
use Dsmaint to do so. You can also use it to verify the local host cache on the
XenApp server. The Local Host Cache or LHC is a subset of the data store
database that runs on each XenApp server. Sometimes, as a troubleshooting

step, you may want to verify the accuracy of that data or even refresh it
altogether.
9. Enablelb: This utility restores XenApp servers into the load balancing mix
after they have failed Citrix health monitoring tests.
10. Icaport: Here's a too that allows you to change the default port that the
ICA protocol typically runs on.
11. Imaport: allows you to change the default port that the IMA protocol runs
on
12. Query: Arguably the most useful command-line tool, I use the query
command for troubleshooting, for verifying load on the server, for just about
anything administration related. If I need to know, I always start with the query
command. It has a subset of values:
1. Query Farm or QFARM returns information on the XenApp servers in

the farm and which one is a data collector

2. Query Session returns information about the sessions that are running

on the XenApp server

3. Query Process will return the all the running processes on the server
4. Query User or QUSER returns information about all the users on the

server
All these tools are available to you with the default installation of XenApp 6.
However, as you can see from the list above, the number of Citrix XenApp 6
command-line tools has been shrinking with each new version and that is not
because of insufficient development. Instead, it's because Citrix is kind of
following the Microsoft lead and porting most of its command-line tools to
PowerShell. Event so, XenApp 6 has a very rich PowerShell footprint, wihich I
plan to explore more in future blogs.

How to migrate a XenApp 6.5 Data Store to a new SQL server

Migration of XenApp data store to a new SQL server can be done using different
scenarios. In this article we will explain how to move a datastore to a new SQL
server using 3 different set of tools. We will follow the scenarios below:
Scenario 1: Migration using only dsmaint command
Scenario 2: Migration using mix of SQL Console and dsmaint command
Scenario 3: Migration using IMA Helper Tool

Scenario 1
Summary
In this scenario we will migrate a data store located on server XA03 to a new
database located on SQL Express installed on server XD01. To perform a
migration we will use dsmaint command. SQL management studio will be used
only in order to create a empty database on new SQL server and assign user
name and permission to the database.
Action plan is the following:
Take a backup of your exisiting datastore.
Migrate the content of data store to a new database.
Create empty database on target server
Create new dsn file pointing to the new SQL server
Migrate the content of data store to a new database.
Run dsmaint config command
Reconfigure remainig servers
On remaining servers create a new file dsn pointing to the new SQL server.
Stop IMA Service
Run dsmaint config command
Recreate local host cache
Start IMA Service
Take a backup of your exisiting datastore.
When XenApp Server Role Manager is used to install SQL Express a standard
configuration is used and database engine is configured with the following
settings:
SQL Instance name: CITRIX_METAFRAME
Database location folder: C:\Program Files (x86)\Citrix\Independent Management
Architecture
Database name: MF20.mdf
It is a best practice to always backup the XenApp database before performing
any operation on data store. To preform the backup we will use dsmain
command. The XenApp Server DSMAINT Reference contains syntax and use
details.

Important note: In many posts or articles you can find an information that
dsmaint command can be used to backup only data store stored in MS Access
database. Please remember that starting from XenApp 6 MS Access is no longer
supported and dsmaint backup command can be used to perform the backup of
data store hosted on SQL Server Express.
From the command prompt the following command is executed:
dsmaint backup c:\backup
The result is shown below:

The command dsmaint with parameter backup makes a copy of the MF20.mdf
SQL Server Express data store to the specified location. Please note that
dsmaint backup must be run on the XenApp 6.x server hosting the SQL Server
Express data store. This command will not work when you try to backup
database located on remote server hosting SQL Server Express and will not
return and error message as it is shown below:

Migrate the content of data store to a new database.

To start the database migration process we have to create an empty database on

target SQL Express server. Open SQL Server Management Studio and login with
valid credentials and expand Databases node in the left panel

Right-click Databases node and select New Database

Click OK and the new data store database is created and ready for use as shown
below:

On the XenApp server hosting the SQL Server Express data store, a new Data
Source Name (DSN) must be created for the new SQL database.
Go to Start -> Administrative Tools -> Data Sources (ODBC) and navigate to File
DSN tab. Change the Look in to C:\Program Files (x86)\Citrix\Independent
Management Architecture as shown below:

Click Add button to create a new dsn file. New dsn file must be pleaced
in C:\Program Files (x86)\Citrix\Independent Management Architecture folder.

Click on SQL Server and click Next

Click browse and navigate to C:\Program Files (x86)\Citrix\Independent

Management Architecture and type the name for new dsn file.

Click Next and Finish and configure the connection parameters as description
and server name.

Click next when completed

Click Next. If everything is configured correctly you will be switched to the next
page of the connfiguration wizard as it is shown below

If there is a problem with connection go to Client

Configuration, uncheck Dynamically determine port and enter the value for the
static port number. Please remember that SQL Express is listening on dynamic
ports unless it is configured to listed on a specific port (standard or non
standard). Please check how to configure SQL Express to accept remote
conections. Additional information on troubleshooting SQL Server 2008 R2 ODBC
can be found at http://msdn.microsoft.com/en-us/library/ms131415.aspx.

When connection is established click Next

Click Finish and test connection

To initiate the migration of data store open the command line window

In the command line window type the following command:

dsmaint migrate /srcdsn:C:\Program Files (x86)\Citrix\Independent Management
Architecture\MF20.dsn /srcuser:citrix /srcpwd:citrix /dstdsn:C:\Program Files
(x86)\Citrix\Independent Management Architecture\XA65Small.dsn
/dstuser:domain\administrator /dstpwd:password and press Enter.
/srcdsn is the SQL Server Express MF20.dsn that was created when the XenApp
server was installed
/srcuser and /srcpwd are both, by default, citrix
/dstdsn is the new DSN file
/dstuser and /dstpwd are the username and password of the account that has
rights to the new SQL Server data store database
Note: I had a problem with dsmaint migrate command presented above. The
command syntax is correct and should work but in my case it does not. I used
simple trick with ms dos variable:
set H=c:\Program Files (x86)\Citrix\Independent Management Architecture
dsmaint migrate /srcdsn:%H%\MF20.dsn /srcuser:citrix /srcpwd:citrix
/dstdsn:%H%\XA65Small.dsn /dstuser:lab\administrator /dstpwd:password

When finished click Yes on the Dsmaint confirmation popup

The result of dsmaint command is displayed in the command prompt window:

In the next step IMA service needs to be configured to connect to the new data
store. Open the command prompt and stop IMA service:

Type command dsmaint config /user:lab\administrator

/pwd:password /dsn:C:\Program Files (x86)\Citrix\Independent Management
Architecture\XA65Small.dsn and press Enter

Type dsmaint recreatelhc and press Enter. This command will recreate Local Host
Cache file.

Start IMA service

At this stage the migration of the server hosting data store is completed. If your
XenApp farm consist of more than 1 server all remaining servers must be
configured to connect to new data store.
Reconfigure remainig server
On the server migrated in the previous step open folder C:\Program Files
(x86)\Citrix\Independent Management Architecture and edit new dsn file in my
case fileXA65Small.dsn

Remove the computer name from the WSID line. The WSID line is not used.

Copy modified XA65Small.dsn to all farms member servers into C:\Program Files
(x86)\Citrix\Independent Management Architecture folder and follow update
steps.
Open the command prompt and stop IMA service:

Type command dsmaint config /user:lab\administrator

/pwd:password /dsn:C:\Program Files (x86)\Citrix\Independent Management
Architecture\XA65Small.dsn and press Enter

Type dsmaint recreatelhc and press Enter. This command will recreate Local Host
Cache file.

Start IMA service

Scenario 2
Summary
In this scenario we will migrate a data store for farm XA_65_LAB located in
database XA65LAB on server XD01 into new database XA65LabNew located on
the same server. Farm XA_65_LAB consist of 2 server XA01 and XA 02. Both
XenApp servers are configured with the Controller and Session-host mode
enabled.
Action plan is the following:
Take a backup of your exisiting datastore.
Restore content of data store to a new database.
Create empty database on target server
Restore a backup to newly created database
Create new dsn file pointing to the new database.
Run dsmaint config command
Reconfigure remainig servers
On remaining server create a new file dsn pointing to the new database.
Stop IMA Service
Run dsmaint config command
Recreate local host cache

Start IMA Service

Take a backup of your exisiting datastore.
Open SQL Server Management Studio and login with valid credentials and
expand Databases node in the left pane

Right-click database XA65LAB node and select Tasks -> Back Up

In section Destination click Remove button to remove default backup file

Click Add button and select Backup folder and type name for backup file.

Click OK

Wait for confirmation window.

Restore content of data store to a new database.

To start the database migration process we have to create an empty database.
Open SQL Server Management Studio and login with valid credentials and
expand Databases node in the left panel

Right-click Databases node and select New Database

Click OK and when new database is created and right-click new database
XA65LabNew and seclect Task -> Restore -> Database

Select Device option and click Browse button

Click Add and navigate to the folder where data store backup was saved and
select latest backup file.

Click OK

In section Destination select new database name XA65LabNew

Select Files in the left pane and in Restore As select database files for new
database. Note: This setp is very important otherwise orginal database files will
be overwritten !!!!

Click Options in the left pane and select Overwrite the existing database

Press OK

Database has been restored successfully.

On the XenApp server performing the function of data colector, a new Data
Source Name (DSN) must be created for the new SQL database. To identify a
server working as data colector run QFARM command from command prompt.
Data colector will be marked with D as is shown below:

On server XA01 goto Start -> Administrative Tools -> Data Sources (ODBC) and
navigate to File DSN tab. Change the Look in to C:\Program Files
(x86)\Citrix\Independent Management Architecture as shown below:

Click Add button to create a new dsn file. New dsn file must be pleaced
in C:\Program Files (x86)\Citrix\Independent Management Architecture folder.

Click on SQL Server and click Next

Click browse and navigate to C:\Program Files (x86)\Citrix\Independent

Management Architecture and type the name for new dsn file.

Click Next and Finish and configure the connection parameters as description
and server name.

Click next when completed

Click Next. If everything is configured correctly you will be switched to the next
page of the connfiguration wizard as it is shown below

If there is a problem with connection go to Client

Configuration, uncheck Dynamically determine port and enter the value for the
static port number. Please remember that SQL Express is listening on dynamic
ports unless it is configured to listed on a specific port (standard or non
standard). Please check how to configure SQL Express to accept remote
conections. Additional information on troubleshooting SQL Server 2008 R2 ODBC
can be found at http://msdn.microsoft.com/en-us/library/ms131415.aspx.

When connection is established click Next. Change the default database to the
database which will be used as a new data store

Click Next and Finish and test connection

In the next step IMA service needs to be configured to connect to the new data
store. Open the command prompt and stop IMA service:

Type command dsmaint config /user:lab\administrator

/pwd:password /dsn:C:\Program Files (x86)\Citrix\Independent Management
Architecture\XA65LabNew.dsn and press Enter

Type dsmaint recreatelhc and press Enter. This command will recreate Local Host
Cache file.

Start IMA service

At this stage the migration of the server hosting data store is completed. Server
XA02 must be configured to connect to new data store.

Reconfigure remainig server

On the server migrated in the previous step open folder C:\Program Files
(x86)\Citrix\Independent Management Architecture and edit new dsn file in my
case file XA65LabNew.dsn

Remove the computer name from the WSID line. The WSID line is not used.

Copy modified XA65LabNew.dsn to server XS02 into C:\Program Files

(x86)\Citrix\Independent Management Architecture folder and follow update
steps.
Open the command prompt and stop IMA service:

Type command dsmaint config /user:lab\administrator

/pwd:password /dsn:C:\Program Files (x86)\Citrix\Independent Management
Architecture\XA65LabNew.dsn and press Enter

Type dsmaint recreatelhc and press Enter. This command will recreate Local Host
Cache file.

Start IMA service

Scenario 3
Summary
In this scenario we will migrate a data store for farm XA_65_LAB located in
database XA65LabNew on server XD01 into new database XA65DataStore
located on the same server. Farm XA_65_LAB consist of 2 server XA01 and XA
02. Both XenApp servers are configured with the Controller and Session-host
mode enabled.
Action plan is the following:
Take a backup of your exisiting datastore.
Restore content of data store to a new database.

Create empty database on target server

Restore a backup to newly created database
Run IMA Helper Tool to create dsn file and recreate local host cache
Reconfigure remainig servers
On remaining server create a new file dsn pointing to the new database.
Stop IMA Service
Run IMA Helper Tool to create dsn file and recreate local host cache
Start IMA Service
All steps related to backup and data base restore are the same as in scenario 2.
Please folow instruction starting from scenario 2. When newly created database
is updated with latest backup start IMA Helper Tool as described below.
IMA Helper Tool
IMA Helper is designed to facilitate the process of running DSMAINT CONFIG on
XenApp servers. The tool provides a Graphical User Interface for DSMAINT
CONFIG to the XenApp Administrator.
Download IMA Helper Tool from Citrix Website and save it to the server folder.
Open command prompt, stop ima service and run IMAHelper.exe

Click Create New DSN to create new connection file. ODBC window will be open

Open File DSN tab and create new dsn file using procedure described in scenario
2. I created XA65DataStore.dsn dsn file.

Enter valid credentials and press Run to execute dsmaint config command.

Wait for confirmation popup

Click OK and run RecreateLHC

button

Wait for
confirmation popup

Start IMA service

XenApp 6.5 load values explained

The load evaluator is a thread in the IMA Service on a XenApp Server that calculates the load index
for that server. The load index is an integer value from 0 to 10,000 that represents how busy is
XenApp server. A value of zero represents no load, while a value of 10,000 indicates the particular
server is fully loaded and is not accepting any new connections.
To dispaly the current load on the server, administrator can run the command qfarm /load or query
farm /load. Load vaules as reported by qfarm utility:
0 to 9998 This is the normal range for Load Manager.
99999
No load evaluator is configured.
10000
Load is at 100 percent (full load).
20000
The AppCenter console contains an incorrect server edition or a license mismatch.
99990
Results when a custom administrator with restricted rights runs the following QFARM
commands:

QFARM SERVER /APP

QFARM /APP

QFARM /APP <appname> The QFARM command may not return any results when a custom
administrator runs the following queries: QFARM /DISC

QFARM /LOAD

QFARM /ZONELOAD

How the server load is calculated ?

The current load is a result of the calculations and sum of the values of all the rules in each and every
load evaluator which applies to the server. The base algorithm for establishing actual load
is: Highest_Load + (Average_Other_Loads * .1).
One important factor to understand is once any single rule reaches its maximum value, the load
value for that server becomes 10,000, effectively removing the individual server from
contention for new sessions. Individual servers continuously update the respective zone data
collector with their current score every 15 seconds under normal conditions, or after each and every
logon or logoff of a user session.
What are the Ports does Citrix commonly use?
License Manager Daemon TCP 27000 handles initial point of contact for license requests
License Management Console TCP 8082 Web-based administration console
Citrix Receiver TCP 80/443 Communication with Merchandising Server
ICA TCP 1494 Access to applications and virtual desktops
ICA with Session reliability TCP/2598
IMA TCP 2512 Independent Management Architecture (IMA)
Management Console TCP 2513 Citrix Management/XenApp Advance Consoles
Application / Desktop Request TCP 80/8080/443 XML Service
Database TCP 1433 Microsoft SQL Server
DNS TCP/UDP 53
TFTP UDP 69 Trivial File Transfer
QueryDS.exe tool is located in Support\debug\w2k3. QueryDS can query data
contained on the data collectors regarding the load management subsystem (LMS). The
three tables that can be queried are:
LMS_AppLoadTable Information on load management for published applications. This
table will only contain data when a load evaluator is applied to a published application.
LMS_ServerLoadTable This will show the current load value for all servers in the zone,
along with the rules applied and the current value for each rule.
LMS_LicensedServerTable Provides a list of all licensed servers in the farm and which
zone each server is a member of.

Citrix Administrator Interview Questions

1) Explain Citrix Logon Process.
2) Purpose of Zone
Zone is subset of Farm. It is a grouping of Citrix Servers that shares the common Data Collector
3) When would you suggest creating new zones?
Users need to access the closest application in a geographically dispersed environment

Presentation Server is part of a disaster plan that fails over to an alternate location

The same published applications are hosted in multiple zones

User-specific backend data is located in other locations than the main data center
4) How big a zone can get?

Its just a matter of looking at the traffic patterns. For instance, do you want one single data
collector updating 1000 servers whenever you make a change to the environment (one zone), or
do you want two data collectors to each update only 500 servers (one zone).
5) When would you suggest creating new farm?
When you want the member servers talk to different datastore like a test environment;
6) What is a Data Store?
This is the place where all the static information are stored. Farm configuration information,
Published Application configurations, Server configurations, Static policy configuration, XenApp
administrator accounts, and Printer configurations) that all servers can refer.
7) How to migrate datastore database from SQL2000 to SQL2005 OR How to recover
datastore database?
Restore the DB to new server
Change mf20.dsn on all servers starting with data collectors
Restart IMA service on all servers
8) How to find out the datastore database server name?
Examine the DSN file which contains the connection details to the database.
C:\Program Files\Citrix\Independent Management Architecture\MF20.dsn
The following is an example of an MF20.dsn file from a server connecting to a remote SQL
Server instance:

[ODBC]
DRIVER=SQL Server
UID=useraccount
Address=SqlServer,1433
Network=
DATABASE=farmdb
WSID=
APP=Citrix IMA
SERVER=SqlServer
9) How to verify Datastore DB connectivity?
To determine if a server is communicating regularly with the data store, check the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\CITRIX\IMA\DataStoreFailureTime
If the value is all zeros, the MetaFrame server is communicating with the data store.
10) How often does the member servers check datastore database?
By default, every 30 minutes.
11) what happens if datastore connectivity is lost?
If the server loses its connection to the central data store, theres 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
wont 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.)
12) How will you remove Citrix server from the farm?
If the server is unresponsive, remove it by right click on server in the console.
For functional server, remove it from add/remove programs
use CHFARM command
13) How will you remove citrix server from the datastore DB?
When citrix is uninstalled from the server, it cleans the entry from data store database.
Additionally you can run this command to remove the entry from Datastore DB.
DSCHECK /servername

14) How to clean up datastore database?

DSCHEK without parameters will check for consistency and clean up the database. /clean
parameter can be used to clean up specific server/application from the datastore but use with
caution.
15) How do you troubleshoot printing issues?
Check print spooler service
Check printer mapping errors in event log
Check printer driver availability n compatibility
Check printer policies for over rides
16) How do you configure session printers?
Through Citrix policies. Add the printer drivers first, map the printer and then assign to user/group
17) What does secure gateway d0?
18) What are monitors in Netscaler?
Netscaler uses monitors to track the status of back end servers. These monitors can be http, tcp,
ping etc
19) What would you do if you see a service down in Netscaler?
Try pinging the actual server from netscaler CLI and verify its responding
20) How do you configure NetScaler? What are the pre-requisites?
16) Can you monitor Citrix services through EdgeSight?
17) How do you configure alerts in EdgeSight?
18) How many users can you host on XenApp 6.5 vs XenApp 5.0?
19) How do you manage capacity planning with EdgeSight?
20) What are the challenges that you have faced in current environment?
21) What happens if you stop the XML service on a server?
Existing users wont be impacted, but no new users will be able to access the applications
published from the server.
22) XML service down on serverA which has 10 applications; can you access the
applications?

Existing users wont be impacted, but no new users will be able to access the applications
published from the server.
23) What is Citrix XML service?
The Citrix XML server is a component of Citrix XenApp and XenDesktop thats used to
enumerates available resources and provide secure tickets for users that to use the WebInterface
or CloudGateway.
XML service has two functions:
Communicating with the XenApp farm / XenDesktop zones; the XML broker

Generating and validating secure ticket to authorize users, the Secure Ticket Authority
(STA)
24) How to change the port used by XML service?

By default XML service uses port 80. But citrix recommends using port 8080 inorder to avoid
conflicts with IIS.
To change the port used by XML service:
In XenApp 6 and above this can be changed via Citrix policies.
In Earlier versions Use the ctxxmlss command-line utility. This can be done by unloading the
Citrix XML Service with /u, changing the port with /r<port number> and restarting the XML
service.
ctxxmlss /u
ctxxmlss /r8080
An alternative method is by changing the port in the registry (and restart the Citrix XML service
after changing).
Key :HKLM\System\CurrentControlSet\Services\CtxHTTP
Value: TCP Port
The value is listed in hex, you need to change the view to decimal.
25) Explain Citrix Load Levels?
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.
20000 :
Citrix server is unable to reach license server
26)How to recover Citrix License Server?
The Citrix servers can function without contacting the license server and it is 30-days fault
tolerant, and in Enterprise version an alert can be set with Resource Manager to send an email in
case of License Server Connection Failure. If the license server reconnects at any time in the
thirty days the problem resolves itself. If the server is not going to come back up, then the license
file, digitally signed with the case-sensitive hostname of the old license server, is the critical
component. The license file, a *.lic file, can be backed up to a thumb drive separately, and
restored to a new server with the same name of the old license server, and the Citrix License
server software installed.
27)How to recover from IMA failing?
There are many reasons that the IMA Service doesnt start
1. IMA Service load time
2. IMA Service subsystem
3. Missing Temp directory
4. Print spooler service
5. ODBC configuration
6. Roaming Profile
Check the Windows Registry setting:
HKEY_LOCAL_MACHINESOFTWARECitrixIMARuntimeCurrentlyLoadingPlugin
If there is no value specified in the CurrentlyLoadingPlugin portion of the above Windows
Registry entry then the IMA Service could not connect to the data store or the local host cache is
missing or corrupt.
If a CurrentlyLoadingPlugin value is specified the IMA Service made a connection to the data
store and the value displayed is the name of the IMA Service subsystem that failed to load.
If administrators see an IMA Service Failed error message with an error code
of 2147483649 when starting the Presentation Server the local system account might be missing
a Temp directory which is required for the IMA Service to run.
Change the IMA Service startup account to the local administrator and restart the server. If the
IMA Service is successful in starting under the local administrator account then it is likely that a
missing Temp directory for the local system account is causing the problem.
If the Temp directory is not present then manually create one as >Temp. For example:
C:\Windows\Temp
Also verify that the TMP and TEMP system environment variables point to the temporary
directory. Restart the server to restart the IMA Service
28) What is new in XenApp 6.5?

Session Lingering
Session Pre-Launch
App Center
Load Evaluators assigned to Worker Groups or OUs instead of individual servers
Datastore and Zone information configured via GPO
Sesssion Only and Controller roles
Desktop Director web console can manage XenApp sessions
MultiStream ICA ica traffic can be split into four separate TCP streams if required
Log On control feauture to drain users.
29) What would happen if you stop the IMA service on a server?
Existing users on the server will not face any issues, but no new user connections to the server
would be allowed.

How To Assign User Logon Scripts

To assign user logon scripts

Open the Local Group Policy Editor.

In the console tree, click Scripts (Logon/Logoff) . The path is User
Configuration\Windows Settings\Scripts (Logon/Logoff) .
In the results pane, double-click Logon .
In the Logon Properties dialog box, click Add .
In the Add a Script dialog box, do the following:

In Script Name , type the path to the script, or click Browse to search for the
script file in the Netlogon shared folder on the domain controller.

In Script Parameters , type any parameters that you want, the same way as you
would type them on the command line. For example, if your script includes
parameters called //logo (display banner) and //I (interactive mode), type //logo //I .
In the Logon Properties dialog box, specify the options that you want:

Logon Scripts for <Group Policy object> : Lists all the scripts that currently are
assigned to the selected Group Policy object (GPO). If you assign multiple scripts, the
scripts are processed in the order that you specify. To move a script up in the list,
click it and then click Up . To move a script down in the list, click it and then click
Down .

Add : Opens the Add a Script dialog box, where you can specify any additional
scripts to use.

Edit : Opens the Edit Script dialog box, where you can modify script information,
such as name and parameters.

Remove : Removes the selected script from the Logon Scripts list.

Show Files : Displays the script files that are stored in the selected GPO.

Additional considerations

To complete this procedure, you must have Edit setting permission to edit a GPO. By
default, members of the Domain Administrators security group, the Enterprise
Administrators security group, or the Group Policy Creator Owners security group have Edit
setting permission to edit a GPO.
Setting logon scripts to run synchronously may cause the logon process to run slowly.
Logon scripts are run as User, not Administrator, and their rights are limited accordingly.

Command Functions under Terminal Services cmd prompt utilities

change logon (Temporarily disable logons to a terminal server)
change port (Changes COM port mappings for MS-DOS program compatibility)
change user (Changes the .ini file mapping for the current user)
cprofile (Removes user-specific file associations from a users profile)
flattemp (Enables or disables flat temporary directories)
logoff (Ends a clients session)
msg (Sends a message to one or more clients)
mstsc (Runs Remote Desktop Connection)
query process (Displays information about processes)
query session (Displays information about Terminal Services sessions)
query termserver (Lists Terminal Services servers on the network)
query user (Displays information about users logged on to the system)
register (Registers a program so that it has special execution characteristics)
reset session (Allows you to reset (delete) a session from the terminal server)
shadow (Allows you to monitor or remotely control an active session of another
user)
tscon (Connects to another existing Terminal Services session)
tsdiscon (Disconnects a client from a Terminal Services session)
tskill (Terminates a process)
tsprof (Copies user configuration and changes profile path)
tsshutdn (Shuts down a Terminal Services server)
Citrix MetaFrame Commands
acrcfg (Configure autoreconnect settings)
altaddr (Specify server alternate IP address)
app (Run application execution shell)
apputil (Add servers to Configured Servers list for published applications (FR3
Only))
auditlog (Generate server logon/logoff reports)
change client (Change ICA Client device mapping)
chfarm (Change the server farm membership of the server)
clicense (Maintain MetaFrame XP licenses)
cltprint (Set the number of ICA Client printer pipes)
ctxxmlss (Change the XML Service port number)

driveremap (Remap the servers drive letters)

dscheck (Validate the server farms data stores integrity)
dsmaint (Configure the server farms data store)
icaport (Configure TCP/IP port number)
imaport (Change IMA ports)
migratetomsde (Migrate the server farms data store from a Microsoft Access
database to an MSDE database (FR3))
mlicense (Add multiple MetaFrame licenses to the server farms data store)
query (View information about server farms, processes, servers, ICA sessions,
and users)
tskill (Ends a process)
twconfig (Configure ICA display settings)
querydc (Use this utility to determine the data collector for a given zone)
queryds (Command-line utility is provided to query the current information on
the local zone data collector)
queryhr (Use this utility to display information about member servers in the
farm)
qprinter
mghook (Execute msghook only if information is requested by Citrix Technical
Support)
chfarm used to join the Citrix server to another farm
ctxxmls to change the xml service port number
dsmaint configure Citrix IMA datastore
query user retrieves current user connections
qfarm /load displays load on server
qfarm /app display published applications currently being run
qfarm /online displays online servers
qfarm /offline displays server that are offline or hung, IMA service not
running.

XenApp 6.5 Powershell Command Line

Get the list of Users currently using a published XenApp Application:
Get-XASession -BrowserName notepad | select AccountName
Get the computer(or client) name from where a XenApp Application is
launched
Get-XASession -BrowerName notepad | select ClientName, AccountName
Logoff a user(user1) session who opened MS Word application in
XenApp:
(Get-XASession -BrowserName MS Word -ServerName XenAPP1 | ?
{$_.AccountName -match User1 }).SessionID | Stop-XASession

Get all published XenApp applications on a Server

Get-XAApplication -ServerName XenApp1 | select DisplayName
Get all Desktops published in XenApp environment
Get-XAApplication | ? {$_.ApplicationType -eq ServerDesktop } | select
DisplayName
Get the users or groups who has permission to a published application:
Get-XAAccount -BrowserName App1
How to get the list of processes running in a given XenApp session on
server:
Get-XASessionProecss -ServerName XenApp1 -Sessionid 10
Rename a published XenApp Application (or change displayname of
XenApp Application):
Get-XAApplication -BrowserName My Notepad | Rename-XAApplication
-NewDisplayName My Notepad OLD
Change the description of a XenApp application:
Get-XAApplication -BrowserName My Notepad OLD | Set-XAApplication
-Description This is going to retire