This article contains information about enabling Group Policy packet tracing in XenApp 6 and XenDesktop 5.

Background

The XenApp 6 and XenDesktop 5 releases of the Group Policy Engine do not support Citrix Diagnostic Facility (CDF) tracing. However, Group Policy Engine supports tracing to DebugView and tracing to a file in order to help debugging of boot-up issues.
You can use the following components to record network packet traces:

• Group Policy UI Components: The Group Policy UI components use the System.Diagnostics.Trace class to record network packet traces. You can use DebugView utility to display the output. Refer to http://technet.microsoft.com/en-us/sysinternals/bb896647 web page for more information.

• Group Policy Engine: The Group Policy Engine uses OutputDebugString to record network packet traces and supports file tracing for debugging boot-up issues. By default, the tracing feature for this component is disabled because this component must be performant.

---

Instructions

To enable Group Policy packet tracing in XenApp 6 and XenDesktop 5, complete the following procedures:

• Client DLL Tracing
• Server EXE Tracing

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Client DLL Tracing

Complete the following procedure to enable client DLL tracing:

1. Set or create the following registry REG_DWORD value to enable DebugView tracing for CitrixCseClient.dll:
   Key: HKLM\SOFTWARE\Citrix\GroupPolicy
   Value Name: CseClientTraceDebug
   Value Data: 0xFFFFFFFF

2. The following screen shot displays the CseClientTraceDebug registry key in the Registry Editor Window:

   

3. If running an application on a 64-bit operating system, set or create the following REG_DWORD registry value to view 32-bit processes for CitrixCseClient.dll:
   Key:HKLM\SOFTWARE\Wow6432Node\Citrix\GroupPolicy
   Value Name: CseClientTraceDebug
   Value Data: 0xFFFFFFFF

4. The following screen shot displays the CseClientTraceDebug registry key in the Registry Editor Window:

   

5. As an administrator, run the application to display the trace messages in DebugView and enable the following tracing options:

   • Capture Win32

   • Capture Global Win32

6. The following screen shot displays the Capture menu options to enable the required options:

   

7. To record the current DebugView information in a log file for non-boot up processing issues, select Save as from the DebugView file menu before you start recording packet traces.

8. To enable file tracing for debugging boot-up issues, create the CseClientTraceDebug value name of the REG_SZ type, as displayed in the following screen shot:

   

Server EXE Tracing

To enable the server EXE tracing, complete the following procedure:

1. Set or create the following REG_DWORD registry value to enable DebugView tracing for CitrixCseEngine.exe:

   Key: HKLM\SOFTWARE\Citrix\GroupPolicy
   Value Name: CseServiceTraceDebug
   Value Data: 0xFFFFFFFF

2. The following screen shot displays the CseServiceTraceDebug registry key in the Registry Editor Window:

   

3. To enable file tracing for debugging boot-up issues, create the CseServiceTraceDebug value name of the REG_SZ type, as displayed in the following screen shot:

   

    

File Tracing Details

File tracing for debugging the boot-up issues writes all trace information to a file that represents the calling process. These files are placed in the Windows temp directory.
The following are the file names to which the trace information is written:

• CitrixCseClient: CitrixCseClient-CALLING_MODULE_NAME-CALLING_PROCESS_ID.log

• CitrixCseEngine: CitrixCseEngine.log

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

This article contains information about enabling Group Policy packet tracing in XenApp 6 and XenDesktop 5.