Depends on what problem you are having. Very often, the first thing you have to do is debunk the "it's a Citrix problem" any time an application acts goofy. Always have a "fat client" installation of your applications, or a way to remove Citrix from the equation. In general the best practice for troubleshooting is: - characterize the problem: When did it start? Who is affected? Is it reproducible? Is it limited to just one application? Just one server? Just one site? Just one user? You CANNOT effectively solve a problem without knowing these kinds of "clues" about what might be causing it. - come up with the simplest explanation that might cause the problem you are seeing, and then test your hypothesis. Continue in this way, until you have found the hypothesis that is correct. During testing, only change one variable at a time, so that if the problem is resolved, you KNOW which change made the difference! ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of deheugden Sent: Thursday, January 10, 2008 8:40 AM To: thin Subject: [THIN] troubleshooting a citrix environment guys, when there are troubles in a citrix environment,whats best practise for troubleshooting this.how should i start,... the reason for this is that i want too write a troubleshooting guide for our admins. regards, johan This message and any attachments may be a confidential attorney-client communication or otherwise be privileged and confidential. If you are not the intended recipient, any review, distribution or copying of this transmittal is prohibited. If you have received this transmittal in error, please reply by e-mail and delete this message and all attachments