Citrix Xenapp Material

Spread the love

Troubleshooting steps for the issue 

Applications are not delivering

Trouble shooting utilities

  • Understand the problem
  • Where is the problem?
  • Client
  • Server side
  • Network
  • App crashes
  • License
  • Load information
  • User profiles


  • Client require citrix plug-in(online or offline)
  • patch levels on client side should be up to date
  • Telnet with Xenapp server
  • Network related issues
  • Check launch.ica file
  • Is the network cable connected
  • Is the network driver properly installed
  • Check your IP address configuration
  • check for blocking software like firewalls
  • check for viruses
  • check your ICA client version
  • Browser Proxy settings

Web interface issues:

  • Have you pointed your WI server to more than one citrix server for xml.
  • Have you ensure that tcp-80 and 443 is open to WI,1494 open to clients and your xml port open between WI and it’s XML service
  • Are you using the correct authentication for your configured connection
  • Are you configure properly for access gateway or secure gateway

Client auto detect 

  • Client auto detect not working? Have you uploaded the right clients to WI and have you created the right directory structure?

License issues:

  • Are the licensing services started?
  • Are the ports correct? Have the ports been changed from defaults?
  • TCP 27000 –default license port
  • TCP 8082 –default License Management Console (LMMC) port
  • Is the policy properly configured for the license server?
  • Is the license server reading the license file correctly?
  • Does the LMC show all the right licenses?
  • Is the XAS configured with the right license edition?
  • Do you have enough Citrix licenses?
  • Do you have enough Microsoft RDS licenses?
  • What’s LMC and ‘LMSTAT –a’ command showing?
  • Are you able to Telnet LS from Xen App box and vice versa?
  • Is customer using Citrix Option (Citrix.opt) file?
  • Is product going into Grace period? If not, what’s the error?
  • License Acquisition Error 500? 

Troubleshooting Installation

  • Where in the installation did the failure occur? Send a screen shot of the last panel seen before the failure occurs.
  • Are there any errors recorded in the event viewer? If so, obtain these and send them.
  • Does the problem occur with a local database
  • Is the installation performed from a CD or a network share? Does it work if the CD is

copied to the server?

  • Are you trying to install on to a Domain Controller or server with different operating system.
  • Msi installer issues

Troubleshooting IMA service and Data Store:

  • What is the Data Store type? Is it on a dedicated server? 
  • If using an SQL, Oracle, or Access Data Store where the server is not hosting the data store,
  • is using chfarm to a test Access data store possible to confirm that the Data Store is not corrupt?
  • Use Qfarm to identify which server is the Data Collector. 
  • Does changing the Data Collector help? Farm Properties (Zone – Set Election Preference)
  • Does the IMA service start? If not, what is the error message?
  • Check the Event Viewer and send any errors to Citrix Technical Support.
  • Check the troubleshooting IMA service article for possible causes
  • Try recreating the Local Host Cache (LHC) on the server
  • Has the use account used to access the data store been changed? Verify dsmaint  /config
  • Check the IMA, XML, and XTE services .are they functioning ?
  • Be conscious of zone architecture and how data collector consolidate IMA traffic. 

Troubleshooting Load Manager:

  • Have you verified load with qfarm/load?
  • Are you familiars with each load evaluators minimum and maximum values
  • And aware of how a simple evaluator impact load value?
  • Are you using Custom Connections to connect directly to a specific server? These do not use the load balancing system
  • Are you using throttled load balancing?
  • Does the issue persist when default load evaluators are used?

Troubleshooting Connectivity Issues:

  • Check article CTX106250 for Troubleshooting ICA Session Initialization steps.
  • Is the same behavior seen with a local account from the server? With an administrator account? With a brand-new user account?
  • Can you ping the server and telnet to the ICA port (1494 by default)? 
  • Are there any routers, firewalls, or proxy servers used between the client and the server?
  • Can you connect using RDP?
  • Test a connection with both TCP/IP+HTTP and just TCP/IP? (Check PN > Application Set Settings > Network Protocol.)
  • Can you make a direct ICA connection to the server? Using its NetBIOS name? IP address?
  • Using Program Neighborhood®, Web Interface, or published application?
  • Does a loopback connection work (ICA connection from the server console back to the same server)?
  • Can you delete and create a new ICA listener from the Citrix Connection Configuration tool?

Corrupt Local Host Cache?

As with most Citrix issues, the local host cache is one of the usual suspects.  If an application won’t launch, you can recreate the local host cache quickly and safely as a first stab at the issue.  Use the command: “DSMaintrecreatelhc” from the CLI on each Xenapp server in your farm.

Corrupt Published Apps?

This doesn’t seem to happen as often as it used to, but it can still come into play occasionally.  If you have ruled out other causes and you still can’t figure out why an app won’t launch – Try publishing it again from scratch in the DSC and seeing if the newly published icon works.  If it does, you can delete your old icon and point users to the new one.

Datastore Corruption?

You may want to check that the datastore isn’t showing any corruption.  Specifically I would recommend running the “DSCHECK /full applications” command to check the apps section of the database for errors.  Look for any verbage like “error”, “missing” or “not found” – and if you see that, run the same command again with the “/clean” switch appended to it.  Be sure to always back up your datastore before running this command, as it will make changes.

Load Balancer Issues?

Occasionally, applications won’t launch in a Citrix environment because of load balancer issues.  There could be issues where Citrix is “black holing” new users into a single server, overloading it, or problems where Citrix mishandles the load balancing completely.  The first step in troubleshooting a load issue is going to be using the “Qfarm /load” command.  If you notice any servers in the farm with a value of “10000” – that means they are at 100% load and can’t accept any new connections, typically. Once you know if load is being equally distributed throughout the farm, you can take action.  If you find that load is not being distributed correctly, check to make sure that your application is published to multiple servers and that it is in fact enabled.  If all other measures have failed, sometimes the Microsoft performance counters that Citrix relies on have been known to go corrupt and need to be rebuilt.

Is it limited to a specific server?

In a large Citrix farm environment, you won’t spend time looking at the load balancer or Netscaler device if you’ve been able to limit it to a specific server.  If you are sure it’s only one server in the environment, make sure that all of the Citrix services are started.  Sometimes it can be helpful to pull up the services console on the non-working server and compare it to a server that is working.  When you do a “Qfarm /load” command, does the problem server even report in?  If it’s missing from the Qfarm, then perhaps the IMA service is not started (See my other blog entry on why IMA won’t start).  If you exist all options, it may be necessary to restore the server from a snapshot (ideally), or run a Citrix repair from the install media.

Hotfix and Patch Level?

When all other options are exhausted, I’ve sometimes seen issues arise after Microsoft updates have run on a server, causing past Citrix patches or updates to get partially overwritten or corrupted.  I’ve seen cases where a client has been running fine on Roll-up 4 for years, and after we upgraded him to Roll-up 7, suddenly applications will launch again.  For these reasons, I’d always recommend checking that you are at current patch levels, and even consider reapplying a roll up pack on a test server as a last resort in such cases.  In cases where you suspect that a Microsoft update may have changed the fundamental way that Citrix and Windows Server communicate or work together, I’d recommend experimenting with rolling back a recent patch or update and judging the result.


This document provides the trouble shooting issues for applications are not delivered to end users. First find out the origin of issue, and fallowed the steps detailed above.  

Changing Data Store from one machine to another:

In order to Migrate Data Store residing on Microsoft SQL Server 2008 R2 Express install Microsoft SQL 2008 Express Management Studio tool to take a backup of MF20 Database residing on Microsoft SQL Server 2008 R2 Express.

You can download X64 Bit of Microsoft SQL Server 2008 R2 Express from here


Once you have the Management Studio Installed, Login to your Source Server and take a backup of the MF20 Database. The File Name will be MF20.Bak

Install Microsoft SQL Server 2008 R2 Express on the Host Server and install the Management Studio and Login and create a Blank Database called MF20, once you have the database created, Restore the Database which is been backed up. 

Once the restoration is Successful, now we need to point the XenApp Server to New Datastore.

Stop Citrix Independent Management Architecture (IMA)Services on the XenApp Server.

On the XenApp Server Open ODBC and click on File DSN and click on ADD, Select SQL Server and click on next and click on browse and point it to the MF20.dsn residing in the IMA Folder (C:\Program Files (x86)\Citrix\Independent Management Architecture)

Select MF20.dsn and click on Finish.

Now you need to point MF20.dsn to the New SQL Server through creating a New Data Source 

After pointing the MF20.dsn to MF20 Database on the New Server, recreate Local Host cache (LHC) on the Source Server (Please make sure you have stopped IMA Services before recreating LHC)

From Command Prompt run “dsmaint recreate lhc” command

Now Start Citrix Independent Management Architecture (IMA) Services and open Citrix Delivery Services Console and verify Farm is connecting to the Datastore.

Citrix Xenapp: IMA, Why won’t you just START?

Working in the field of application virtualization as a Citrix consultant, problems with IMA sometimes are the bulk of my support calls. Citrix Xenapp is completely dependent on the IMA service.  When IMA fails to start on a server, it can really put a damper on your day.  Often we find ourselves asking why Citrix doesn’t just tell you what it means when there is a failure, because Citrix error messages and codes can border on the ridiculously generic.  You may encounter a variety of error messages.  These errors could range from IMA related errors in the event viewer on the server, to cryptic number code errors when trying to start the IMA service via the services console.  There are many reasons that IMA may crash, or choose not to start on a server.  For the purposes of troubleshooting Citrix Xenapp, we’ll cover a few of these basic reasons in today’s blog.

Reasons IMA may not start:

–          Heavy Load: Sometimes if there is heavy load on a database, it can take longer than the 6 minutes IMA is allotted to start.  In these rare cases, IMA may eventually start anyway, and therefore the failed error messages can be disregarded as benign.

