What is windows termservice
Allows users to connect interactively to a remote computer. Remote Desktop and Remote Desktop Session Host Server depend on this service. To prevent remote use of your computer, clear the checkboxes on the Remote tab of the System properties control panel item.
Default Settings
| Startup type: | Manual |
| Display name: | Remote Desktop Services |
| Service name: | TermService |
| Service type: | share |
| Error control: | normal |
| Object: | NT Authority\NetworkService |
| Path: | %SystemRoot%\System32\svchost.exe -k NetworkService |
| File: | %SystemRoot%\System32\termsrv.dll |
| Registry key: | HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService |
| Privileges: |
|
Default Behavior
Remote Desktop Services is a Win32 service. In Windows 10 it is starting only if the user, an application or another service starts it. When the Remote Desktop Services is started, it is running as NT Authority\NetworkService in a shared process of svchost.exe along with other services. If Remote Desktop Services fails to start, the failure details are being recorded into Event Log. Then Windows 10 will start up and notify the user that the TermService service has failed to start due to the error.
Dependencies
Remote Desktop Services cannot be started under any conditions, if the Remote Procedure Call (RPC) service is disabled.
While Remote Desktop Services is stopped, disabled or working incorrectly, the Remote Desktop Services UserMode Port Redirector cannot be launched.
Restore Default Startup Configuration for Remote Desktop Services
1. Run the Command Prompt as an administrator.
2. Copy the command below, paste it into the command window and press ENTER:
sc config TermService start= demand
3. Close the command window and restart the computer.
Win32_PerfRawData_TermService_TerminalServicesSession class
The Win32_PerfRawData_TermService_TerminalServicesSession raw performance data class provides raw data from performance counters that monitor terminal services resources for each session.
This class represents the Terminal Services Session object in System Monitor. The WMI source of its data is the high-performance Performance Counter Provider. The original data source is the TermService performance library. The corresponding formatted data class is Win32_PerfFormattedData_TermService_TerminalServicesSession.
The following syntax is simplified from MOF code and shows all inherited properties, including the Frequency and Timestamp properties required for class display in System Monitor. For more information about required property qualifiers, see Property Qualifiers for Performance Counter Classes. For more information about CounterType values, see WMI Performance Counter Types.
Syntax
Members
The Win32_PerfRawData_TermService_TerminalServicesSession class has these types of members:
Properties
The Win32_PerfRawData_TermService_TerminalServicesSession class has these properties.
Caption
Data type: string
Access type: Read-only
Short textual description for the statistic or metric. This property is inherited from CIM_StatisticalInformation.
Description
Data type: string
Access type: Read-only
Textual description of the statistic or metric. This property is inherited from CIM_StatisticalInformation.
Frequency_Object
Data type: uint64
Access type: Read-only
Frequency, in ticks per second, of Timestamp_Object. This property is defined by the provider. This property is inherited from Win32_Perf.
For more information about using uint64 values in scripts, see Scripting in WMI.
Frequency_PerfTime
Data type: uint64
Access type: Read-only
Frequency, in ticks per second, of Timestamp_Perftime. A value can be obtained by calling the Windows function QueryPerformanceCounter. This property is inherited from Win32_Perf.
For more information about using uint64 values in scripts, see Scripting in WMI.
Frequency_Sys100NS
Data type: uint64
Access type: Read-only
Frequency, in ticks per second, of Timestamp_Sys100NS (10000000). This property is inherited from Win32_Perf.
For more information about using uint64 values in scripts, see Scripting in WMI.
HandleCount
Data type: uint32
Access type: Read-only
Total number of handles currently opened by this process. This number is the sum of the handles currently opened by each thread in this process.
InputAsyncFrameError
Data type: uint32
Access type: Read-only
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
Data type: uint32
Access type: Read-only
Number of input async overflow errors. These can be caused by a insufficient buffer size available on the host.
InputAsyncOverrun
Data type: uint32
Access type: Read-only
Number of input async overrun errors. An error can occur when the baud rate is too fast for the computer 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 power.
InputAsyncParityError
Data type: uint32
Access type: Read-only
Number of input async parity errors. These can be caused by a noisy transmission line.
InputBytes
Data type: uint32
Access type: Read-only
Number of bytes entered on this session, including all protocol overhead.
InputCompressedBytes
Data type: uint32
Access type: Read-only
Number of bytes entered after compression. This number compared with the TotalBytes value is the compression ratio.
InputCompressFlushes
Data type: uint32
Access type: Read-only
Number of compression dictionary flushes entered. When the data cannot be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. One cause of data not compressing includes transferring compressed files over client drive mappings.
InputCompressionRatio
Data type: uint32
Access type: Read-only
Compression ratio of the server input data stream.
InputErrors
Data type: uint32
Access type: Read-only
Number of input errors of all types. Some examples of input errors are lost acknowledgments (ACKs), badly formed packets, and so on.
InputFrames
Data type: uint32
Access type: Read-only
Number of frames (packets) entered on this session.
InputTimeouts
Data type: uint32
Access type: Read-only
Total number of time outs 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 time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing unnecessary repeat transmissions.
InputTransportErrors
Data type: uint32
Access type: Read-only
Number of Terminal Services transport-level errors on input.
InputWaitForOutBuf
Data type: uint32
Access type: Read-only
Number of times that a wait for an available send buffer was done by the protocols on the client side of the connection.
InputWdBytes
Data type: uint32
Access type: Read-only
Number of bytes entered on this session after all protocol overhead has been removed.
InputWdFrames
Data type: uint32
Access type: Read-only
Number of frames entered after any additional protocol-added frames have been removed.
Name
Data type: string
Access type: Read-only
Label by which the statistic or metric is known. This property is inherited from CIM_StatisticalInformation.
OutputAsyncFrameError
Data type: uint32
Access type: Read-only
Number of output async framing errors. This could be caused by a hardware or line problem.
OutputAsyncOverflow
Data type: uint32
Access type: Read-only
Number of output async overflow errors.
OutputAsyncOverrun
Data type: uint32
Access type: Read-only
Number of output async overrun errors.
OutputAsyncParityError
Data type: uint32
Access type: Read-only
Number of output async overflow errors.
OutputBytes
Data type: uint32
Access type: Read-only
Number of bytes produced on this session, including all protocol overhead.
OutputCompressedBytes
Data type: uint32
Access type: Read-only
Number of bytes produced after compression. This number compared with the TotalBytes value is the compression ratio.
OutputCompressFlushes
Data type: uint32
Access type: Read-only
Number of compression dictionary flushes produced. When the data cannot be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. One cause of data not compressing includes transferring compressed files over client drive mappings.
OutputCompressionRatio
Data type: uint32
Access type: Read-only
Compression ratio of the server output data stream.
OutputErrors
Data type: uint32
Access type: Read-only
Number of output errors of all types. Some examples of output errors are lost acknowledgments (ACKs), badly formed packets, and so on.
OutputFrames
Data type: uint32
Access type: Read-only
Number of frames (packets) produced on this session.
OutputTimeouts
Data type: uint32
Access type: Read-only
Total number of time outs 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 time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing unnecessary repeat transmissions.
OutputTransportErrors
Data type: uint32
Access type: Read-only
Number of Terminal Services errors produced at the transport level.
OutputWaitForOutBuf
Data type: uint32
Access type: Read-only
Number of times that a wait for an available send buffer was done by the protocol on the server side of the connection.
OutputWdBytes
Data type: uint32
Access type: Read-only
Number of bytes produced on this session after all protocol overhead has been removed.
OutputWdFrames
Data type: uint32
Access type: Read-only
Number of frames produced before any additional protocol frames have been added.
PageFaultsPerSec
Data type: uint32
Access type: Read-only
Rate at which page faults occur in the threads executing in this process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. The page may not be retrieved from disk if it is on the standby list and therefore already in main memory. The page also may not be retrieved if it is in use by another process which shares the page.
PageFileBytes
Data type: uint64
Access type: Read-only
Current number of bytes this process has used 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 lack of space in paging files can prevent other processes from allocating memory.
For more information about using uint64 values in scripts, see Scripting in WMI.
PageFileBytesPeak
Data type: uint64
Access type: Read-only
Maximum number of bytes this process has used 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 lack of space in paging files can prevent other processes from allocating memory.
For more information about using uint64 values in scripts, see Scripting in WMI.
PercentPrivilegedTime
Data type: uint64
Access type: Read-only
Percentage of elapsed time that the threads of the process have spent executing code in privileged mode. When an operating system service is called, the service often runs 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. The operating system uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by the operating system on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.
For more information about using uint64 values in scripts, see Scripting in WMI.
PercentProcessorTime
Data type: uint64
Access type: Read-only
Percentage of elapsed time that all of the threads of this process used the processor to execute 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.
For more information about using uint64 values in scripts, see Scripting in WMI.
PercentUserTime
Data type: uint64
Access type: Read-only
Percentage of elapsed time that this process’s threads have spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in the user mode cannot damage the integrity of the operating system executive, kernel, and device drivers. The operating system uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by the operating system on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.
For more information about using uint64 values in scripts, see Scripting in WMI.
PoolNonpagedBytes
Data type: uint32
Access type: Read-only
Number of bytes in the non-paged 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. This property displays the last observed value only; it is not an average.
PoolPagedBytes
Data type: uint32
Access type: Read-only
Number of bytes in 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. This property displays the last observed value only; it is not an average.
PrivateBytes
Data type: uint64
Access type: Read-only
Current number of bytes this process has allocated that cannot be shared with other processes.
For more information about using uint64 values in scripts, see Scripting in WMI.
ProtocolBitmapCacheHitRatio
Data type: uint32
Access type: Read-only
Hit ratio in the protocol bitmap cache. A higher bit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not reused or is flushed out of the client cache.
ProtocolBitmapCacheHits
Data type: uint32
Access type: Read-only
Number of hits in the protocol bitmap cache.
ProtocolBitmapCacheReads
Data type: uint32
Access type: Read-only
Number of references to the protocol bitmap cache.
ProtocolBrushCacheHitRatio
Data type: uint32
Access type: Read-only
Hit ratio in the protocol brush cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not used again or is flushed out of the client cache.
ProtocolBrushCacheHits
Data type: uint32
Access type: Read-only
Number of hits in the protocol brush cache.
ProtocolBrushCacheReads
Data type: uint32
Access type: Read-only
Number of references to the protocol brush cache.
ProtocolGlyphCacheHitRatio
Data type: uint32
Access type: Read-only
Hit ratio in the protocol glyph cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not used again or is flushed out of the client cache.
ProtocolGlyphCacheHits
Data type: uint32
Access type: Read-only
Number of hits in the protocol glyph cache.
ProtocolGlyphCacheReads
Data type: uint32
Access type: Read-only
Hit ratio in the protocol glyph cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not used again or is flushed out of the client cache.
ProtocolSaveScreenBitmapCacheHitRatio
Data type: uint32
Access type: Read-only
Hit ratio in the protocol save screen bitmap cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not used again or is flushed out of the client cache.
ProtocolSaveScreenBitmapCacheHits
Data type: uint32
Access type: Read-only
Number of hits in the protocol save screen bitmap cache.
ProtocolSaveScreenBitmapCacheReads
Data type: uint32
Access type: Read-only
Number of references to the protocol save screen bitmap cache.
ThreadCount
Data type: uint32
Access type: Read-only
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
Data type: uint64
Access type: Read-only
Object-defined timestamp, defined by the provider. This property is inherited from Win32_Perf.
For more information about using uint64 values in scripts, see Scripting in WMI.
Timestamp_PerfTime
Data type: uint64
Access type: Read-only
High Performance counter timestamp. A value can be obtained by calling the Windows function QueryPerformanceCounter. This property is inherited from Win32_Perf.
For more information about using uint64 values in scripts, see Scripting in WMI.
Timestamp_Sys100NS
Data type: uint64
Access type: Read-only
Timestamp value in 100 nanosecond units. This property is inherited from Win32_Perf.
For more information about using uint64 values in scripts, see Scripting in WMI.
TotalAsyncFrameError
Data type: uint32
Access type: Read-only
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
Data type: uint32
Access type: Read-only
Qualifiers: DisplayName («Total Async Overflow») , CounterType (65536) , DefaultScale (0) , Pewmi.property_qualifiers_for_performance_counter_classesrfDetail (100)
Total number of async overflow errors. These can be caused by a insufficient buffer size available on the host.
TotalAsyncOverrun
Data type: uint32
Access type: Read-only
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 power.
TotalAsyncParityError
Data type: uint32
Access type: Read-only
Total number of async parity errors. These can be caused by a noisy transmission line.
TotalBytes
Data type: uint32
Access type: Read-only
Total number of bytes on this session, including all protocol overhead.
TotalCompressedBytes
Data type: uint32
Access type: Read-only
Total number of bytes after compression. This number compared with the TotalBytes value is the compression ratio.
TotalCompressFlushes
Data type: uint32
Access type: Read-only
Total number of compression dictionary flushes. When the data cannot be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. One cause of data not compressing includes transferring compressed files over client drive mappings.
TotalCompressionRatio
Data type: uint32
Access type: Read-only
Total compression ratio of the server data stream.
TotalErrors
Data type: uint32
Access type: Read-only
Total number of errors of all types. Some example errors are lost acknowledgments (ACKs), badly formed packets, and so on.
TotalFrames
Data type: uint32
Access type: Read-only
Total number of time outs 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 time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing needless re-transmissions.
TotalProtocolCacheHitRatio
Data type: uint32
Access type: Read-only
Overall hit ratio for all protocol caches.
TotalProtocolCacheHits
Data type: uint32
Access type: Read-only
Total hits in all protocol caches. The protocol caches Windows objects that are likely to be re-used to avoid having to send them again on the transmission line. Example objects are Windows icons and brushes. Hits in the cache represent objects that did not must be re-sent.
TotalProtocolCacheReads
Data type: uint32
Access type: Read-only
Total references to all protocol caches.
TotalTimeouts
Data type: uint32
Access type: Read-only
Total number of time outs 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 time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing unnecessary repeat transmissions.
TotalTransportErrors
Data type: uint32
Access type: Read-only
Total number of Terminal Services transport-level errors.
TotalWaitForOutBuf
Data type: uint32
Access type: Read-only
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
Data type: uint32
Access type: Read-only
Total number of bytes on this session after all protocol overhead has been removed.
TotalWdFrames
Data type: uint32
Access type: Read-only
Total number of frames entered and produced before any additional protocol frames have been added.
VirtualBytes
Data type: uint64
Access type: Read-only
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, by using too much, the process can limit its ability to load libraries.
For more information about using uint64 values in scripts, see Scripting in WMI.
VirtualBytesPeak
Data type: uint64
Access type: Read-only
Maximum number of 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. Virtual space is finite and, by using too much, the process might limit its ability to load libraries.
For more information about using uint64 values in scripts, see Scripting in WMI.
WorkingSet
Data type: uint64
Access type: Read-only
Current number of bytes in 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 are then soft-faulted back into the working set before they leave main memory.
For more information about using uint64 values in scripts, see Scripting in WMI.
WorkingSetPeak
Data type: uint64
Access type: Read-only
Maximum number of bytes in 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 are then soft-faulted back into the working set before they leave main memory.
For more information about using uint64 values in scripts, see Scripting in WMI.
Remarks
All classes derived from Win32_Perf are designed to be used with a refresher object. For more information about how to create and use a refresher object in C++, see Accessing Performance Data in C++. For more information about how to create and use a refresher object using scripts, see Refreshing WMI Data in Scripts.
The performance class and property qualifiers determine how to interpret the class data. For more information, see Class Qualifiers for Performance Counter Classes and Property Qualifiers for Performance Counter Classes.
Examples
For script code examples, see WMI Tasks for Scripts and Applications and the TechNet ScriptCenter Script Repository.
