- WMI Library -
WMI Libraly > Win32_PerfFormattedData_TermService_TerminalServicesSession Class

Win32_PerfFormattedData_TermService_TerminalServicesSession Class

Terminal Services per-session resource monitoring.
Namespace value is root/CIMV2.
WMI Provider value is WmiPerfInst.


Properties

  • Caption
  • A short textual description (one-line string) for the statistic or metric.

  • Description
  • A textual description of the statistic or metric.

  • Frequency_Object
  • Not applicable.

  • Frequency_PerfTime
  • Not applicable.

  • Frequency_Sys100NS
  • Not applicable.

  • HandleCount
  • The total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.

  • InputAsyncFrameError
  • Number of input async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size may help in some cases.

  • InputAsyncOverflow
  • Number of input async overflow errors. These can be caused by a lack of buffer space available on the host.

  • InputAsyncOverrun
  • Number of input async overrun errors. These can be caused by the baud rate being faster than the computer can handle, or a non-16550 serial line is used. Overruns can also occur if too many high speed serial lines are active at one time for the processor's power.

  • InputAsyncParityError
  • Number of input async parity errors. These can be caused by a noisy transmission line

  • InputBytes
  • Number of bytes input on this session that includes all protocol overhead.

  • InputCompressedBytes
  • Number of bytes input after compression. This number compared with the Total Bytes input is the compression ratio.

  • InputCompressFlushes
  • Number of input compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transferring compressed files over Client Drive Mapping.

  • InputCompressionRatio
  • Compression ratio of the server input data stream.

  • InputErrors
  • Number of input errors of all types. Some example input errors are lost ACK's, badly formed packets, etc.

  • InputFrames
  • Number of frames (packets) input on this Session.

  • InputTimeouts
  • The total number of timeouts on the communication line as seen from the client side of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions.

  • InputTransportErrors
  • Number of Terminal Services transport-level errors on input.

  • InputWaitForOutBuf
  • The number of times that a wait for an available send buffer was done by the protocols on the client side of the connection.

  • InputWdBytes
  • Number of bytes input on this session after all protocol overhead has been removed.

  • InputWdFrames
  • The number of frames input after any additional protocol added frames have been removed.

  • Name
  • The Name property defines the label by which the statistic or metric is known. When subclassed, the property can be overridden to be a Key property.

  • OutputAsyncFrameError
  • Number of output async framing errors. This could be caused by a hardware or line problem.

  • OutputAsyncOverflow
  • Number of output async overflow errors.

  • OutputAsyncOverrun
  • Number of output async overrun errors.

  • OutputAsyncParityError
  • Number of output async parity errors. These can be caused by a hardware or line problem.

  • OutputBytes
  • Number of bytes output on this Session that includes all protocol overhead.

  • OutputCompressedBytes
  • Number of bytes output after compression. This number compared with the Total Bytes output is the compression ratio.

  • OutputCompressFlushes
  • Number of output compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transfering compressed files over Client Drive Mapping.

  • OutputCompressionRatio
  • Compression ratio of the server output data stream.

  • OutputErrors
  • Number of output errors of all types. Some example output errors are lost ACK's, badly formed packets, etc.

  • OutputFrames
  • Number of frames (packets) output on this session.

  • OutputTimeouts
  • The total number of timeouts on the communication line from the host side of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions.

  • OutputTransportErrors
  • Number of Terminal Services transport-level errors on output.

  • OutputWaitForOutBuf
  • This is the number of times that a wait for an available send buffer was done by the protocol on the server side of the connection.

  • OutputWdBytes
  • Number of bytes output on this session after all protocol overhead has been removed.

  • OutputWdFrames
  • The number of frames output before any additional protocol frames have been added.

  • PageFaultsPersec
  • Page Faults/sec is the rate at which page faults by the threads executing in this process are occurring. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.

  • PageFileBytes
  • Page File Bytes is the current amount of virtual memory, in bytes, that this process has reserved for use in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this counter reflects the current amount of virtual memory that the process has reserved for use in physical memory.

  • PageFileBytesPeak
  • Page File Bytes Peak is the maximum amount of virtual memory, in bytes, that this process has reserved for use in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this counter reflects the maximum amount of virtual memory that the process has reserved for use in physical memory.

  • PercentPrivilegedTime
  • % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

  • PercentProcessorTime
  • % Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.

  • PercentUserTime
  • % User Time is the percentage of elapsed time that the process threads spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in user mode cannot damage the integrity of the Windows executive, kernel, and device drivers. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

  • PoolNonpagedBytes
  • Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process\\Pool Nonpaged Bytes\\_Total. This counter displays the last observed value only; it is not an average.

  • PoolPagedBytes
  • Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process\\Pool Paged Bytes\\_Total. This counter displays the last observed value only; it is not an average.

  • PrivateBytes
  • Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.

  • ProtocolBitmapCacheHitRatio
  • Hit ratio in the protocol bitmap cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

  • ProtocolBitmapCacheHits
  • Number of hits in the protocol bitmap cache.

  • ProtocolBitmapCacheReads
  • Number of references to the protocol bitmap cache.

  • ProtocolBrushCacheHitRatio
  • Hit ratio in the protocol brush cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

  • ProtocolBrushCacheHits
  • Number of hits in the protocol brush cache.

  • ProtocolBrushCacheReads
  • Number of references to the protocol brush cache.

  • ProtocolGlyphCacheHitRatio
  • Hit ratio in the protocol glyph cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

  • ProtocolGlyphCacheHits
  • Number of hits in the protocol glyph cache.

  • ProtocolGlyphCacheReads
  • Number of references to the protocol glyph cache.

  • ProtocolSaveScreenBitmapCacheHitRatio
  • Hit ratio in the protocol save screen bitmap cache. A higher hit ratio means better performance since data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

  • ProtocolSaveScreenBitmapCacheHits
  • Number of hits in the protocol save screen bitmap cache.

  • ProtocolSaveScreenBitmapCacheReads
  • Number of references to the protocol save screen bitmap cache.

  • ThreadCount
  • The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.

  • Timestamp_Object
  • Not applicable.

  • Timestamp_PerfTime
  • Not applicable.

  • Timestamp_Sys100NS
  • Not applicable.

  • TotalAsyncFrameError
  • Total number of async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size may help in some cases.

  • TotalAsyncOverflow
  • Total number of async overflow errors. These can be caused by a lack of buffer space available on the host.

  • TotalAsyncOverrun
  • Total number of async overrun errors. These can be caused by the baud rate being faster than the computer can handle, or a non-16550 serial line is used. Overruns can also occur if too many high speed serial lines are active at one time for the processor's power.

  • TotalAsyncParityError
  • Total number of async parity errors. These can be caused by a noisy transmission line.

  • TotalBytes
  • Total number of bytes on this Session that includes all protocol overhead.

  • TotalCompressedBytes
  • Total number of bytes after compression. This number compared with the total bytes is the compression ratio.

  • TotalCompressFlushes
  • Total number of compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transfering compressed files over Client Drive Mapping.

  • TotalCompressionRatio
  • Total compression ratio of the server data stream.

  • TotalErrors
  • Total number of errors of all types. Some example errors are lost ACK's, badly formed packets, etc.

  • TotalFrames
  • Total number of frames (packets) on this Session.

  • TotalProtocolCacheHitRatio
  • Overall hit ratio for all protocol caches.

  • TotalProtocolCacheHits
  • Total hits in all protocol caches. The protocol caches Windows objects that are likely to be re-used to avoid having to re-send them on the transmission line. Example objects are Windows icons and brushes. Hits in the cache represent objects that did not need to be re-sent.

  • TotalProtocolCacheReads
  • Total references to all protocol caches.

  • TotalTimeouts
  • The total number of timeouts on the communication line from both the host and client sides of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions.

  • TotalTransportErrors
  • Total number of Terminal Services transport-level errors.

  • TotalWaitForOutBuf
  • The number of times that a wait for an available send buffer was done by the protocols on both the server and client sides of the connection.

  • TotalWdBytes
  • Total number of bytes on this Session after all protocol overhead has been removed.

  • TotalWdFrames
  • The total number of frames input and output before any additional protocol frames have been added.

  • VirtualBytes
  • Virtual Bytes is the current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries.

  • VirtualBytesPeak
  • Virtual Bytes Peak is the maximum size, in bytes, of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. However, virtual space is finite, and the process might limit its ability to load libraries.

  • WorkingSet
  • Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.

  • WorkingSetPeak
  • Working Set Peak is the maximum size, in bytes, of the Working Set of this process at any point in time. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before they leave main memory.


    Methods

    Method not found.

    Example WQL

    SELECT * FROM Win32_PerfFormattedData_TermService_TerminalServicesSession
    About this site information

    This contents is created by WMI having class information.
    WMI Environment is Windows Server 2008 R2 Enterprise Edition.

    This link is Microsoft documents for "Managing Windows with WMI".
    That is VB(Visual Basic) scripting sample.
    This link is Microsoft documents for "Advanced Programming Topics in WMI .NET".
    That is VB.net(Visual Basic .net) scripting sample.

    - WMI Library -
    http://library.wmifun.net/

    WMI useful by VB,VB.Net,VC,VC.Net,VC#.Net,VBS(WSH),PowerShell for PC asset management, system monitoring and collecting hardware and software inventory.

    This website is created by Toh.
    Copyright(C) 1997-2016 WMI Fun !!. All rights reserved.
    ^ Go to the top...