Wallpaper choice and the difference it makes to your citrix environment
Graphically “busy” wallpapers can degrade the user experience when users are working with windows in a published desktop setting. This can manifest itself as mouse latency, start menu latency, and lag when launching, minimizing, maximizing, and moving windows. The more “photographic” the wallpaper and the more latent the user’s network connection, the worse the issue will become. Consider the follow two example wallpapers:
The wallpaper on the left is more complex than the one on the right – prettier but that has a cost. Many fine lines and fast color changes (steep gradients) mean that, all things being equal, the user using the wallpaper design on the left will have a degraded experience compared to the one using the wallpaper on the right. The intensity of the performance impact is reliant on their network connection and, to a smaller extent, the versions of XenApp and the Citrix Receiver being used (newer versions will tend to be faster than older ones for both products).
The issue arises due to the way the receiver breaks down the screen images into glyphs to send to the endpoint. While many GUI elements are directly passed through, window edges and graphics, such as the background, are broken down and compressed before being sent to the endpoint device. The simpler the blocks the faster and smaller they can be compressed and send to the user to be rendered.
All things being equal best to “go bland” and stick to a solid color background, your users’ will thank you for it in the long run – oh and restrict letting them changing it via GPO!
Common enough one on the VMware forums this but worth regurgitating as often the database is felt to blame for slowdowns,
Recently saw a query for this up on the citrix discussions and one I was interested in seeing what was required.
Main motivation for me was purely selfish ones, being an admin in a few farms meant over time i’d added myself to a lot of published apps/desktops I didn’t need day-to-day access to so was keen to clean up my desktop which had come a mess from all published apps I had assigned to me.
So a couple of powershell cmdlets help out big time in this regard
1) First to verify the list of apps he/she has assigned run the following:
2) Then to remove from an individual app
Remove-XAApplicationAccount -BrowserName “APPNAME” -Accounts “DOMAIN\USERNAME“
3) To remove from all
Remove-XAApplicationAccount -BrowserName * -Accounts “DOMAIN\USERNAME“
Shout out to Khalid Aldrouby for this tip
Recently as part of a windows 2003 decommission cycle internally was charged with looking at retiring all pre xenapp 6.x farms in the environment.
As part of this obviously a migration strategy for the applications from running in windows 2003 to windows 2008 r2 was part and parcel and to a great extent was able to achieve that, so much so we had one application left running that had an IE6 tie-in which currently working on.
To that end this application was running off a PVS image and all the associated infrastructure that come with it and the farm it was felt much more efficient to retire the farm and publish the application out as a remoteApp application while the issue with IE10/11 compatibility is resolved(which is 90% there at time of writing).
To that end still have 2003 servers for the application but at least enabled us to retire:
I) Farm XML brokers
ii) Farm ZDC’s
iii) Old PVS farm supporting the aforementioned application image
iv) Associated databases
v) Hypervisor hosts running the above
Associated link helped in achieving above
While back seen this issue and never documented workaround (not documented fix with the existing version of the agent, shortly moving to later release). The real and crucial takeaway is to verify from the Move server end before rebooting target devices as it will be a lot quicker troubleshooting that end first.
MOVE AV client error -Event ID-2
Have seen some recent instances on the citrix discussion groups regards issues encountered by administrators using virtual netscaler appliances.
In area to particular to keep an eye on is /var, this area will show most volatility in terms of growth due to the nature of what is stored in it in particular by and nearly entirely, log files. Log rotation will be in place for some logs but not all so keep trimming.
More details on how to remove files in the directory: