Link to home
Start Free TrialLog in
Avatar of Mase2k
Mase2kFlag for United States of America

asked on

Slow performing Citrix XenApp in Windows XP

I have been struggling with this issue quite a bit recently. We are running Citrix 6.5 XenApp with Receiver 4.0. Any Windows 7 or newer operating systems run all published apps just fine. On our systems running Windows XP they run all apps fine with the exception of our software which we develop in house. It is developed in Java and is executed using a Batch file. When running this app ONLY ON WINDOWS XP we get very slow screen draw issues. For example the login window will draw a square and then fill in with the actual window after a few seconds. Then any window we open draws similarly with the surrounding window first drawing and then the contents of the window filling in after a few seconds. Just wanted to check and see if anyone had any recommendations on this.
Avatar of Tony J
Tony J
Flag of United Kingdom of Great Britain and Northern Ireland image

Ensure you're using the latest client / receiver compatible with XP.

Are the video cards a much lower spec thean the Win 7 machines? Indeed are the machines themselves very much a lower spec? Whilst it is true that 100% of code in XenApp is executed on the server, it still leverages some components of the client such as the graphics card.

If you lower the colour depth slightly for XP clients, does it have any impact?

You may wish to review these settings: http://support.citrix.com/article/CTX136671

There is also a HDX monitor: http://support.citrix.com/article/CTX126491

On the face of it, it sounds like the XP desktops are underpowered, graphically.
ASKER CERTIFIED SOLUTION
Avatar of Mase2k
Mase2k
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
How very odd. Glad you sorted it out and thanks for feeding back what cured it for you.
Avatar of Mase2k

ASKER

Once we discovered the issue was related to seamless delivery of the App we resolved it by executing the app in a windowed environment.