Article ID: 914539 - Last Review: May 8, 2007 - Revision: 2.6 The Terminal Server object and the object of the Terminal Server session for a Windows Server 2003 Terminal Server are unavailable when you use Performance Monitor on a remote computerImportant This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify 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 SYMPTOMSWhen you use Performance Monitor to remotely monitor the performance of a Microsoft Windows Server 2003 Terminal Server, the Terminal Server object and the object of the Terminal Server session are unavailable. This issue occurs even when the remote user is a member of the Performance Monitor Users group on the Windows Server 2003 Terminal Server. CAUSEThis issue occurs if the Performance Monitor Users group does not have permissions to the Application log in Windows Server 2003. RESOLUTION
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
WORKAROUNDWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. To work around this issue, give Read permissions and Write permissions to the Performance Monitor Users group for the Application log in Windows Server 2003. To do this, follow these steps:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2. MORE INFORMATION
For more information about event log security, click the following article number to view the article in the Microsoft Knowledge Base:
323076
(http://support.microsoft.com/kb/323076/
)
How to set event log security locally or by using Group Policy in Windows Server 2003
For more information about security descriptors, visit the following Microsoft Web sites:
http://msdn2.microsoft.com/en-us/library/aa379602.aspx
(http://msdn2.microsoft.com/en-us/library/aa379602.aspx)
http://msdn2.microsoft.com/en-us/library/aa374928.aspx
(http://msdn2.microsoft.com/en-us/library/aa374928.aspx)
APPLIES TO
| Article Translations
|
Back to the top
