One of the most challenging tasks for a Citrix administrator is when a user calls in complaining of a Citrix problem: logon is slow, session is getting disconnected, application launch is slow, session itself is slow, etc. So, how does a Citrix admin go about solving these issues? A Citrix infrastructure has many tiers and dependencies. Where do you start looking, what do you analyze, and how do you triage?
Watch this webinar by George Spiers, Citrix CTP and EUC Architect, who shares his real-world experience to help you learn the art of Citrix troubleshooting. You will find out how to:
• Methodically go about finding the scope, magnitude of impact, and source of the problem
• Troubleshoot common Citrix problems like slow logons, slow app/desktop launch, disconnecting sessions, frozen sessions, etc.
• Investigate issues in the supporting infrastructure (network, AD, virtualization, etc.)
• Optimize the Citrix environment for maximum performance
At the end, we discuss how automated monitoring can help accelerate performance troubleshooting.
What is WEM and why is it different? Discuss how before you have Group Policies applying as a user logs on. Now you have WEM doing the same but only after logon.
Brief mention of architecture and Agent placed on VDA.
Mention of entitlement (Enterprise + CSS)
User perception is key, the quicker they see the desktop wallpaper and interact with the desktop the better.
Rather than cache a large file to the VDA, we can just have CPM create a symbolic link to it. This is pretty much like redirected folders at a file level.
Support for one active session at a time.
For keeping the XA/XD environment up to date, mention broker improvements in 7.11.
Just by upgrading to 7.11, you are getting some optimised code that makes improvements to SQL blocking queries. Look at the table, it shows the brokering requests per second between 7.11 and previous versions. Also the amount of time it takes to broker 10k users.
Zones is another way to group Delivery Controllers and VDAs together so that you have your resources closest together wherever they are in the world.
Session Prelaunch is for XenApp applications only and there is no licensing restrictions.
Users that use physical PCs don’t always launch their Citrix applications straight away. We can use this to our advantage.
Prelaunch is enabled by Delivery Group to all users or subset
If user does not launch application, session can be ended after ‘x’ mins/hrs/days
Receiver for Windows must be installed (SSON recommended) with EnablePreLaunch=True
Mention with a VDA freeze, the write cache may be filled.
Other tools such as Splunk, eG Enterprise
EDT is good on latent connections.
Stressed VDAs will result in a higher RTT.
So, first let us understand the Citrix Logon Process itself and what is involved there, as well as the implications of logon slowness.
10% buffer
So, first let us understand the Citrix Logon Process itself and what is involved there, as well as the implications of logon slowness.
Show how eG Enterprise helps diagnose Citrix issues in each of the 3 categories:
User issue: High CPU in desktop or non-corporate app taking more bandwidth and slowing down Citrix session
Citrix issue: Logon GPO
Infra issue: VMware issue prove it’s not Citrix!