–          Corrupt Local Host Cache:  As most Citrix administrators know, the local host cache on a Citrix server can sometimes get out of line with what is in the central data store.  This seems to occur randomly most often in multi-server environments, and sometimes when servers have not been rebooted in a long time.  When IMA won’t start, often the first step a savvy Citrix administrator will take is to recreate the local host cache.  It’s considered fairly safe and commonplace to recrate the local host cache from the command prompt by issuing the “DSMAINT RecreateLHC” command.

–          Corrupt Rade Components:  Whether your environment does streaming or not, you might be surprised to know that IMA won’t start if the Rade components are corrupt.  If you suspect that this is a possibility, it’s a fairly safe procedure to recreate the Rade components from a command prompt by issuing the “DSMAINT RecreateRade” command.  I’ve personally seen this command resolve issues even in environments that weren’t using any of the streaming capabilities included in recent versions of Citrix.

–          Corrupt Service Account: Citrix IMA uses the network service account, which sometimes goes corrupt.  To verify if this account is working properly, try going into the service console and changing the account that IMA uses from the NSA to the local account.  If this resolves the issue, you’ll know you need to rebuild your account.

–          Corrupt Datastore:  Citrix, after all, is just a big database – and database corruption is a fact of life for those of us in IT.  If you’re experiencing IMA problems across multiple servers, you may be experiencing a corrupt data store.  There are many options to attempt to repair a corrupt database (I recommend running “DSCHECK /FULL ?” to see the full syntax of commands available), and these commands should be exhausted completely before proceeding further.  If you are in a small farm environment with an access database, you can easily recover a backup of the database by issuing the “DSMAINT recover” command from the CLI.  Sadly, most of us in the real world are using SQL and recovery options are not so easy.  Many of you rely on help from a DBA team, and therefore recovery will involve putting a ticket in to the appropriate group to restore your datastore from a backup.  This should be a last resort, as restoring a SQL database from backup can bring it’s own set of headaches.

–          Rebuild Link to Data Store:  For unknown reasons, sometimes the link between a Xenapp server and it’s SQL datastore can become broken or corrupted.  In order to re-establish this link and rebuild ODBC connections, it is sometimes recommended for you to reinitiate connectivity from the command line.  You can accomplish this by running the “DSMAINT CONFIG /user:username /pwd:password /dsn:DSNFilename” command from the CLI.

–          XML Service Corruption:  The degree to which XML and IMA rely on each other is debatable, but what is not up for debate is the experience I have had successfully re-registering the XML service in attempts to solve IMA issues.  Sometimes you may notice that the XML service is not started on a trouble server, or sometimes it will show that it’s started in the service console – but if you do a “Netstat –a” command from the CLI, you may see that it’s not listening on the XML port. If you have exhausted other options (Even if you don’t explicitly see XML errors in the event viewer), re-registering the XML service may be worth a shot.  Overall, it’s a pretty low risk procedure that can be accomplished by running the, “CTXXMLSS.EXE /u” first to unregister the service, and then the “CTXXMLSS.EXE /r80” command to re-register the service on port 80, or any port of your choice.

–          IP/Netbios conflict:  A rare cause of IMA issues occurs when there is another server on the network with the same Netbios name or IP address.  This can disrupt communication over IMA, and can cause the service to fail to start up.

–          Print Spooler:  What does IMA have to do with printing, you may ask?  Well, if the print spooler is hung – Citrix Admins have experienced problems with IMA operation.   You may fix this by restarting the print spooler, or in some cases by locating print drivers on the terminal server that are in a stuck state and deleting them.

–          Service Account Permissions: You may think that there is no way permissions could have changed for the service account being used for IMA, but in the field we often find that to be incorrect.  You’ll want to verify that the account you have set up for IMA has the “Log on as a service” permission on the local machine, or you may see specific error codes like “2147483647”.  Also open Regedit, and give full control rights to the local administrators group on the following key: “HKEY_Local_Machine\Software\Citrix\IMA\Data”.

–          Missing Temp Directory:  Believe it or not, Citrix IMA can fail to start if the C:\Winnt\Temp folder is missing.  If this directory doesn’t exist, try creating it and verifying that the TMP and TEMP system environment variables are pointed to it.

–           Troubleshooting IMA:

–          Event Viewer:  Sometimes the Windows event viewer can provide you with some valuable information on why IMA failed to start.  More often than not it’s only going to tell you that you’re in trouble (Which, if you are looking in the EV – chances are, you already know).

–          Check the registry:  Citrix developers did Citrix Admins a favor by including a special registry key on every Citrix server that can help you determine the reason why IMA may fail.  In order to use this registry key, simply launch regedit and browse to the “HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime\CurrentlyLoadingPlugin” and pay attention to the value in that field.  If the value mentions a particular DLL file, it may give you a clue on something that has gone corrupt or is no longer working in the environment.  According to Citrix, it should be OK to copy working DLL’s from other servers in the environment to a trouble server for troubleshooting purposes.

–          Network Ports: If you suspect that a port that IMA relies on (Such as 2512) may be blocked in your environment, try telnet’ing from one Xenapp server to another over that port.  You can use the command, “telnet <server name> 2512” to test connectivity.  If the result is a blank black window with a flashing cursor, then your traffic is flowing.  If the CLI hangs after typing in the command, chances are there may be some network hardware or a software firewall in the way.

My Server Was Running FINE!  What Happened?

Many support calls surrounding Citrix IMA are relayed from Citrix Admins who immediately state that their server has been running fine for years and nothing has changed.  While this may be true in cases wh

ere the problem was caused by random corruption, this may not always be the case.  For this reason, it’s very important to tightly control what Microsoft patches and updates go onto a Citrix server.  I’ve seen issues in the field caused by the order of patch install, or by allowing patches after certain Citrix hotfixes have been applied, etc.  There does not always seem to be logic to the cause of these types of support calls, so sometimes they’ve got to be troubleshot from the ground up like any other.

The Sledgehammer Solution:

The reason why we spend so much time troubleshooting is to try to avoid having to run a dreaded Citrix repair.  When you have exhausted 100% of the other options, and you’ve limited your IMA problems to a single server in the environment – it may be time to push the red button and begin this emergency process.  By inserting the Citrix media into the CD-Rom of the server, you can complete the repair wizard in the hopes that it resolves your issue.  If you are dealing with operating system corruption or database problems, this process probably won’t help.

Citrix Licensing 

Startup License

The startup license (citrix_startup.lic) allows Citrix products to communicate with the license server using a continuous open connection.

The Startup license does not affect the license count. It is used to allow Citrix products to communicate with the license server using a continuous open connection. Every five minutes the license server and the products send a heartbeat message to each other to verify that they are mutually communicating.

Caution: Do not edit the startup license file, or any other license files.

Options File

The options file (Citrix.opt) is a license server configuration file that the Citrix vendor daemon reads every time it restarts or receives a command to reread the file. This configuration file defines licensing behavior—the number of licenses a product server can use, the location of the system logs, and other user-defined customizations.

The options file (Citrix.opt) gives or restricts access to licenses.

The Citrix vendor daemon reads a server configuration file every time it starts or

receives a command to reread the file.

This whitepaper details the customizations that you can make by modifying the

options file. The options file is third party technology and is not specifically designed

to work with Citrix products or the way Citrix licenses its products. Note the following

important considerations:

? Modifying the options file works only with the Citrix concurrent licensing model. If

your product was purchased under any other licensing model, the modified

options file will not work properly and Citrix does not recommend nor support it.

? Modifications to the options file do not work with User/Device licensing or with

XenDesktop regardless of license type.

The License Request Process

When a product requests a license from the license server, the Citrix vendor daemon determines whether a license is available for the request.

The license request process has two phases: the product startup phase and the user connection phase.

Product Start-Up Phase

•When a Citrix product starts, it retrieves the license server location from its data store

•The product connects to the Citrix vendor daemon

•The product checks out a startup license

User Connection Phase

•A user connects to a computer running the Citrix product

•The product requests a license from the license server

•The Citrix vendor daemon checks to see if any licenses are available and grants or denies the product’s request

•The license module in the product grants or denies the use of the product based on the response from the Citrix vendor daemon

LMSTAT command shows a Client Hardware ID, a license has been assigned to that device.

Troubleshooting licensing issues in XenApp 6 and 6.5

1. Make sure the license server name on the license file has the same name as the hostname of the license server (note: the name is case sensitive, so if the hostname has upper and lower case, the license file must match the upper and lower case of the hostname)

The license file is located in c:\program files (x86)\citrix\Licensing\My Files folder. The license file has a .LIC extension.

It can be opened by MS WordPad, but it cannot be modified (it has a signed key, which is a encrypted signature for the number of licenses described in the top of the file, so if you change the number of licenses manually, the signed key won’t match the signed key and this will make your license file useless)

NOTE: The license file is tied to dates, not the version of XenApp. As long as the date interval for the license is  valid, the subscription advantage  license is valid and the license file doesn’t care what version of XenApp you have.


2. Open a command prompt and type : “netstat -a” on the licensing server and see if port 27000 is listening.

3. If you change the license file name or did any modifications  in the policies container of XenApp (DSC or Apps Center) make sure to run from the command prompt “gpupdate /force” on the server you made the change(s)

4. Open a command prompt and type “net stop imaservice” and “net start imaservice”  to restart the IMA service after the gpupdate,  so IMA can re-read the policies

5. To check if the Licensing registry key is correct: (on the XenApp server or servers), open regedit and look into the [HKEY_LOCAL_MACHINE\Software] hive for this key:



Make sure you see something like this:


“LicenseServerHostName”=”server name”

To recreate the ICA listener in XA6.0 or XenApp 6.5:

Navigate to the [HKEY_LOCAL_MACHINE\System] hive and look for this key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\ICA-Tcp]

Delete the ICA-Tcp key and reboot.

After rebooting import the ICA listener key from another server that is working properly

(see this Citrix article here for more details)

Miscellaneous information on the Licensing Server
The Citrix License Server maintans a list of users based on the concurrent license model.
The license server can be installed on the following type of servers:

File server
DB server
Web server
XenApp server

If license server fails there is a 720 hrs or 30day grace period
License server groups can be found here: ctx106282
License files are timed to dates – no specific versions of Xen App
License files are located in the c:\Program Files\Citrix\licensing\My files folder
The license file has a signed key which is the encrypted signature of the file. Modifying this file will make it unusable

Event ID 7034 logged in the EventViewer System log of the Licensing server is related
to an issue when the Citrix Licensing service unexpectedly stops on License Server 11.6.1 Build 10007 running on Windows Server 2003, when logging off the server console. This issue occurs when logging off the physical console or logging off RDP session 0 that was established using the /console or /admin switch.

The cause: The underlying code of the License Server does not properly handle the Windows logoff function

The workaround: the recovery option of the Citrix Licensing service can be modified to restart the service when it fails.

To modify the recovery option of the Citrix Licensing service, complete the following procedure:

In the Recovery tab of the Citrix Licensing service, set the response for first, second, and subsequent failures to Restart the Service.
Set the Restart service after option to 0 minutes (see the CTX article with screen shot)


Citrix Licensing Service Crashes on Startup with event id 1000:

Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Description: Faulting application lmadmin.exe, version, faulting module lmadmin.exe, version, fault address 0x0005d8c2.

The Cause:
The C:\Program Files\Citrix\Licensing\LS\conf\concurrent_state.xml and or the C:\Program Files\Citrix\Licensing\LS\conf\activation_state.xml files becomes unusable and the Citrix Licensing Service, lmadmin.exe, file does not properly handle the unusable file and crashes.

The Workaround: Delete the concurrent_state.xml and the activation_state.xml files.
Restart the license server. 

These files are recreated after restarting the license server allowing the Citrix Licensing Service to successfully start and the Citrix License Server to function normally.

This is a bug on the Citrix code for both Licensing Server 11.6 and 11.9, as confirmed here. Wait for the next version of Licensing Server

Windows Updates and Anti-Malware software can cause the License server to stop working
The License Server uses the following ports:
Port 8082 – The License Management Console uses this port and needs to be open in order for you to view the console
Port 27000 – Used by XenApp servers to communicate with the License Server
Port 7279 – Static port for the Citrix vendor daemon

If The licensing service stops working after a Windows update or because the Anti-virus, Anti malware software is blocking any of those ports, you might need to disable the Anti-virus, Anti-malware, re-open those ports or even uninstall the Windows update that blocked the port
In addition you can remove the License server installation and reinstall it by using the msi install file found in the Mycitrix website

For the License Server, version 11.9, the Add/Remove Programs may list the license software as product version 7.6, but the registry key should list both the version and the product version of the software, so it should list the version as 11.9 and product version of 7.6. Not sure why this is done but it can be confusing for sure.
The registry key should be HKLM\Software\Citrix\Licensing Server\Install, Check to make sure that is the case and don’t worry: “It is working as designed”!


Xen Desktop User Device licensing issue; Using the new Citrix Licensing VPX appliance (Linux based)

Question:Protocol driver error while making a connection:

Resolution 1:

Complete the following procedure to ensure that both RDP and ICA listeners are not set to a specific network adapter. 

  1. Open Administrative Tools from the XenApp Server(s).
  2. Browse to Remote Desktop Services.
  3. Click Remote Desktop Session Host Configuration.
  4. Select RDP listener.
  1. Right click, navigate to properties and verify all network adapters are selected.
  2. After verifying all Network Adapters are selected, review the ICA adapters (only applies to XenApp 6 / Windows 2008 R2 x64). Click on Start > All Programs > Citrix > Administrative Tools > ICA Listener Configuration

Resolution 2:

Check the XTE Service status. If Session +Reliability is enabled, XTE service is required to broker the connection to the XenApp Server. 

Refer to CTX106531 – Troubleshooting the Citrix XTE Service and Errors: There is no route to the specified address … protocol Driver Error for more information about XTE Service.

Question: Trouble shooting the ICA message: protocol driver error


Personally I think this is a rather poor chosen error message. Protocol driver error within a Citrix environment can mean so many things. But it comes down to this: the client cannot find the server. So if it were up to me, I’d change this message to ‘The ICA client cannot connect to the XenApp server’. 


‘Protocol drive error’ can have so many causes, and here’s a list of things you should check. 

1 – Step one is to determine were the problem is, we split that up in 3 groups;

client, the XP workstation or thin client

transport, network cables/switches/firewall

server, XenApp server/load balancer

To determine which is your case is usually fairly simple: 

-How much people have the problem;

1 – usually the client

2 to department size (50-100) – usually transport (network)

All people cannot login; usually server problems

These figures are indicative, it is very well possible they don’t count in your case!

2 – Client problems

Here’s a list of things you could check;

-is the network cable connected

-Is the network driver properly installed

-check you IP configuration

-check for blocking software like firewalls

-check for viruses

-check your ICA client version

Sometimes it faster and easier to just replace the whole client, specially with thin clients. Or sometimes a reinstall is faster than troubleshooting. 

3 – Transport problems

At one of the faulty clients;

-check the IP configuration;

– check network card physically, cable, link LED, follow the cable to the outlet. 

– check the default gateway, see if you can ping the default gateway

– check the DHCP settings

– try to resolve one of your XenApp servers at the client

-ping one of the XenApp servers

-Use telnet to see if the port is blocked somewhere during transport, do a:

 C:> telnet ctxsvr01 1494 

If the ICA protocol is listening you should get a black empty screen, with a few ‘ICA’s appearing. If not, this means that either the server is not listening on port 1494, or some network component is blocking traffic on this port. This is usually a firewall, so contact your network administrator if you suspect the port is being block underway.

*in this example we use port 1494, the default ICA port, this might be different in your environment!

**You can easily spot the difference from listening port and a non-listening port by connecting to a port number from which you know for sure no service is listening, for example;

C:\> telnet ctxsvr01 15121

Telnet usually responds with something like; ‘cannot connect to host, on port 15121’ 

 4 – Server problems

If no one can connect to you published applications, or if all people sometimes get ‘protocol driver error’ something might be wrong with your XenApp setup. 

 Webinterface/CAG If you use a Citrix Access Gateway/Citrix Secure Gateway/Netscaler to connect via NFuse/Webinterface to your XenApp/Presentation server farm, rule out these components by connecting to the XenApp servers directly using the Program Neighbourhood. If connecting via the Program Neighbourhood doesn’t pop up ‘protocol driver error’s’, you are sure it must be your CAG/WI setup. (WI=Web Interface) Things to check in your CAG/WI setup:

-Are all STA’s configured correctly and responsive. (you can turn on logging)

-Have you chosen the correct access method; 




-Gateway Direct

-Gateway Alternate

-Gateway Translated

-Double check the ‘access routes’, ‘Firewall translations’ and ‘Gateway settings’.

 Server general When you connect to your published application using the Program Neighbourhood till shows ‘protocol driver error’, it must be the load balancer or one of your XenApp servers. Isolate the issue by replicating the published resource and have it end up at one XenApp server. For each server involved you should check:

-can you ping the server

-Check the load balancing, on a XenApp server: qfarm /load

-is the IMA service running

-is the logon service running

-is the server listening on port 1494

-try bypassing your entire Citrix setup by connecting with RDP

These things can be automated using Farm Monitor, Farm Monitor automaticly discovers every XenApp server in a farm, and monitors the most important services and ports. You can choose what service to monitor, by default Farm Monitor monitors; IMA service, Logon and the print spooler.  More information: http://www.gourami.eu/products/farm-monitor.

Citrix Services

Display Name (Service Name)ExecutableLogon Account / Startup TypeDescriptionDependencies
Citrix 64-bit Virtual Memory Optimizationctxsfosvc64.exeLocal SystemManualDynamically optimizes 64-bit applications running on a XenApp server.None
Citrix Client Network(CdmService)cdmsvc.exeLocal System AutomaticMaps client drives and peripherals for access in sessions.Client Drive Mapping (CDM)Windows Management Instrumentation Driver ExtensionsWorkstation
Citrix CPU Utilization Mgmt/CPU Rebalancer (CTXCPUBal)ctxcpubal.exe.\ctx_cpuuser ManualOne of the services for the CPU Utilization Management feature.This service enhances resource management across multiple CPUs. This service is installed only on servers that have multiple CPUs.None
Citrix CPU Utilization Mgmt/Resource Mgmt(ctxcpuSched)ctxcpusched.exeLocal System ManualOne of the services for the CPU Utilization Management feature.Manages resource consumption to enforce entitlement policies.Remote Procedure Call (RPC)
Citrix Diagnostic Facility COM Server (CdfSvc)CdfSvc.exeNT AUTHORITY\ Network Service AutomaticManages and controls diagnostic trace sessions, which are used to diagnose problems on a XenApp server.Remote Procedure Call (RPC)
Citrix Encryption Service encsvc.exeNT AUTHORITY\ Local Service AutomaticEnables secure communication with RC5 128-bit encryption between XenApp Plug-ins and XenApp.Windows Management Instrumentation Driver Extensions
Citrix End User Experience Monitoring (Citrix EUEM)SemsService.exeLocal Service ManualCollects and collates end-user experience measurements.Citrix SMC Support Driver
Citrix Health Monitoring and Recovery (CitrixHealthMon)HCAService.exeNT AUTHORITY\ Local Service AutomaticProvides health monitoring and recovery services in the event problems occur.Citrix Independent Management Architecture serviceTerminal Services
Citrix Independent Management Architecture(IMAService)ImaSrv.exeNT AUTHORITY\ NetworkService AutomaticProvides management services in the XenApp farm.Citrix Services Manager serviceIPsec Policy AgentRemote Procedure Call (RPC)TCP/IP Protocol DriverServerWindows Management Instrumentation Driver ExtensionsWorkstation
Citrix MFCOM Service (MFCom)mfcom.exeNT AUTHORITY\ NetworkServiceAutomaticProvides COM services that allow remote connections from the management tools.Remote Procedure Call (RPC)Citrix Independent Management Architecture serviceCitrix Services Manager service
Citrix Print Manager Service(cpsvc)CpSvc.exe.\ctx_cpsvcuser AutomaticManages the creation of printers and driver usage within XenApp sessions. This service supports the Citrix Universal Printing features.Print SpoolerRemote Procedure Call (RPC)
Citrix Secure Gateway Proxy(CtxSecGwy)CtxSGSvc.exeNT AUTHORITY\ Network ServiceAutomaticProxy to the Citrix Secure Gateway server.None 
Citrix Services Manager(IMAAdvanceSrv)IMAAdvanceSrv.exeLocal System AutomaticProvides XenApp with an interface to the operating system. Other services use this services to perform elevated operations.None
Citrix Streaming Service(RadeSvc)RadeSvc.exe.\Ctx_StreamingSvc AutomaticManages the XenApp Plug-in for Streamed Apps when streaming applications.Remote Procedure Call (RPC)
Citrix Virtual Memory OptimizationCTXSFOSvc.exeLocal System ManualDynamically optimizes applications running on a XenApp server to free up server memory.None
Citrix WMI Service(CitrixWMIservice)ctxwmisvc.exeNT AUTHORITY\ Local Service ManualProvides the Citrix WMI classes for information and management purposes.Citrix Independent Management Architecture serviceCitrix Services Manager serviceIPsec Policy AgentRemote Procedure Call (RPC) TCP/IP Protocol DriverServerWindows Management Instrumentation Driver ExtensionsWorkstation
Citrix XML Service(CtxHttp)ctxxmlss.exeNetwork ServiceAutomaticServices XML data requests sent by XenApp componentsNone
Citrix XTE Server(CitrixXTEServer)XTE.exeNT AUTHORITY\ NetworkServiceManualServices network requests for session reliability and SSL from XenApp components.

