Help and Support

Article ID: 893368 - Last Review: October 26, 2006 - Revision: 1.6

Terminal services and remote desktop session events are not logged in Windows 2000 Server

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows Registry

On This Page

Expand all | Collapse all

SYMPTOMS

If auditing to log terminal services and remote desktop session events is enabled on a Microsoft Windows 2000 Server-based computer, the events are not logged in the System event log. For example, auditing is enabled for event logging for Terminal Services client logoffs and for shadowing.

Note Shadowing makes it possible for you to monitor a session of another user. All information that is displayed on the computer of the session that you are shadowing also appears on your computer.
Back to the top

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Microsoft Windows 2000 Service Pack 4 (SP4).

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version         Size       File name
   ----------------------------------------------------------
   07-Feb-2005  05:35  5.0.2195.7026   6,301,696  Sp3res.dll
   07-Feb-2005  06:09  5.0.2195.7028     144,144  Termsrv.exe
   19-Jun-2003  20:05  5.0.2195.6701      39,184  Winsta.dll
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top

MORE INFORMATION

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

After you install the hotfix, make sure that you enable auditing for logon, logoff and remote control events. To do this, follow these steps:
  1. Click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Configuration.
  2. In the Terminal services Configuration box, right-click RDT-Tcp, and then click Properties.
  3. In the RDP-Tcp Properties box, click the Permissions tab, and then click Advanced.
  4. In the Access Control Settings for RDP-Tcp box, click Add.
  5. In the Look in box, click the name of your server, click Everyone, and then click OK.
  6. In the Auditing Entry for RDP-Tcp dialog box, click to select the Successful check box and the Failed check box for the following entries:
    • Remote Control
    • Logon
    • Logoff
  7. Click OK three times.
  8. Close the Terminal Services Configuration window.
To turn on the functionality to log terminal services and remote desktop session events, you must add LogTSLogOff and LogRemoteControl registry entries to the registry. To do this, follow these steps:
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then click the following subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
  3. On the Edit menu, point to New, and then click REG_DWORD Value.
  4. Type LogTSLogOff, and then press ENTER.
  5. Right-click LogTSLogOff, and then click Modify.
  6. Type 1 in the Value data box, and then click OK.
  7. On the Edit menu, point to New, and then click REG_DWORD Value.
  8. Type LogRemoteControl, and then press ENTER.
  9. Right-click LogRemoteControl, and then click Modify.
  10. Type 1 in the Value data box, and then click OK.
  11. Quit Registry Editor
Windows 2000 Service Pack 4 (SP4) adds the EventMessageFile registry entry that is located under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System\TermService
Additionally, you must append the EventMessageFile entry with the following value, including the leading semi-colon :
;%SystemRoot%\System32\sp3res.dll
Note Adding the EventMessageFile registry entry may cause Citrix MetaFrame event logging to stop working. If this issue occurs, contact Citrix to obtain a possible workaround or resolution to this issue.

After you turn on the functionality to log terminal services and remote desktop session events and then view the System event log, events similar to the following events are logged:

Event Type: Information
Event Source: TermService
Event Category: None
Event ID: 35018
Date: Date
Time: Time
User: N/A
Computer: computerName
Description:
Terminal Services Remote Control Attempt Succeeded:
DomainName\administrator attempted a Remote Control of:
User: Username
Domain: DomainName

Event Type: Information
Event Source: TermService
Event Category: None
Event ID: 35020
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Terminal Services Remote LogOff Success:
User Name: UserName
Domain: DomainName
Source Network Address: NetworkAddress

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915  (http://support.microsoft.com/kb/816915/ ) New file naming schema for Microsoft Windows software update packages
For additional information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates


Note Only auditing of Remote Control, Logon, and Logoff for the Everyone user group was implemented.
Back to the top
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
Back to the top
Keywords: 
kbautohotfix kbregistry kbbug kbfix kbhotfixserver kbqfe KB893368
Back to the top

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations

 

Related Support Centers