This article provides a list of CDF tracing recommendations that facilitate faster turnaround and better quality analysis reports from Citrix technical support Personnel by analyzing the CDF traces.

Recommendations for Collecting the CDF Traces

• Check that the traces are not empty before sending to the support team.

• If the problem cannot be reproduced in some specific configurations and/or servers, send two traces (better and worst) for comparison. The latter must be taken when the problem can be reproduced. Both the traces must be taken in the most similar environments.

• Tracing time, the duration that is needed to reproduce the issue must be as short as possible.

• Avoid using split traces when using the CDFControl tool (CDFControl).

• Keep a minimum number of sessions opened during the tracing period.

• Check the start and stop time of the CDF trace for timing related issues. For example, when logon takes five minutes, the tracing time must take six minutes.

• Take supporting notes about relevant data like session ID, user name, printers names, process ID, and so on.

• CDF traces are not different from other types of software traces like registry, file monitoring, event logs, and the output of many other troubleshooting tools. Keep in mind about the information that Citrix technical support personnel might need for better and faster analysis of the data.