Citrix Ports and Commands

License Manager Daemon27000Handles initial point of contact for license request.
Citrix Vendor Daemon7279Check-in/check-out of Citrix licenses
License Management Console8082Web-based administration console
Citrix Receiver80/443Communication with Merchandising Server
ICA1494Access to applications and virtual desktops
Session Reliability2598Access to applications and virtual desktops
IMA2512 Communication between Xenapp Servers.
Management Console2513Citrix Management Consoles
Application / Desktop Request 80/8080/443XML Service
STA80/8080/443 Secure Ticketing Authority (embedded into XML Service)
RDP3389To access the windows desktop remotely
SQL Server Port1433Used for Data Store.
Edgesight Server9035Communications to Edgesight Server

Citrix IMP Commands

  • Aiesetup Install or uninstall an application from an isolation environment.
  • altaddr Specify server alternate IP address.(Use altaddr to query and set the alternate (external) IP address for a server running Citrix XenApp. The alternate address is returned to clients that request it and is used to access a server that is behind a firewall.)
  • app Run application execution shell.(App is a script interpreter for secure application execution. Use App to read execution scripts that copy standardized .ini type files to user directories before starting an application, or to perform application-related cleanup after an application terminates.)
  • apputil Add servers to Configured Servers list for published applications.
  • auditlog Generate server logon/logoff reports.
  • chfarm Change the server farm membership of the server.
  • CTXKEYTOOL Use ctxkeytool to enable and disable the IMA encryption feature and generate, load, replace, enable, disable, or back up farm key files.
  • dscheck Validate the integrity of the server farm data store.
  • dsmaint Configure the server farm’s data store.
  • enablelb Enable load balancing for servers that fail health monitoring tests.
  • acrcfg – Configure Auto Client Reconnect settings
  • auditlog – allows you to get an audit for the user,time, failed and success logons in detail.
  • change – allows you to change logon or change port or change user.
  • ctxxmlss – used to configure citrix xml service port number(Default is 80).
  • icaport – change value of tcp/ip port for ica terminal sessions.(def is 1494. if u want to change it, use icaport cmd)
  • imaport – change ima port configuration utility
  • query – used to query farm, process,server, session,termserver and user.
  • 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
  • qwinsta- Display information about Remote Desktop Sessions. Default is current server. Displays users for current(or any given) server.
  • twconfig – configure ica settings for graphics performance.

dsmaint verifylhc [/autorepair] run this command atleast an year to verify LHC.

All the citrix ports and their usage is given at link:  Citrix Ports and Usage and Xenapp 6 Commands

Citrix Xenapp: Troubleshooting Slow Logons

In the world of Citrix Xenapp consulting, there is one call that you seem to get over and over again.  The client calls you and says that the farm you built for them last year is now taking 60+ seconds to launch a single application.  Everything was working fine for an extended period of time, but then something went wrong.  What could cause such an issue?

Winlogon Troubleshooting Steps

Before investing too much time in troubleshooting Citrix, be sure to log onto the Xenapp server via RDP to make sure that logons remain slow there as well.

If you want to know everything that is happening during the logon process, there are verbose logs that can be enabled.  In Server 2003, you can enable the USERENV logging by following the KB article: http://support.microsoft.com/kb/221833

If you are using Server 2008, then you can enable something similar following this process:


Let’s examine some of the usual suspects:

Networking Problems

In order to prove whether or not there are networking problems in an environment, you’ll need to use some networking tools.  Some admins like tools like Wireshark for tracing network communication so you can pick up dropped packets, etc.  Recently, I found a great tool for Citrix called SMCC, which can be installed on a trouble Xenapp server.  The tool will give you instant feedback on whether there are network problems impacting the server.  Read more about it here:


Roaming Profiles

Roaming profiles are public enemy number 1 in a Citrix environment.  While there have been countless articles written about why roaming profiles are no longer the best practice, we can never seem to get away from them.  They are especially popular in hospital environments where user customization is important, and this is the way they’ve always done it.  These profiles can often grow very large in size, and before the Citrix administrator knows it – he is dealing with profiles that are 200MB+ in size.  For this reason, when you get a slow Citrix logins call, the first place you should look would be at the profile size.  Beyond size you should also look at the location of your roaming profiles, because if there is a wan connectivity issue or any networking problems – it could also impact the speed at which the roaming profile is loaded.   Be aware that you can rule roaming profiles in or out quickly by creating a local account for testing purposes, with no reference to the roaming profile.

Windows Group Policy

When a virtualized application is launched through Citrix, it kicks off a huge stream of events.  Profiles are engaged, printers are mapped, and policies are applied.  Some companies have more complex GPO structure than others, so it’s important to keep it simple whenever possible.  In environments where a Citrix farm might have been “inherited” from previously staff that is no longer there, you will sometimes deal with clients who have no idea what their GPO’s are doing or how they are set up.  When you suspect GPO’s are the cause of slow application launch, you should isolate a single Citrix server into a fresh OU, and block inheritance completely.  Test logins again, and if they improve drastically – you know to focus your efforts on simplifying GPO’s in the environment.

Logon Scripts

Now that you can accomplish just about anything in Server 2008 via GPO, it’s logon scripts are something that should become a thing of the past shortly.  You will still see a lot of these in use in many environments today, so it’s important to know what they do and monitor them closely.  If a particular set of Citrix users is experiencing slow logons, it may be important to isolate what logon script is causing the issue.  You can test the logon script by running it line-by-line from the command prompt of the Xenapp server that you have isolated for testing.  If you find a particular line that hangs for an extended period of time, you’ll know to investigate more closely.

Drive Mappings

Drive mappings can work great for years, and suddenly stop working for many reasons.  Maybe a fileserver has a loose cable, or maybe there is a network problem.  The result can be a long delay during logon until the bad drive mapping times out.  Most of the time you will discover these bad drive mappings in a log on script, or perhaps a GPO.  Once again you can test by logging in with a user account that doesn’t have a log on script or GPO applied to it to see if the log in speed increases.

Printer Mappings

The volume of printers a user has may cause a slow login depending on how your Citrix policies are configured.  Best practice is usually to configure your printer mappings to load in the background during the logon process.  If you have a policy that says to do the opposite, you could be waiting a long time to see your virtualized application pop up.

Hotfix Level

There have been several hotfixes included in the various roll up packs for Xenapp and Presentation server over the years to address slow logons.  For this reason, it is best practice to always make sure you are on the most recent roll up package available from Citrix.  If you ever end up opening a case with Citrix support, you will find that this will be one of the first things they check for.

Slow Logins:

