To troubleshoot Session Directory for Terminal Services servers, you can use the Terminal Services Session Directory logging feature. This article describes how to turn on this feature.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
- Stop the Terminal Services Session Directory service.
- In the registry, locate the following key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tssdis\Parameters
- If the Parameters key does not exist, create it.
- Add the following DWORD value:TraceOutputMode
- Select the option you want:
- 0 (no output)
- 1 (output to debugger)
- 3 (output to log file)
- Start the Terminal Services Session Directory Service. If you selected option 3 in step 5, Terminal Service Session Directory placess the output in a log file that is named Tssdis.log under following folder.
- For Windows Server 2008 based Terminal Services Session broker, under %systemroot%\system32\tssesdir folder.
- For Windows Server 2003 based Terminal Service Session Directory service, under %systemroot%\system32 folder.
- Session Directory service started
- Session Directory service stopped
- Machine joins session directory
- Machine leaves session directory
- User logs in
- User disconnects
- User reconnects
- User logs out
- Session Directory-related event log messages.
Article ID: 327508 - Last Review: Apr 6, 2010 - Revision: 1