Discussion:
Missing Win32_PerfRawData_TermService_TerminalServices on Windows
(too old to reply)
Teknix1
2009-03-27 11:48:01 UTC
Permalink
Hi,

Is there Win32_PerfRawData_TermService_TerminalServices WMI class on Windows
2008 & Vista or is the documentation incorrect?
http://msdn.microsoft.com/en-us/library/aa394343(VS.85).aspx

Every Windows 2008 or Vista machine I have seen is missing this class. I
have rebuilt the WMI repository, reregistered WmiPerfInst.dll and rebuilt
mofs without luck.

If it does exist, instructions on how to bring it back would be very nice.

Thank you
Nicolas
unknown
2009-11-16 15:30:30 UTC
Permalink
This class has been moved to

Win32_PerfRawData_LocalSessionManager_TerminalServices



hope it helps

Alzoo



Teknix wrote:

Missing Win32_PerfRawData_TermService_TerminalServices on Windows
27-Mar-09

Hi

Is there Win32_PerfRawData_TermService_TerminalServices WMI class on Windows
2008 & Vista or is the documentation incorrect
http://msdn.microsoft.com/en-us/library/aa394343(VS.85).asp

Every Windows 2008 or Vista machine I have seen is missing this class. I
have rebuilt the WMI repository, reregistered WmiPerfInst.dll and rebuilt
mofs without luck

If it does exist, instructions on how to bring it back would be very nice

Thank yo
Nicolas

Previous Posts In This Thread:

On 27 March 2009 07:48
Teknix wrote:

Missing Win32_PerfRawData_TermService_TerminalServices on Windows
Hi

Is there Win32_PerfRawData_TermService_TerminalServices WMI class on Windows
2008 & Vista or is the documentation incorrect
http://msdn.microsoft.com/en-us/library/aa394343(VS.85).asp

Every Windows 2008 or Vista machine I have seen is missing this class. I
have rebuilt the WMI repository, reregistered WmiPerfInst.dll and rebuilt
mofs without luck

If it does exist, instructions on how to bring it back would be very nice

Thank yo
Nicolas

EggHeadCafe - Software Developer Portal of Choice
C00D11BB - resolve protocol error from Windows Media Player
http://www.eggheadcafe.com/tutorials/aspnet/187cb72b-8da5-4dd9-b061-52e6d6304bee/c00d11bb--resolve-protoc.aspx
Loading...