Complete Steps 1-3 with the same user account, in a load balanced environment. It might be necessary to log on to multiple Remote Desktop Servers to see if the issue is seen on one or more servers.

  1. Log on to the same server using Microsoft’s RDP client instead of the Citrix Receiver. Remote Desktop Server is Microsoft’s updated name for a Terminal Server.
  2. From a workstation on the LAN, log on to the Remote Desktop Server with an RDP or ICA desktop session.
  3. If applicable, from a workstation on the WAN, log on to the Remote Desktop Server with an RDP or ICA desktop session.
    Important! Steps 1 – 3 gives an idea whether or not the logon issue is strictly related to XenApp or is more likely a profile, logon script, network, or other user environment issue.
  4. For profile issues, remove any references to a profile path from the Remote Desktop User and/or user profile path within Active Directory users and computers, or Computer Management. Alternatively, create a local account directly on the Remote Desktop Server to ensure the profile is being loaded directly from the server. Retest the logon time.
    Note: New user accounts, accounts without a local profile, and anonymous accounts need to generate a local profile upon logon. The creation of the original profile might take time. It might be necessary to log on a second time when troubleshooting a profile issue. Are local copies of the user profiles being cached or deleted on logoff? As that can slow down logons if they are deleted on logoff using a Microsoft Policy due to the profile having to be rebuilt on the server each time the users logs in.
  5. Verify if Citrix User Profile Management (UPM) is being used to manage user profiles. If so try disabling the service on one server and retesting. (If this improves the issue, look over your Citrix UPM policies.There might be something in the configuration causing the issue. To enable UPM logging, see CTX126723 – How to Enable and Retrieve Profile Management Log Files).
  6. For logon script issues, remove any references to a logon script within Active Directory users and computers, Computer Management, or any sort of computer or group policy. Creating a local account directly on the Remote Desktop Server and testing might be worth the time. If a logon script is the issue, it might be necessary to REM (comment out) or input pause statements throughout each section of the logon script. This will help troubleshoot the resources in the logon script that are slowing down the logon process.
  7. For Network issues, such as Font Searching Might Cause Slow Logins on Remote Desktop Server are often difficult to find and troubleshoot. Network monitors or sniffers and other third party utilities such as Process Monitor fromwww.microsoft.com can be used for these issues. The issue described was resolved by the following:
    In some cases, the logon process on a Remote Desktop Server might be very slow because an application is searching for fonts. (Usually caused by older applications.)
    During the logon process, users can encounter a black screen for 1 to 20 minutes before the logon finally completes. The effect is magnified as the bandwidth is reduced; dial-in users experience the problem much more severely than LAN users.
    Network traces on such systems revealed that a process running on the Remote Desktop Server is searching for fonts by name during the logon process and not finding them. Completing the following steps to resolve:
    – In the system Control Panel, click the Environment tab.
    – In the system variables section, click the variable Path.
    – Add the following to the end of the string in the Value field at the bottom of the panel: ;%SystemRoot%\Fonts
    – Click Set. The changes take effect immediately.
  8. The issue might be related to the permissions on the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \MSLicensing registry key. For the Citrix Receiver to function properly, the user requires Full permission on this registry key.
    Some other symptoms <there is only one symptom> that are indicative of this issue are as follows: 
    – Local workstation administrator and power users are not affected
  9. Try disabling the XenApp virtual channels for 1 user using a XenApp policy (client drives, audio, printing, com ports, USB redirection). If this helps enable each channel to see which might be causing the issue and investigate. If printing, for example, try deleting the printers off the users workstation then logging in if that works add each of them back to see which is causing the issue might be there is an update driver from the vendor.
  10. If an antivirus product is running on the client device, disable it and retest the connection to the XenApp server.
  11. Check the session for a possible hung process. Try to terminate the hung process to see if then it speeds up the logon. If it is a third-party process check with the vendor of the process to further troubleshoot the issue.
  12. For published applications, investigate, within the Delivery Services Console, or Citrix AppCenter. Navigate to the Properties on the Application Printing section ensure Start this application without waiting for printers to be created has been selected as the default.
  13. If applicable, disable session reliability.


There are various causes of slow logons in Citrix environments.  Be methodical with your troubleshooting methods, and limit your troubleshooting to a single user account on a single server.  By experimenting with AD GPO’s and enabling/disabling logon scripts, you should be able to narrow down the root cause of the issue quickly.

Citrix Xenapp Admin Daily Activities:

  • Monitoring of Xenapp servers through Edgesight
  • If any aletrs are there look in to those
  • Will check tickets assign to our queue
  • priortise those and work on the tickets/Incidents
  • Prepare and Imlement RFC(Request for Change)
  • Shift Incharge or reporting any alerts in the Shift time
  • CAB Meetings and Emergency CAB Meeting
  • Installing ,Configuring Xenapp servers,Licences,Publishing of applications,Web Interfaces
  • Verify the Event viewer logs and Configuration logging database
  • Computer policies,User policies,GPO,Local security policies
  • Running Policy Modeling Wizard to know final resultant of policies on users and computers
  • Printing and Troubleshooting Printer issues
  • Edgesight Monitoring
  • Troubleshooting application issues and Performance issues
  • Troubleshooting Accessgateway and Netscaler issues
  • adding certificates to CAG if certificates expired
  • Verify Load evelauators and apply as per requirements
  • Patching ,Service packs and Antivirus
  • Implementing New POC Projects for Xenapp7.5 and 7.6
  • Updating Roolup patches on Xenapp server
  • Rebooting Xenapp servers on weekly basis
  • Backup of Datastore and Restore
  • Migration of Datastore from one database to another
  • Removing the Servers from Farm
  • Uninstall Xenapp servers
  • Hardware/Asset changes on Xenapp servers
  • Connecting to Servers through DRAC/ILO

PVS Roles:

  • Creating and Configurigng PVS Farm
  • Creating master target devices
  • Converstion in to vdisk using Imaging wizard,Xen Convert
  • Adding multiple target devices in collection
  • Configuring Writecache locations
  • Monitoring and Trobuleshooting PVS
  • Xenapp Vdisk conversion
  • Updating Vdisks
  • Creating Streamed catalogs from Xendesktop

Infrastruture for your Environment:

We need to tell following answers for Infrastruture

  • How many farms:2 -3
  • How Many Zones:2
  • How many Xenapp servers: 400 to 600
  • How Many Data Collecters:2
  • How Many  XML Brokers:2
  • How Many  BZDC,Xml Brokers:2
  • How Many  STA servers:2
  • How Many Wi,Licece servers:3
  • How Many  Applicatinons and Some examples:20-30
  • How many users and Concurrent users: 2000 to 4000
  • How many Citrix licences and RDS Licences: 2000
  • How many admins in shifts: 8 to 12
  • Xenapp is on Virtual servers or Physical servers: 40 virtual 60 physical
  • Zones Locations: Us and India
  • How many Esxi servers: 40 to 60
  • How many Vcenters: 2
  • How many pvs vdisk: 4
  • How many target devices using pvs: 800
  • How many Tickes you will handle perday:6 to 8
  • Which Hardware for ESX: Dell
  • Which Hardware for Xenapp servers
  • Thin Client Configuration
  • Antivirus
  • patching solutions in your environment
  • Backup Solutions in your Environment
  • SAN Storage Configuration
  • Which Ticeketing solutions

Vmware Roles and Responsibilities:

  • Installing and Configuring Vcenter,ESXI servers
  • Creating Vms based on user requirements
  • Adding Storage Luns
  • Configre Network
  • p2v,v2v converstions
  • Creating Templates and Snapshots
  • Host Proviles,Sysprep setting
  • Troubleshooting
  • Monitoring
  • Backup and Restore
  • Update manager


  • Creating and Configurigng Xendesktop site
  • Creating master target devices and VDA
  • Creating machine catalogs based on user requirements
  • Assigning those to the user groups in Desktop Groups
  • Adding more machines to catalog
  • Configuring Vcenter for Xendesktop
  • Troubleshooting Unregisterd issues
  • troubleshooting performance issues
  • Troubleshooting MCS and Desktops not delivering to users
  • Updating Pooled catalogs
  • Configuring WI/Storefront for xenapp and Xendesktops
  • Implementing POC on Xendesktop7.1 and Xenapp 7.5
  • Policies configuration for users and machines
  • Configuring HA by adding more controllers to Site

Infrastruture for your Environment:

  • How many farms:
  • How Many Zones
  • How many Xenapp servers
  • How Many Data Collecters
  • How Many  XML Brokers
  • How Many  BZDC,Xml Brokers
  • How Many  STA servers
  • How Many Wi,Licece servers
  • How Many  Applicatinons and Some examples
  • How many users and Concurrent users
  • How many Citrix licences and RDS Licences
  • How many admins in shifts
  • Xenapp is on Virtual servers or Physical servers
  • Zones Locations
  • How many Esxi servers
  • How many Vcenters
  • How many pvs vdisk
  • How many target devices using pvs
  • Which Catlaogs you have in XD
  • Desktops in Catalog
  • Pooled:
  • Dedicated
  • Streamed
  • Physical/Virtual
  • Configuration of VM in XD
  • TOTAL Storage and ESI confuration for XD
  • How many Tickes you will handle perday:
  • Which Hardware for ESX
  • Which Hardware for Xenapp servers
  • Thin Client Configuration
  • Antivirus
  • patching solutions in your environment
  • Backup Solutions in your Environment
  • SAN Storage Configuration
  • Which Ticeketing solutions

Patching of Xenapp servers:

Considerations Prior to Installation

Citrix recommends that you thoroughly evaluate hotfix rollup packs on a test server or farm. Ensure that you cover some testing comparable to the tasks of an everyday user, as well as some administrator oriented tasks.

Examine the readme that accompanies the hotfix rollup pack. Readmes provide necessary information on the prerequisites and known installation issues. 3. Because hotfix rollup packs are cumulative, there is no need to install earlier hotfix rollup packs. The latest hotfix rollup pack includes the fixes from all the previously released hotfix rollup packs for that product.

Order of Deployment:

The order of hotfix rollup pack deployment is very important, especially in large or complex farm configurations. Before installing a hotfix rollup pack:

Ensure that there are no existing connections on any servers

Ensure that the Independent Management Service is running

Back up the data store database.

After a deployment, always ensure that all servers in the farm are updated to the same hotfix rollup pack level.

Citrix recommends the following order of deployment:

  • Zone data collector
  • Backup zone data collectors
  • XML Brokers
  • Backup Xml Brokers
  • Session host servers

The hotfix rollup pack installs and updates only servers that have core XenApp (mps.msi) and/or XenApp Advanced Configuration (cmc.msi) installed.


Question:Printers are not auto-creating in one of the servers in the farm.

Troubleshooting Methodology

1.Policy configured: Client Printers – Auto Creation – Auto-create only the default printer of the client

2.Policy applied to all Domain users

3.Compared registry Settings for the Printer Policy on working and non-working server. Settings are identical (HKLM\Software\Citrix\Policies\session#\Printer)

4.Checked Event Viewer logs; Both Application and System logs were checked; No errors were logged on either logs

5.Restarted both the Print Spooler and the Citrix Print Manager Service; without any errors

6.Checked Terminal Services Configuration by right clicking ICA-TCP-Properties-Permissions; username ctx_cpsvcuser was missing on the non-working server.


The username ctx_cpsvcuser is required in order to properly auto-create printers in an ICA session. The absence of this account caused the faulty behavior.


Add the username ctx_cpsvcuser to the Permissions tab on the ICA-TCP listener.

Click Advanced > Edit under Special Permissions and grant access by checking the Allow check boxes for Query Information and Virtual Channels.

Restart the Print Spooler and the Citrix Print Manager Service.

Prior to XenApp 6, the Citrix Print Manager Service was configured with the ctx_cpsvcuser local account. This account was created during the installation of XenApp and contained the minimum permissions required to successfully handle autocreation and other printer-related tasks. In XenApp 6, this service is now started with the built-in Local Service account. This change is designed to help prevent problems where Group Policy Objects (GPOs) are in place to lockdown the local accounts (which affects ctx_cpsvcuser and causes printing problems).

For many years, printing has been the bane of the Citrix tech’s existence.  You work hard to put together a successful Citrix farm, carefully virtualizing applications and meeting user needs – but everything goes to pieces when the users try to print.  Citrix printing issues can usually be categorized into one of four categories:  Citrix issues, Print Driver Issues, Universal Print Driver Issues, or Application problems. Let’s take a look at a few common printer related trouble calls that a Citrix tech may receive:

How should printers be deployed in the environment?

In the old days, you would commonly deploy printers through a complex login script if you did anything at all.  Keep in mind that deploying printers with a login script can cause slow logins – See my other blog: http://citrixtechs.com/blog/?p=42

In many offices, users are responsible for mapping their own printers.  In today’s world through the magic of Microsoft GPO, printers can be deployed to a non-technical user base with relative ease.  Use the following article to guide you with such GPO based printer deployments:

  • Make sure to utilize the Citrix stress printers tool in your test/dev environment so that you can test print drivers before putting them into your production farm.
  • Problems with the print spooler?
  • Citrix techs usually spend some of their time wrestling with the print spooler.  The print spooler on a Citrix server may hang, stop responding, or gobble the entire CPU of a server in certain scenarios.  If you find that your print spooler is hung, the first thing you may try is to restart it through the services console.  If the print spooler refuses to restart, or it is gobbling 100% of the cpu in task manager – you may have a specific rogue printer drive that is causing the issue.  You’ll need to open the printers folder and see if there is a driver with stuck jobs on it.  If you find this, delete the driver from the server and watch as the CPU returns to normal in the task manager.

  • Problems with the Citrix printing account?
  • The Citrix printing account can occasionally go corrupt, or be missing key permissions needed for it to function properly.  If you suspect problems with this account, try switching the service from using this account to the local account to see if issues resolve.  If problems go away, then you’ll need to use the Citrix account recreation tool (CTX113554) to rebuild the account, and follow CTX113555 to make sure that the permissions are assigned correctly.
  • How are my Citrix print policies configured?
  • Remember that all aspects of printing can be controlled through Citrix print policies.  Until the latest version of Citrix, the Universal Print Driver (UPD) is available for client connected printers only.  Depending on how you configure the Citrix print policies, your users may or may not be allowed to use the UPD, or to use native drivers. If you’ve excluded certain drivers from your farm after using the Citrix stress printers tool, you can use Citrix print policies to prohibit specific rogue drivers that you know to be a problem on your farm.
  • My Citrix print policies are not being applied!
  • In most cases where this is reported, Citrix print policies are applied – but then they are taken away by some other rogue GPO or policy in the environment.  As with all GPO troubleshooting, the best way to troubleshoot this is to place a test server in it’s own OU and block all inheritance. Log in with a test user account, and verify that you can get the policy to work properly when other Microsoft GPO’s are completely out of the mix.  Once you’ve proven this, then start adding back one GPO at a time until you find the troublemaker.
  • Can Roaming Profiles be causing printing issues for users?
  • Absolutely!  There have been many cases recorded where Citrix techs had to delete and recreate user roaming profiles to solve printer auto-creation issues.  I’ve witnessed some cases where users were not getting their default printer assigned correctly according to policy, etc.
  • Problems with certain versions of the ICA Client?
  • There are many documented issues with older versions of the ICA client.  If you suspect a client issue, upgrade to a newer version of the client and see if the issue resolves.
  • Hot Fix and Patch level?
  • Every roll up pack for Citrix has contained multiple fixes involving printer and auto-creation of print drivers, etc.  For this reason, I generally recommend that you always make sure your farm is operating on the most recent hot fix roll-up package from Citrix.
  • Problems with the version of printer drivers on print servers?
  • You may need to experiment with different versions of print drivers to troubleshoot certain issues.  There have been documented issues with some PCL drivers, Ricoh drivers, etc – where certain versions did not work with Citrix, but when upgraded issues were resolved.  Also be aware that some print manufacturers may require that you be running a certain level of .NET framework in order for their drivers to function completely.
  • Is the printing problem application specific?
  • Someone may submit a ticket that they can’t print over Citrix via the Great Plains application.  The first thing you should do is have them try to print from Notepad or any other application.  If the printing issue only occurs through a specific application, work with the application vendor to trace the issue.  It could be that their application depends on a certain version of .NET framework or some other server side requirement in order for printing to function properly.  If you want to rule Citrix out completely, log in via RDP to the desktop of the terminal server in question and launch the problem application.  Try printing via RDP, and if the same issue occurs there – Citrix can be ruled out of the equation.
  • CPViewer.exe is gobbling resources and freezing my servers?
  • This is a known issue with Citrix printing when you are using applications that start many small print jobs.  This is common with check printing applications, or other apps that might send 100+ small print jobs to the queue at any given time.  The resolution is to employ a registry change (Mentioned in CTX114755) that stops this behavior.
  • Are there print related errors in the event viewer?
  • Most terminal servers and Citrix servers will have a certain amount of printer related errors in the event viewer.  You can determine if you are looking at relevant errors by the printer name that is specified in the error message and the time/date stamp.  Event viewer errors may be able to tell you if certain users are not able to get their printers when they log on, or if some printers are hung or having difficulty printing.
  • Should I use the Citrix Universal Print Driver?
  • The Citrix UPD has been a great invention that has gotten better with each revision of Citrix.  By using the UPD a savvy Citrix Tech can make sure he isn’t loading his servers up with a bunch of unnecessary print drivers.  Anybody who has run a Citrix farm for a period of time knows the dangers of allowing their clients to connect from home and print to their client attached printers.  While you may have carefully screened the printers you allow on your network in the office, the printers people have on their desks at home can pose a danger to your terminal servers.  If these drivers are allowed to load individually, they can interfere with or cause corruption with other drivers on the server.  By utilizing the UPD, a Citrix administrator can cut down on print driver headaches dramatically.  The only caveat is that some advanced printer functionality may be lost if the printers perform activities like stapling, collating, etc – so test UPD compatibility if you have important client printers in the environment.
  • Third Party Citrix print software?
  • Later versions of Citrix Xenapp seem to have dramatically fewer print problems than versions of the past.  I’d say that anyone running Xenapp 6 or newer will probably be ok utilizing the built in features for Citrix printing.  If you are running a version of Citrix older that Xenapp 6, you might want to consider using a 3rd party print software package like Tricerat Screwdrivers.  Screwdrivers allows you to completely turn off Citrix printing features from within Xenapp or Presentation Server, and rely completely on the third party tool for all printing activities.  While expensive to some companies, my experience has shown that companies with a lot of printer problems should at least consider using a third party tool like this to take some of the workload off of their Citrix administrators.

Question:Qfarm /load is showing 1000 without load:

The server shows a QFARM /LOAD of 10000 or an invalid load, even if no users or sessions of any kind are active on the server.

This issue is very common if the server has issues with the PerfMon counters. Open the performance monitor console, and run a performance counter test. If the server has errors with the counters, usually the counter list is empty and you are not able to run the test.

The load balance concept of XenApp depends on the use of Windows Performance Monitor counters to run the test and receive the correct statistics. If this is damaged or not installed correctly, XenApp is not able to get a correct read forcing a load of 10000 because the tests are failing.


 Rebuild the PerfMon counters.

To rebuild the counters in a Windows 2003 server,

goto http://support.microsoft.com/kb/300956.

To rebuild the counters in a Windows 2008 server, run lodctr.exe /r.


1. Please check the Load Evaluator assigned to the server. It shouldn’t be on Maintenance Mode.

2. If it’s not on maintenance, then find the rules of the load evaluator, which has been assigned to the particular server and check if the server is reaching its Threshold limit and if it is, then find in case anyway is there to reduce the load below Threshold.

e.g.- The server is having load evaluator set with respect to “CPU utilization” & “Memory utilization”, then check the Threshold value and check whether the CPU & memoty are being utilised until that value.

8. If still not resolved, then please check the below Registry Keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

And confirm that the following value does not exist:
disable performance counters = 1

If it is there, then change the value to 0 or delete the value altogether. No reboot is required for the changes to take effect.

9. Stop the Windows Management Instrumentation (WMI) Service and run the following command:

winmgmt /salvagerepository

winmgmt /resetrepository

And restart the XenApp Server. Please start the WMI service after reboot and check the load now.

10. If still not resolved, then Stop “Citrix WMI Service” & “Performance Logs & Alerts” service

a) Go to “C:\Windows\System32\”

b) Rename the files “perfc009.dat” & “perfh009.dat” to _OLD

c) Copy “perfc009.dat” & “perfh009.dat” from a working Citrix w2K8 R2 server to the same location.

d) Reboot the server

e) Once the server is rebooted, Start “Citrix WMI Service” & “Performance Logs & Alerts” service.

This should resolve the issue.

ICA Listerner:

Although the remote desktop session host configuration tool includes the listener configurations for both ICA and RDP, settings for ICA must be configured using the ICA listener configuration tool included with XenApp.
The ICA listener configuration tool is located at Start All Programs Citrix Administration Tools > ICA Listener 

 The only available options on the listener configuration tools are the following.

  • Disconnected Session Timeouts
  • Active Session Limit Timeouts
  • ICA Connection Limits per Network Adapter
  • Environment Options

In addition to these settings, the client must use Citrix Policies to apply other desired settings.

Real Time issues:

1.Full Desktop Launched Instead of the Published Application

In a Citrix XenApp 6 environment, publish for example notepad.exe within the Citrix Delivery Services Console. When launching this application also a full desktop is started.

Sometimes when you create a new domain user without defining the ‘Terminal Services Profile’ path, this user is able to launch the published application correctly.

A few solutions can be found at Citrix and Microsoft blogs and knowledge bases.
A summary:

  •       Microsoft hotfix: http://support.microsoft.com/kb/969851
    Instead of the specified startup program, the whole desktop is started on a remote desktop connection when you change the “Terminal Services Profile” setting for the user account
  • Connecting to a Published Application Produces the Entire Desktop: http://support.citrix.com/article/ctx644401
  • Environment / Initial Program is checked but is empty (User account property or ICA/RDP protocol property)
  • Windows 2003 domain user is changed within a Windows 2008 AD Users & Computers console. The User Object attribute “UserParameters” becomes corrupted.

2.XenApp AppCenter Console Displays Application Status – Application not running

Symptoms or Error

A user closes a published application, but the session remains active, and the AppCenter console displays application status “Application not running”:

User-added image


The “Application State” column was added to AppCenter in XenApp 6.5 to support the Session Lingering and Session Pre-Launch features.

  1. If the correct process is closed, the ICA session should end.

Once the process has been identified, the LogOffCheckSysModules registry key can be amended to ensure this process is closed automatically by XenApp when the published application is closed.

3.An Active Session Exists Even after Logging off the Session when Symantec Endpoint Protection is Installed on a Citrix XenApp Server


An active session might still exist even after logging off the session when Symantec Endpoint Protection is installed on the Citrix XenApp Server.

Note: The issue was observed when a user starts a published application in the seamless mode. Additionally, multiple Symantec Endpoint Protection (SEP) system tray icons are displayed on Terminal Server Client for each connection made to a Citrix XenApp Server.


The session was left in active state if the SmcGui.exe application did not terminate properly after the user logs off gracefully. This might be due to the Seamless Desktop Integration feature of Citrix, where resources running on a Terminal Server might be made to appear as if the resources are running on the client.

4.Graceful Logoff from a Published Application Renders the Session in Active State

Graceful logoffs from a published application launched in a seamless, fixed window, or as an RDP Initial Program, might result in the session not closing and the user being logged off. Sessions can be reset or exited correctly by manually resetting them, or by terminating remnant user processes in Terminal Services Administration, the Management Console, or Access Suite Console

First, determine if the application in question and its associated processes correctly exit on a windows workstation outside of a Terminal Services environment.
If they do not, then it is possible that this mechanism might not work or it might be necessary to contact the application manufacturer.

Add the process file name to the following registry key:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Value Name:LogoffCheckSysModules


  • Do not place the executable name of the main published application in this key because this might result in failure to properly launch the published application. There is an issue if the main executable for the specified published application is not terminating correctly.

When publishing an application, only the main executable file is specified. However, some applications might spawn additional processes that run in the background and are not closed by the corresponding main executable file. Additional processes might also be created, from scripts that are executed, or from specific registry keys, such as the RunOnceKey:

Some processes might create a visible window for added functionality, and others might not.

Because the Explorer.exe Desktop is not running when launching an application in one of these ways, there is no default mechanism in either Presentation Server or Windows to terminate these background processes when a user has exited the main application.

 5)I have a policy which creates a (session ) printer for a user. It works fine.
I then remove the user from that policy. Now, since the user is not in the policy any more I would expect the printer not to appear but it still does when the user logs in.
Why is the session printer still appearing when the user logs in even thought they are not in the policy for it?
Its not a ‘show stopper’ but it gets very confusing when you have loads of different printing scenarios with different locations and user devices , as I do.


After a user get all their applications enumerated in IE (via web site), and then click on multiple published applications to launch the applications they get this error:

“The task you are trying to do can’t be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on”

And the second application will not open. The first application that was selected opens OK.

It’s OK, if you click on multiple published applications after you already have at least one application already open in citrix

Environment: XenApp 6.5 on Win 2008 R2 64bit with SP1

Anyone had this issue in their xenapp environment and possible resolution?


install hotfix 7 (XA650W2K8R2X64007) then add this reg key:

Name: LogoffCheckerStartupDelayInSeconds 
Data: <An integer for the length of time to wait for application start. – Enter the delay time in seconds, up to 10 minutes (600 seconds)


Some of my users got a strange problem from time to time… sometimes they can’t click anymore in an published app (regardless of the app) but keyboard regular input and shortcuts still work (ALT+F4, TAB, ALT+TAB, etc.).

The mouse pointer can be moved… but clicks (left or right doesn’t matter) aren’t recognized.

My environment: XenApp 6.5 HRP1 with installed Hotfixes (002, 007, 011, 013, 028, 033, 053, 058), Windows Server 2008 R2 (latest Updates installed).

Any suggestions?


Our first problem consists of the wrong shown IP for some of our clients. This was caused by our proxy settings. The old squid server in our environment has worked fine with the old presentation server 4.5 environment… but not with the new XenApp 6.5. After disabling the proxy settings the IP shows up with the real endpoint IP.

The next problem was caused by the self-service plugin exe which was automatically installed with the latest receiver. I avoid this by deinstalling the receiver an reinstall it with the use of a batch file and called the setup routine like this:

CitrixReceiverWeb.exe ADDLOCAL=ReceiverInside,ICA_Client,USB,DesktopViewer,Flash,Vd3d /silent

After this our mouse problem is gone…

    or Try below 

We experience this issue since January 2014 more and more (XA6.0, XA6.5, Win2008R2@XenServer). So we got in touch with Citrix and Microsoft. Microsoft finally provided this:

Change SNP features on client machine:

netsh int tcp set global chimney=disabled

netsh int tcp set global rss=disabled

netsh int ip set global taskoffload=disabled

netsh int tcp set global autotuninglevel=disabled

netsh int tcp set global congestionprovider=none

netsh int tcp set global ecncapability=disabled

netsh int tcp set global timestamps=disabled

Change CGP settings on client machine. (Usually there’s no value in CGPAddress. We set if the key was existing.)

HKLM\SOFTWARE\Policies\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Network\CGP\CGPAddress: “”

HKLM\SOFTWARE\Wow6432Node\Policies\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Network\CGP\CGPAddress: “”

Last but not least set this option on Terminal server:

netsh interface tcp set global autotuninglevel=highlyrestricted

On client and server, the network adapter must be rebooted after these changes. Or reboot the system;-)

Before I had that mousepointer problem as well (0-3 times a day). After applying these changes the issues were gone.

It would be great if you could share your experience with this workaround. For us it’s not a real solution but at least users with heavy impact (5-8 times a day) can work again. We will get back to Microsoft for further debugging.


I cannot seem to launch any published applications. 

I get this error: “This version of Citrix Receiver does not support selected encryption. Please contact your administrator.[Error 1046: The Virtual Driver is not loaded]

I’m running the latest Citrix Receiver 3.4 Enterprise. I see other that have this problem that have uninstalled and reinstalled receiver and it fixed the issue and also some hotfix that may be available if you open a support ticket?

Is there any other way to fix this error? It was working fine yesterday… so this came out of no where. No windows updates were done and no updates to Citrix were done recently


Edit this value:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ICA 3.0]

“VirtualDriverEx”=”HDX RealTime Media Engine, SOCKSProxyPlugin, UDPGatewayPlugin”

 Remove the UDPGatewayPlugin entry.

I only had this issue through the Netscaler. VPN and LAN clients never had a problem. It seems to me that this Plugin should be smarter and give up if the ports are not open.  I am still testing a Citrix Policy approach that would not mess with the clients LAN based connections.


I am running XenApp 6.5 our users log onto a published server desktop and them run streamed apps.

A couple of times a month one of server will stop allowing users from opening new applications, they just get an egg timer and nothing else. and I am unable to open task manager or process explorer. I end up having to restart the server.

In the system event log I a load of messages such as the below;

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.

The only thing I have found is this;


Is anyone else having a similar thing?



Server hangs in my environment possibly caused by our Antivirus product (CA eTrust 8.1). The specific scenario for my server hang is:

– User session connected via CSG 3.3.1
– Data (XLS,DOC, PDF etc) accessed in session via mapped client drive.
– Users instance of wfshell.exe hangs (runinng at 100% cpu time).
– On the server numerous system 7011 (NlaSvc, RSCorSvc) events are logged before server wide hang occurs.

If our anitvirus softwares realtime monitoring service is stopped early enough server spings back to life, same for if session with out of control wfshell.exe running is disconnected and logged off.

– Current workaround in place is for exlusion on wfshell.exe from being monitored.
– Edgesight alerts configured to provide advance warning for when wfshell.exe consumes > 3% CPU, and when 7011 events are generated (get a few red herrings throughout the day unfortunately for the NlaSvc).

10) We are seeing problem with WMI service on some xenapp 6.5 (Rollup pack 1) servers in our environment. WMI service is crashing frequently, upon checking in the event viewer found common event id 7036 which is not pointing anything. Can anyone help me to troubleshoot the issue?


Please update your farm with latest rollup pack and see the difference.



You could try re-creating performance counters and then restarting the WMI service, to see if that helped.

cd c:\windows\sysWOW64

lodctr /R


Error while installing Rollup pack 4 on Xenapp 6.5

We found the solution, turned out someone had been testing a GPO and removed the access rights for system under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments

After we gave the correct rights the install went through

Question: XenApp Qfarm Load reports 10000 when using VMtools

On installing XenApp and joining the farm, sessions cannot be completed with the error “An error occurred while making the requested connection”. Running Qfarm /Load on the affected server reports 10000. Indicating the server is full.

On removing VMware tools the server is able to service requests and the load is 0.


There a few articles on resolving this, these articles refer to Perfmon Corruptions, Lack of a worker group, and installing VMWare tools with the Volume shadow copy unchecked. I attempted all of these and nothing resolved the issue.
As VMware tools is required as best practice I couldn’t simply leave them off.

After much investigation I found that the esx hosts had been configured without an NTP time source. Configuring this option allows the WMI framework to correctly enumerate system resources and the load issue is resolved.

13) Health Monitor and Recovery action failing with xenapp 6.5 rollup 3:

SOLVED.  Opened a case with Citrix on this issue.  They were able to repro and determined that this is a bug introduced with Rollup 3 AND rollup 4.  After RU3 or RU4 are installed, healthmon is looking for newer versions of certain DLL’s, even though these DLL’s aren’t actually updated by the rollups.  Citrix provided me with updated DLL’s and I have confirmed it fixes this issue.  The following DLL’s need to be replaced with the newer versions:




They all live here:  Program Files (x86)\Citrix\Healthmon


Application could not be published in folder

I had the same problem. Everytime I tryied to publish ONE application I got an error. After some testing with renaming the application.exe, publishing in different folders etc I found out, that the icon was responsible for this error. So I published the app and choose another icon and it worked…


There is a request to load balance a Citrix published application in XA 6.5 across 2 servers.

But all users need to go always to one server. Only in case the first is not responding/available, the second one must be used.

How can this configued on XA 6.5 ?

Solutions: Use Load Banancing Policies worker group priorities


I have 3 Server Farm with Windows 2008 R2 Server and Citrix XenApp 6.5 installed.
it was everything fine and we were at rooling out in production Environment.
But now ther ist a very big Problem with the user Policy Editor in Xen AppCenter Policy are all of the policies disappeared. My second Admin has meant he has edit the policies from an other Server an than they were away!!!
I need help how can i restore the common policy back again or how can i repair this?
If i start the XenApp Center and go in to the Policy editor und press F5 i become error with ,Net Frame. I attache a picture of that.
If i try to create a new policy there is an other error like this

System.Runtime.InteropServices.COMException (0x80004005): Beim Aufruf einer COM-Komponente wurde ein HRESULT E_FAIL-Fehler zurückgegeben.
bei ScriptingLib.IGPFDocument.set_Namespace(String pVal)
bei Citrix.GroupPolicy.DataModel.Scope.Save()
bei Citrix.GroupPolicy.Gui.ViewModel.PolicyEditorViewModel.<CreatePolicy>b__58(Object s, DoWorkEventArgs e)
bei Citrix.GroupPolicy.Gui.TaskProcessor.OnDoWork(DoWorkEventArgs e)
bei Citrix.GroupPolicy.Gui.TaskProcessor.<RunWorkerAsync>b__4(Object s, DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)


If, for some reason, you are no longer able to restore the database, (in our case it was a Test-Farm and we didn`t know the date/time when the policies disappeared) you can run the following command on the SQL-Database to at least be able to create user policies again:

(obviously backup your database first) 

1.Shutdown all SessionHosts of the Farm

2.On the Datacollector, stop the IMA-Service

3.Run the following command on the IMA-Database:

delete from keytable where cast(rdn as nvarchar) = ‘FarmGpoBuffer’ and parentid in (select nodeid from keytable where cast(rdn as nvarchar) = ‘FarmGpoBuffer’)

(2 rows should be affected)

4.Execute dsmaint recreatelhc on the Datacollector

5.Start the IMA Service on the Datacollector

6.Start the SessionHosts

You should now see an empty unfiltered policy in the user tab. 

Again: The Command will not restore the user policies but at least you will be able to create policies again.. 

BTW: I was able to reproduce the issue on another Test-Farm and it usually happened when the appcenter had high memory consumption when I was creating several policies from policy-templates.

Seems like there is a private hotfix for it: http://support.citrix.com/article/CTX140488 but I have not been able to test it myself if it fixes the issue.


I have seen this several times now. If the policy is visible on some servers but not others then it’s because software is missing on the other servers. If the policy is missing on all servers then it’s probably datastore corruption and the database needs to be restored. You should probably open a support case.

Here is the latest software, some of which might require a Partner or Support to download.

LIMITED RELEASE – Hotfix GPMx170WX64006 – For Group Policy Management Console for Windows x64 – English

From <http://support.citrix.com/article/CTX139312>

LIMITED RELEASE – Hotfix GPCSExt170W2K8R2X64001- For Group Policy Client side Extension – English

 From <http://support.citrix.com/article/CTX136427>

Hotfix DSCXAMx650W006 – For Citrix XenApp 6.5 AppCenter – English

 From <http://support.citrix.com/article/CTX137747


There is no Citrix XenApp server configured on the specified address.

When the user clicks on an icon, Web interface or StoreFront looks up the private IP address of the least busy XenApp server and instructs Receiver to connect to the destination XenApp server’s private IP using the ICA protocol. The ICA protocol uses TCP 1494 and TCP 2598.

If you are using NAT then you have a couple options:

  • If Web Interface, right-click the site, click Secure Access, add a line for the network and select Translated or Alternate. If Alternate, go to each XenApp server and run ALTADDR to set the NAT’d IP. Without Secure Gateway or NetScaler Gateway you’d need a NAT’d IP for each XenApp server.
  • If StoreFront, you would need to deploy a NetScaler Gateway appliance to proxy the ICA traffic through one NAT’d IP address.

18)For Desktop Studio on XenDesktop 5.0:

The following might also be required:
Locate the Desktop Studio folder on the system:
C:\Program Files\Citrix\Desktop Studio\ (32-bit machines and 64-bit machines with 64-bit Desktop Studio)
C:\Program Files (x86)\Desktop Studio\ (64-bit machines with 32-bit Desktop Studio)
Note: Verify that the LaunchConsole.exe file is present in this folder

  1. Create a file in the \Desktop Studio\ folder named LaunchConsole.exe.config.
  2. Place the following text inside the file and save it:
  3. <?xml version=”1.0″ encoding=”utf-8″?>
  4. <configuration>
  5. <runtime>
  6. <generatePublisherEvidence enabled=”false” />
  7. </runtime>


  1. Restart the Desktop Studio Console. This must be much faster because the system does not attempt to verify the Authenticode signature.


I need to get a report of all virtual desktops in our environment, and the user assigned to each.  These are dedicated desktops. 
Can someone point me in the right direction?  I think I’ll need to use powershell, as I don’t see an option in Desktop Studio or Desktop Director.

 Get-BrokerDesktop -maxrecordcount 5000 -adminaddress <DDC server name> | where {$_.DesktopGroupName -eq “<delivery group name>”} | Select-Object HostedMachineName, AssociatedUserNames,AssociatedUserFullNames

20)Booting to PVS vDisk without PXE or DHCP Options

Instead of the DHCP boot options, run BDM.exe (in your PVS install directory). This will allow you to create a .iso that you can mount as cdrom image that will point to your pvs servers.

Here are the directions for a ESX backend.

Here are the directions for a XenServer backend:

18) HA for PVS Servers:

For High availability purpose, I am planning to use shared LUN concept for storing PVS vDisks and cache files (Difference disk mode). I created required LUN on NetApp filer and it is ready to mount.

-How do I create a shared LUN on two PVS servers?
-How does PVS know when to take over the LUN?
-If two PVS servers are in HA mode and if one of the PVS is down, does target devices freeze or they will failover to another PVS with out any interruption?


-How do I create a shared LUN on two PVS servers?

You have already configured your LUN, zoning, etc..
Then you can access the LUN over two ways:

– CIFS access, if your NetApp does support that protocol
You can create your vDisk store and point it to e.g. \\netapp\vdisks

– SAN access, both servers can see the LUN as a disk device, but you need to buy a SAN filesystem. Advantages: less protocol overhead than CIFS, but maybe more expensive

>> -How does PVS know when to take over the LUN?
There is no integrated active/passive mode, both PVS servers “see” the LUN all the time.

>> -If two PVS servers are in HA mode and if one of the PVS is down, does target devices freeze or they will failover to another PVS with out any interruption?
The target devices will fail over to the working PVS server if your vDisk is configured for HA and both PVS servers are able to access the vDisk store. Maybe there is a short interruption while the failover happens (one “ping” in my latest POC). But you can also tune the failover parameters.

21) Black or Blue Screen When Connecting to Published Desktop

Connecting to a published desktop on a computer that is running Windows 7 or Windows Server 2008 R2, is not successful. A black or blue screen is displayed.


Add or set the following registry key on the XenApp server(s) to resolve the issue:
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Logon
Name: DisableStatus
Value: 00000001

Problem Cause

There are several that could have caused the issue.
A majority of them are related to drive mappings or folder redirections in logon scripts, user profiles and/or GPOs, which point to an incorrect location or experience delays mapping during the logon process.

22) Xenapp Can’t Take a Picture With a Webcam

I am having issues taking a picture with webcam in XenApp 6 ICA session, both published desktop and published app. We get an error (may be an error from the app) that reads “Failed to acquire image from device”. All the HDX/Multimedia policies look fine, as they are all enabled by default (unless i’m missing something). I’ve gone through CTX124655, but it did not help. I have also tried installing Desktop Experience, still no joy. I have tried a couple different webcams as well, but I’m at a loss at this point.


We resolved this issue. When a picture is captured it is trying to save the file on the root of the C drive. I don’t know if that’s a feature of Citrix, or the app Centricity that is capturing the picture. We ended up having to grant modify permissions to files on the root of the C drive to Authenticated Users. Once we did that, all was happy.

It was actually the root of C: we set the permissions on. The permissions we set (straight from my documentation), these are “special permissions”:
Allow the following permissions on the root of C:\ for Authenticated Users, apply to This folder and files, and check the Apply these permissions to objects and/or containers within this container only
a. Create files / write data
b. Create folders / append data
c. Write attributes
d. Write extended attributes

I found that the root of C: was the location causing the issue by using procmon, and found an access denied event.

Call us for Free Demo on AWS,Vmware,Citrix,Azure,Devops,Python,Realtime Projects
Calls will be forwarded to Our Trainers for demo

Leave a Reply

Your email address will not be published. Required fields are marked *