| Name | Description |
|---|---|
| ARC_CS_PRIVATE_PACKET | The ARC_CS_PRIVATE_PACKET structure contains the client response cookie used to seamlessly re-establish a client session connection after network interruption. It is sent as part of the extended information of the Client Info PDU. |
| ARC_SC_PRIVATE_PACKET | The ARC_SC_PRIVATE_PACKET structure contains server-supplied information used to seamlessly re-establish a client session connection after network interruption. It is sent as part of the Save Session Info PDU logon information (see section ). |
| ByteClass | A class wraps byte. This class is used especially for some optional integer fields. To set it null means not the field of this type will not present, or else it is present. |
| CERT_BLOB | The CertBlob packet encapsulates an X.509 certificate |
| CHANNEL_DEF | The CHANNEL_DEF packet contains information for a particular static virtual channel. |
| CHANNEL_PDU_HEADER | The CHANNEL_PDU_HEADER MUST precede all opaque static virtual channel traffic chunks transmitted via RDP between client and server. |
| ChannelChunk | Virtual Channel data. |
| Client_Auto_Detect_Response_PDU | The Auto-Detect Response PDU is sent by the client to the server and is used to detect network characteristics such as bandwidth and round-trip time. |
| Client_Confirm_Active_Pdu | The Confirm Active PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Capabilities Negotiation phase (see section ). It is sent as a response to the Demand Active PDU. |
| Client_Control_Pdu_Cooperate | The Client Control PDU (Cooperate) is a Standard RDP Connection Sequence PDU sent from client to server during the Connection Finalization phase (see section ). It is sent after transmitting the Client Synchronize PDU. |
| Client_Control_Pdu_Request_Control | The Client Control PDU (Request Control) is a Standard RDP Connection Sequence PDU sent from client to server during the Connection Finalization phase (see section ). It is sent after transmitting the Client Control PDU (Cooperate). |
| Client_Font_List_Pdu | The Font List PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Connection Finalization phase (see section ). It is sent after transmitting a Persistent Key List PDU or, if the Persistent Key List PDU was not sent, it is sent after transmitting the Client Control PDU (Request Control). |
| Client_Info_Pdu | The Client Info PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Secure Settings Exchange phase (see section ). It is sent after transmitting a Security Exchange PDU or, if the Security Exchange PDU was not sent, it is transmitted after receiving all requested MCS Channel Join Confirm PDUs. |
| Client_Initiate_Multitransport_Response_PDU | The Initiate Multitransport Response PDU is sent by the client to the server and is used to indicate to the server whether the client was able to complete the multitransport initiation request associated with the ID specified in the requestId field. |
| Client_MCS_Attach_User_Request | The MCS Attach User Request PDU is an RDP Connection Sequence PDU sent from client to server during the Channel Connection phase (see section 1.3.1.1) to request a user channel ID. It is sent after transmitting the MCS Erect Domain Request PDU (section 2.2.1.5). |
| Client_MCS_Channel_Join_Request | The MCS Channel Join Request PDU is an RDP Connection Sequence PDU sent from client to server during the Channel Connection phase (see section 1.3.1.1). It is sent after receiving the MCS Attach User Confirm PDU (section 2.2.1.7). The client uses the MCS Channel Join Request PDU to join the user channel obtained from the Attach User Confirm PDU, the I/O channel and all of the static virtual channels obtained from the Server Network Data structure (section 2.2.1.4.4). |
| Client_MCS_Connect_Initial_Pdu_with_GCC_Conference_Create_Request | The MCS Connect Initial PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Basic Settings Exchange phase (see Section ). It is sent after receiving the X.224 Connection Confirm PDU. The MCS Connect Initial PDU encapsulates a GCC Conference Create Request, which encapsulates concatenated blocks of settings data. A basic high-level overview of the nested structure for the Client MCS Connect Initial PDU is illustrated in Figure 2. Note that the order of the settings data blocks is allowed to vary from that shown in Figure 2 and the message syntax layout which follows. This is possible because each data block is identified by a User Data Header structure (see section ). |
| Client_MCS_Erect_Domain_Request | The MCS Erect Domain Request PDU is an RDP Connection Sequence PDU sent from client to server during the Channel Connection phase (see section 1.3.1.1). It is sent after receiving the MCS Connect Response PDU (section 2.2.1.4). |
| Client_Persistent_Key_List_Pdu | The Persistent Key List PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Connection Finalization phase (see section ). This PDU MAY be sent after transmitting the Client Control PDU (Request Control). It MUST NOT be sent to a server which does not advertise support for the Bitmap Host Cache Support Capability Set. |
| Client_Refresh_Rect_Pdu | The Refresh Rect PDU allows the client to request that the server redraw one or more rectangles of the session screen area. The client can use it to repaint sections of the client window that were obscured by other windowed applications. Server support for this PDU is indicated in the General Capability Set. |
| Client_Security_Exchange_Pdu | The Security Exchange PDU is a Standard RDP Connection Sequence PDU sent from client to server during the RDP Security Commencement phase (see section ). It MAY be sent after receiving all requested MCS Channel Join Confirm PDUs. |
| Client_Shutdown_Request_Pdu | The Shutdown Request PDU is sent by the client as part of the disconnection sequences specified in section ; specifically as part of the User-Initiated on Client disconnect sequence (see section ). |
| Client_Suppress_Output_Pdu | The Suppress Output PDU is sent by the client to toggle all display updates from the server. This packet does not end the session or socket connection. Typically, a client sends this packet when its window is either minimized or restored. |
| Client_Synchronize_Pdu | The Client Synchronize PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Connection Finalization phase (see section ). It is sent after transmitting the Confirm Active PDU. |
| Client_X_224_Connection_Request_Pdu | The X.224 Connection Request PDU is a Standard RDP Connection Sequence PDU sent from client to server during the Connection Initiation phase (see section ). |
| ConnectGCC | Gcc used in MCSConnectInitial. |
| ConnectGCCRsp | Gcc used in MCSConnectInitial. |
| DomainParameter | DomainParameter used in MCSConnectInitial. |
| Early_User_Authorization_Result_PDU | The Early User Authorization Result PDU is sent from server to client and is used to convey authorization information to the client. This PDU is only sent by the server if the client advertised support for it by specifying the PROTOCOL_HYBRID_EX (0x00000008) flag in the requestedProtocols field of the RDP Negotiation Request structure and it MUST be sent immediately after the CredSSP handshake has completed. |
| Enhanced_Security_Server_Redirection_Pdu | The Enhanced Security Server Redirection PDU is sent by the server to the client to instruct it to reconnect to an existing session on another server. The information required to perform the reconnection is contained in an embedded Server Redirection Packet (section 2.2.13.1). This PDU MUST NOT be sent if Standard RDP Security (see section 5.3) is in effect. The Standard Security Server Redirection PDU (see section 2.2.13.2.1) MUST be used instead. |
| ErrorPdu | A type of PDU to indicate some errors. |
| LICENSE_BINARY_BLOB | The LICENSE_BINARY_BLOB structure is used to encapsulate arbitrary length binary licensing data. |
| LICENSE_ERROR_MESSAGE | The LICENSE_ERROR_MESSAGE structure is used to indicate that an error occurred during the licensing protocol. Alternatively, it is also used to notify the peer of important status information. |
| LICENSE_PREAMBLE | The LICENSE_PREAMBLE structure precedes every licensing packet sent on the wire. |
| MCSConnectInitial | The main fields of MCS Connect Initial PDU. |
| MCSConnectResponse | The main fields of MCS Connect Initial PDU. |
| MCS_Disconnect_Provider_Ultimatum_Pdu | The MCS Disconnect Provider Ultimatum PDU is an MCS PDU sent as part of the disconnection sequences, as specified in section . |
| MCS_Disconnect_Provider_Ultimatum_Server_Pdu | The MCS Disconnect Provider Ultimatum PDU is an MCS PDU sent as part of the disconnection sequences, as specified in section . |
| NETWORK_DETECTION_REQUEST | Base class for all network detection request structure |
| NETWORK_DETECTION_RESPONSE | Base class for all the Network Detection Response Structures |
| PROPRIETARYSERVERCERTIFICATE | The PROPRIETARYSERVERCERTIFICATE structure describes a signed certificate containing the server's public key and conforming to the structure of a Server Certificate. For a detailed description of Proprietary Certificates, see section . |
| RDP_BW_PAYLOAD | The RDP_BW_PAYLOAD structure is used to transfer data associated with a bandwidth measurement operation that takes place during the Optional Connect-Time Auto-Detection phase of the RDP Connection Sequence |
| RDP_BW_RESULTS | The RDP_BW_RESULTS structure is used to send the results of a bandwidth measurement operation to the initiating end-point. |
| RDP_BW_START | The RDP_BW_START structure is used to start a bandwidth measurement operation. |
| RDP_BW_STOP | The RDP_BW_STOP structure is used to stop a bandwidth measurement operation. |
| RDP_NEG_CORRELATION_INFO | The RDP Correlation Info structure is used by a client to propagate connection correlation information to the server. This information allows diagnostic tools on the server to track and monitor a specific connection as it is handled by Terminal Services components. |
| RDP_NEG_FAILURE | The RDP Negotiation Failure structure is used by a server to inform the client of a failure that has occurred while preparing security for the connection. |
| RDP_NEG_REQ | The RDP Negotiation Request structure is used by a client to advertise the security protocols which it supports. |
| RDP_NEG_RSP | The RDP Negotiation Response structure is used by a server to inform the client of the security protocol which it has selected to use for the connection. |
| RDP_NETCHAR_RESULT | The RDP_NETCHAR_RESULTS structure is used by the server to send detected network characteristics to the client. |
| RDP_NETCHAR_SYNC | The RDP_NETCHAR_SYNC structure is sent in response to the RTT Measure Request (section 2.2.14.1.1) message or Bandwidth Measure Start (section 2.2.14.1.2) message and is used to short-circuit connect-time network characteristics detection in the case of an auto-reconnect (section 1.3.1.5 and 2.2.4). |
| RDP_RTT_REQUEST | The RDP_RTT_REQUEST structure is used to initiate a round-trip time measurement operation. |
| RDP_RTT_RESPONSE | The RDP_RTT_RESPONSE structure is used to respond to round-trip time measurement operations initiated by the RTT Measure Request (section 2.2.14.1.1) message. |
| RDP_SERVER_REDIRECTION_PACKET | |
| RSA_PUBLIC_KEY | The structure used to describe a public key in a Proprietary Certificate. |
| RdpbcgrClientPdu | A type of PDU to indicate the PDU is a RDPBCGR PDU. It's a base class for all input/output PDUs. |
| RdpbcgrDecoder | MS-RDPBCGR Decoder Class |
| RdpbcgrServerDecoder | MS-RDPBCGR Server Decoder Class |
| RdpbcgrServerPdu | |
| RdpbcgrServerSessionContext | Maintain the important parameters of the session during RDPBCGR transport, including the main sent or received PDUs, Channel Manager, the selected Encryption Algorithm etc. |
| RdpelePdu | This type of PDU is RDPELE PDU. It is especially used for RDPELE which is based on RDPBCGR. |
| SERVER_CERTIFICATE | The SERVER_CERTIFICATE structure describes the generic server certificate structure to which all server certificates present in the Server Security Data conform. |
| Server_Auto_Detect_Request_PDU | The Auto-Detect Request PDU is sent by the server to the client and is used to detect network characteristics such as bandwidth and round-trip time. |
| Server_Auto_Reconnect_Status_Pdu | The Auto-Reconnect Status PDU contains error information after a failed auto-reconnection attempt has taken place. |
| Server_Control_Pdu | The Server Control PDU includes Cooperate and Granted Control. |
| Server_Control_Pdu_Cooperate | The Server Control PDU (Cooperate) is a Standard RDP Connection Sequence PDU sent from server to client during the Connection Finalization phase (see section ). It is sent after transmitting the Server Synchronize PDU. |
| Server_Deactivate_All_Pdu | The Deactivate All PDU is sent from server to client to indicate that the connection will be dropped or that a capability renegotiation using a Deactivation-Reactivation Sequence (see section ) will occur. |
| Server_Demand_Active_Pdu | The Demand Active PDU is a Standard RDP Connection Sequence PDU sent from server to client during the Capabilities Negotiation phase (see section ). It is sent upon successful completion of the Licensing phase (see section ) of the connection sequence. |
| Server_Font_Map_Pdu | The Font Map PDU is a Standard RDP Connection Sequence PDU sent from server to client during the Connection Finalization phase (see section ). It is sent after transmitting the Server Control PDU (Granted Control). This PDU is the last in the connection sequence and signals to the client that it can start sending input PDUs (see section ) to the server. |
| Server_Heartbeat_PDU | The Heartbeat PDU is sent by the server to the client and allows the client to monitor the state of the connection to the server in real time. |
| Server_Initiate_Multitransport_Request_PDU | The Initiate Multitransport Request PDU is sent by the server to the client and is used to bootstrap the creation of a side-band channel ([MS-RDPEMT] section 1.3). |
| Server_License_Error_Pdu_Valid_Client | The License Error (Valid Client) PDU is a Standard RDP Connection Sequence PDU sent from server to client during the Licensing phase (see section ). This licensing PDU indicates that the server will not issue the client a license to store and that the Licensing Phase has ended successfully. This is one possible message that may be sent during the Licensing Phase (see [MS-RDPELE] for a detailed discussion of the Remote Desktop Protocol: Licensing Extension). |
| Server_MCS_Attach_User_Confirm_Pdu | The MCS Attach User Confirm PDU is an RDP Connection Sequence PDU sent from server to client during the Channel Connection phase (see section 1.3.1.1). It is sent as a response to the MCS Attach User Request PDU (section 2.2.1.6). |
| Server_MCS_Channel_Join_Confirm_Pdu | The MCS Channel Join Confirm PDU is an RDP Connection Sequence PDU sent from server to client during the Channel Connection phase (see section 1.3.1.1). It is sent as a response to the MCS Channel Join Request PDU (section 2.2.1.8). |
| Server_MCS_Connect_Response_Pdu_with_GCC_Conference_Create_Response | |
| Server_Play_Sound_Pdu | The Play Sound PDU instructs the client to play a "beep" sound. |
| Server_Redirection_Pdu | The Standard Security Server Redirection PDU is sent by the server to the client to instruct it to reconnect to an existing session on another server. The information required to perform the reconnection is contained in an embedded Server Redirection Packet (see section 2.2.13.1). This PDU MUST NOT be sent if Enhanced RDP Security (see section 5.4) is in effect. |
| Server_Save_Session_Info_Pdu | The Save Session Info PDU is used by the server to transmit session and user logon information back to the client after the user has logged on. |
| Server_Set_Error_Info_Pdu | The Set Error Info PDU is sent by the server when there is a connection or disconnection failure. This PDU is only sent to clients which have indicated that they are capable of handling error reporting using the RNS_UD_CS_SUPPORT_ERRINFO_PDU flag in the Client Core Data. |
| Server_Set_Keyboard_IME_Status_Pdu | The Set Keyboard IME Status PDU is sent by the server when the user session employs input method editors (IMEs) and is used to set the IME state. This PDU is accepted and ignored by non-IME aware clients. |
| Server_Set_Keyboard_Indicators_Pdu | The Set Keyboard Indicators PDU is sent by the server to synchronize the state of the keyboard toggle keys (Scroll Lock, Num Lock, and so on). It is similar in operation to the Client Synchronize Input Event Notification (see sections and ), but flows in the opposite direction. |
| Server_Shutdown_Request_Denied_Pdu | The Shutdown Request Denied PDU is sent by the server as part of the disconnection sequences specified in section ; specifically as part of the "User-Initiated on Client" disconnect sequence (see section ). |
| Server_Status_Info_Pdu | The Status Info PDU is sent by the server to update the client with status information. This PDU is only sent to clients that have indicated that they are capable of status updates using the RNS_UD_CS_SUPPORT_STATUSINFO_PDU flag in the Client Core Data (section 2.2.1.3.2). |
| Server_Synchronize_Pdu | The Server Synchronize PDU is a Standard RDP Connection Sequence PDU sent from server to client during the Connection Finalization phase (see section ). It is sent after receiving the Confirm Active PDU. |
| Server_X_224_Connection_Confirm_Pdu | The X.224 Connection Confirm PDU is a Standard RDP Connection Sequence PDU sent from server to client during the Connection Initiation phase (see section ). It is sent as a response to the X.224 Connection Request PDU. |
| Server_X_224_Negotiate_Failure_Pdu | The RDP Negotiation Failure structure is used by a server to inform the client of a failure that has occurred while preparing security for the connection. |
| SlowPathOutputPdu | Slow path output PDU, including Graphics PDU and Pointer PDU. |
| SlowPathPduCommonHeader | A slow path header for input/output PDUs. |
| StaticVirtualChannel | Base class for Static Virtual Channel |
| StaticVirtualChannelName | |
| TARGET_NET_ADDRESS | The Target Net Address structure holds a Unicode text representation of an IP address. |
| TARGET_NET_ADDRESSES | The TARGET_NET_ADDRESSES structure is used to hold a collection of IP addresses in Unicode format. |
| TS_AUTORECONNECT_STATUS_PDU | The TS_AUTORECONNECT_STATUS_PDU structure contains the contents of the Auto-Reconnect Status PDU, which is a Share Data Header with a status field. |
| TS_BITMAPCACHE_CAPABILITYSET | The TS_BITMAPCACHE_CAPABILITYSET structure is used to advertise support for Revision 1 Bitmap Caches (see [MS-RDPEGDI] section 3.1.1.1.1). This capability is only sent from client to server. In addition to specifying bitmap caching parameters in the Revision 1 Bitmap Cache Capability Set, a client MUST also support the MemBlt and Mem3Blt Primary Drawing Orders (see [MS-RDPEGDI] sections 2.2.2.2.1.1.2.9 and 2.2.2.2.1.1.2.10 respectively) in order to receive the Cache Bitmap (Revision 1) Secondary Drawing Order (see [MS-RDPEGDI] section 2.2.2.2.1.2.2). |
| TS_BITMAPCACHE_CAPABILITYSET_REV2 | The TS_BITMAPCACHE_CAPABILITYSET_REV2 structure is used to advertise support for Revision 2 Bitmap Caches (see [MS-RDPEGDI] section 3.1.1.1.1). This capability is only sent from client to server. In addition to specifying bitmap caching parameters in the Revision 2 Bitmap Cache Capability Set, a client MUST also support the MemBlt and Mem3Blt Primary Drawing Orders (see [MS-RDPEGDI] sections 2.2.2.2.1.1.2.9 and 2.2.2.2.1.1.2.10 respectively) in order to receive the Cache Bitmap (Revision 2) Secondary Drawing Order (see [MS-RDPEGDI] section 2.2.2.2.1.2.3). |
| TS_BITMAPCACHE_CELL_CACHE_INFO | The TS_BITMAPCACHE_CELL_CACHE_INFO structure contains information about a bitmap cache on the client. |
| TS_BITMAPCACHE_HOSTSUPPORT_CAPABILITYSET | The TS_BITMAPCACHE_HOSTSUPPORT_CAPABILITYSET structure is used to advertise support for persistent bitmap caching (see [MS-RDPEGDI] section 3.1.1.1.1). This capability set is only sent from server to client. |
| TS_BITMAPCACHE_PERSISTENT_LIST_ENTRY | The TS_BITMAPCACHE_PERSISTENT_LIST_ENTRY structure contains a 64-bit bitmap key to be sent back to the server. |
| TS_BITMAPCACHE_PERSISTENT_LIST_PDU | The TS_BITMAPCACHE_PERSISTENT_LIST_PDU structure contains a list of cached bitmap keys saved from Cache Bitmap (Revision 2) Orders (see [MS-RDPEGDI] section 2.2.2.3.1.2.3) which were sent in previous sessions. By including a key in the Persistent Key List PDU Data the client indicates to the server that it has a local copy of the bitmap associated with the key, which implies that the server does not need to retransmit the bitmap to the client (for more details about the Persistent Bitmap Cache, see [MS-RDPEGDI] section 3.1.1.1.1). The bitmap keys can be sent in more than one Persistent Key List PDU, with each PDU being marked using flags in the bBitMask field. |
| TS_BITMAPCODEC | The TS_BITMAPCODEC structure is used to describe the encoding parameters of a bitmap codec. |
| TS_BITMAPCODECS | The TS_BITMAPCODECS structure contains an array of bitmap codec capabilities. |
| TS_BITMAPCODECS_CAPABILITYSET | The TS_BITMAPCODECS_CAPABILITYSET structure advertises support for bitmap encoding and decoding codecs used in conjunction with the Set Surface Bits Surface Command (section 2.2.9.2.1) and Cache Bitmap (Revision 3) Secondary Drawing Order ([MS-RDPEGDI] section 2.2.2.2.1.2.8). This capability is sent by both the client and server. |
| TS_BITMAPCODEC_GUID | The GUID structure contains 128 bits that represent a globally unique identifier that can be used to provide a distinctive reference number. |
| TS_BITMAP_CAPABILITYSET | The TS_BITMAP_CAPABILITYSET structure is used to advertise bitmap-orientated characteristics and is based on the capability set specified in [T128] section 8.2.4. This capability is sent by both client and server. |
| TS_BITMAP_DATA | The TS_BITMAP_DATA structure wraps the bitmap data bytestream for a screen area rectangle containing a clipping taken from the server-side screen frame buffer. |
| TS_BITMAP_DATA_EX | The TS_BITMAP_DATA_EX structure is used to encapsulate encoded bitmap data. |
| TS_BRUSH_CAPABILITYSET | The TS_BRUSH_CAPABILITYSET advertises client brush support. This capability is only sent from client to server. |
| TS_CACHEDPOINTERATTRIBUTE | The TS_CACHEDPOINTERATTRIBUTE structure is used to instruct the client to change the current pointer shape to one already present in the pointer cache. |
| TS_CACHE_DEFINITION | The TS_CACHE_DEFINITION structure specifies details about a particular cache in the Glyph Capability Set structure. |
| TS_CAPS_SET | The TS_CAPS_SET structure is used to describe the type and size of a capability set exchanged between clients and servers. All capability sets conform to this basic structure (see section ). |
| TS_CD_HEADER | The TS_CD_HEADER structure is used to describe compressed bitmap data. |
| TS_COLORCACHE_CAPABILITYSET | Color Table Cache Capability Set (see [MS-RDPEGDI] section 2.2.1.1) |
| TS_COLORPOINTERATTRIBUTE | The TS_COLORPOINTERATTRIBUTE structure represents a regular T.128 24 bits-per-pixel color pointer, as specified in [T128] section 8.14.3. This pointer update is used for both monochrome and color pointers in RDP. |
| TS_COMPDESK_CAPABILITYSET | |
| TS_COMPRESSED_BITMAP_HEADER_EX | |
| TS_CONFIRM_ACTIVE_PDU | The TS_CONFIRM_ACTIVE_PDU structure is a standard T.128 Confirm Active PDU (see [T128] section 8.4.1). |
| TS_CONTROL_CAPABILITYSET | The TS_CONTROL_CAPABILITYSET structure is used by the client to advertise control capabilities and is fully described in [T128] section 8.2.10. This capability is only sent from client to server and the server ignores its contents. |
| TS_CONTROL_PDU | |
| TS_DEACTIVATE_ALL_PDU | The TS_DEACTIVATE_ALL_PDU structure is a standard T.128 Deactivate All PDU (see [T128] section 8.4.1). |
| TS_DEMAND_ACTIVE_PDU | The TS_DEMAND_ACTIVE_PDU structure is a standard T.128 Demand Active PDU (see [T128] section 8.4.1). |
| TS_DRAWGRIDPLUS_CAPABILITYSET | Draw GDI+ Cache Capability Set ([MS-RDPEGDI] section 2.2.1.3) |
| TS_DRAWNINEGRIDCACHE_CAPABILITYSET | DrawNineGrid Cache Capability Set ([MS-RDPEGDI] section 2.2.1.2) |
| TS_EXTENDED_INFO_PACKET | The TS_EXTENDED_INFO_PACKET structure contains user information specific to RDP 5.0, RDP 5.1, and RDP 5.2. |
| TS_FONT_CAPABILITYSET | The TS_FONT_CAPABILITYSET structure is used to advertise font support options. This capability is sent by both client and server. |
| TS_FONT_LIST_PDU | The TS_FONT_LIST_PDU structure contains information that is sent to the server for legacy reasons. |
| TS_FONT_MAP_PDU | The TS_FONT_MAP_PDU structure contains information that is sent to the server for legacy reasons. |
| TS_FP_CACHEDPOINTERATTRIBUTE | The TS_FP_CACHEDPOINTERATTRIBUTE structure is the fast-path variant of the TS_CACHEDPOINTERATTRIBUTE structure. |
| TS_FP_COLORPOINTERATTRIBUTE | The TS_FP_COLORPOINTERATTRIBUTE structure is the fast-path variant of the TS_COLORPOINTERATTRIBUTE structure. |
| TS_FP_FIPS_INFO | The TS_FP_FIPS_INFO structure contains fast-path information for inclusion in a fast-path header. |
| TS_FP_INPUT_EVENT | The TS_FP_INPUT_EVENT structure is used to describe the type and encapsulate the data for a fast-path input event sent from client to server. All fast-path input events conform to this basic structure (see sections to ). |
| TS_FP_INPUT_PDU | Fast-path revises client input packets from the first byte with the goal of improving bandwidth. The TPKT (see [T123]), X.224 (see [X224]) and MCS SDrq (see [T125]) headers are replaced, the Security Header is collapsed into the fast-path input header, and the Share Data Header is replaced by a new fast-path format. The contents of the input notification events (see section ) are also changed to reduce their size, particularly by removing or reducing headers. Support for fast-path input is advertised in the Input Capability Set. |
| TS_FP_KEYBOARD_EVENT | |
| TS_FP_POINTERATTRIBUTE | The TS_FP_POINTERATTRIBUTE structure is the fast-path variant of the TS_POINTERATTRIBUTE structure. |
| TS_FP_POINTERPOSATTRIBUTE | The TS_FP_POINTERPOSATTRIBUTE structure is the fast-path variant of the TS_POINTERPOSATTRIBUTE structure (see section ). |
| TS_FP_POINTERX_EVENT | |
| TS_FP_POINTER_EVENT | |
| TS_FP_SURFCMDS | The TS_FP_SURFCMDS structure is the fast-path variant of the TS_UPDATE_SURFCMDS (section 2.2.9.1.1.3.1.4) structure. |
| TS_FP_UNICODE_KEYBOARD_EVENT | |
| TS_FP_UPDATE | The TS_FP_UPDATE structure is used to describe and encapsulate the data for a fast-path update sent from server to client. All fast-path updates conform to this basic structure (see sections to ). |
| TS_FP_UPDATE_BITMAP | The TS_FP_UPDATE_BITMAP structure is the fast-path variant of the TS_UPDATE_BITMAP_PDU_DATA structure. |
| TS_FP_UPDATE_ORDERS | Indicates a Fast-Path Orders Update (see [MS-RDPEGDI] section 2.2.2.3). |
| TS_FP_UPDATE_PALETTE | The TS_FP_UPDATE_PALETTE structure is the fast-path variant of the TS_UPDATE_PALETTE_PDU_DATA structure. |
| TS_FP_UPDATE_PDU | Fast-path revises server output packets from the first byte with the goal of improving bandwidth. The TPKT (see [T123]), X.224 (see [X224]) and MCS SDin (see [T125]) headers are replaced, the Security Header is collapsed into the fast-path output header, and the Share Data Header is replaced by a new fast-path format. The contents of the graphics and pointer updates (see sections and ) are also changed to reduce their size, particularly by removing or reducing headers. Support for fast-path output is advertised in the General Capability Set. |
| TS_FRAME_ACKNOWLEDGE_CAPABILITYSET | The TS_FRAME_ACKNOWLEDGE_CAPABILITYSET structure advertises support for frame acknowledgment using the TS_FRAME_ACKNOWLEDGE_PDU (section 2.2.3.1) structure. |
| TS_FRAME_ACKNOWLEDGE_PDU | The TS_FRAME_ACKNOWLEDGE_PDU structure is a client-to-server PDU sent to the server whenever the client receives a Frame Marker Command ([MS-RDPBCGR] section 2.2.9.2.3) with the frameAction field set to SURFACECMD_FRAMEACTION_END (0x0001) and it has finished processing this particular frame (that is, the surface bits have been rendered on the screen). |
| TS_FRAME_MARKER | The Frame Marker Command is used to group multiple surface commands so that these commands can be processed and presented to the user as a single entity, a frame. |
| TS_GENERAL_CAPABILITYSET | The TS_GENERAL_CAPABILITYSET structure is used to advertise general characteristics and is based on the capability set specified in [T128] section 8.2.3. This capability is sent by both client and server. |
| TS_GLYPHCACHE_CAPABILITYSET | The TS_GLYPHCACHE_CAPABILITYSET structure advertises the glyph support level and associated cache sizes. This capability is only sent from client to server. |
| TS_INFO_PACKET | The TS_INFO_PACKET structure contains extra information not passed to the server during the Basic Settings Exchange phase (see section ) of the Standard RDP Connection Sequence, primarily to ensure that it gets encrypted (as auto-logon password data and other sensitive information is passed here). |
| TS_INPUT_CAPABILITYSET | The TS_INPUT_CAPABILITYSET structure is used to advertise support for input formats and devices. This capability is sent by both client and server. |
| TS_INPUT_EVENT | The TS_INPUT_EVENT structure is used to wrap event-specific information for all slow-path input events. |
| TS_INPUT_PDU | The slow-path Input Event PDU is used to transmit input events from client to server. |
| TS_KEYBOARD_EVENT | |
| TS_LARGE_POINTER_CAPABILITYSET | |
| TS_LOGON_ERRORS_INFO | The TS_LOGON_ERRORS_INFO structure contains information which describes a logon error notification. |
| TS_LOGON_INFO | TS_LOGON_INFO is a fixed-length structure which contains logon information intended for the client. |
| TS_LOGON_INFO_EXTENDED | |
| TS_LOGON_INFO_FIELD | The TS_LOGON_INFO_FIELD is used to encapsulate extended logon information field data of variable length. |
| TS_LOGON_INFO_VERSION_2 | TS_LOGON_INFO_VERSION_2 is a variable length structure which contains logon information intended for the client. |
| TS_MONITOR_ATTRIBUTES | The TS_MONITOR_ATTRIBUTES packet describes extended attributes of a client-side display monitor. |
| TS_MONITOR_DEF | The TS_MONITOR_DEF packet describes the configuration of a client-side display monitor. The x and y coordinates used to describe the monitor position MUST be relative to the upper-left corner of the monitor designated as the "primary display monitor" (this implies that the upper-left corner of the primary monitor is always (0, 0)). |
| TS_MONITOR_LAYOUT_PDU | The Monitor Layout PDU is used by the server to notify the client of the monitor layout in the session on the remote server. |
| TS_MULTIFRAGMENTUPDATE_CAPABILITYSET | The TS_MULTIFRAGMENTUPDATE_CAPABILITYSET structure is used to specify capabilities related to the fragmentation and reassembly of Fast-Path Updates (see section ). This capability is sent by both client and server. |
| TS_OFFSCREEN_CAPABILITYSET | The TS_OFFSCREEN_CAPABILITYSET structure is used to advertise support for off-screen bitmap caching (see [MS-RDPEGDI] section 3.1.1.1.5). This capability is only sent from client to server. |
| TS_ORDER_CAPABILITYSET | The TS_ORDER_CAPABILITYSET structure advertises support for primary drawing order-related capabilities and is based on the capability set specified in [T128] section 8.2.5 (for more information about primary drawing orders, see [MS-RDPEGDI] section ). This capability is sent by both client and server. |
| TS_PALETTE_ENTRY | The TS_PALETTE_ENTRY structure is used to express the red, green and blue components necessary to reproduce a color in the additive RGB space. |
| TS_PLAIN_NOTIFY | The TS_PLAIN_NOTIFY is a fixed-length structure which contains 576 bytes of padding. |
| TS_PLAY_SOUND_PDU_DATA | The TS_PLAY_SOUND_PDU_DATA structure contains the contents of the Play Sound PDU, which is a Share Data Header and two fields. |
| TS_POINT16 | The TS_POINT16 structure specifies a point relative to the top-left corner of the server's virtual desktop. |
| TS_POINTERATTRIBUTE | The TS_POINTERATTRIBUTE structure is used to send pointer data at an arbitrary color depth. Support for the New Pointer Update is advertised in the Pointer Capability Set. |
| TS_POINTERPOSATTRIBUTE | The TS_POINTERPOSATTRIBUTE structure is used to indicate that the client pointer should be moved to the specified position relative to the top-left corner of the server's virtual desktop (see [T128] section 8.14.4). |
| TS_POINTERX_EVENT | |
| TS_POINTER_CAPABILITYSET | |
| TS_POINTER_EVENT | |
| TS_POINTER_PDU | The Pointer Update PDU is sent from server to client and is used to convey pointer information, including pointers' bitmap images, use of system or hidden pointers, use of cached cursors and position updates. |
| TS_RAIL_CAPABILITYSET | Remote Programs Capability Set ([MS-RDPERP] section 2.2.1.1.1) |
| TS_RECTANGLE16 | The TS_RECTANGLE16 structure describes a rectangle expressed in inclusive coordinates (the right and bottom coordinates are included in the rectangle bounds). |
| TS_REFRESH_RECT_PDU | The TS_REFRESH_RECT_PDU structure contains the contents of the Refresh Rect PDU, which is a Share Data Header and two fields. |
| TS_SAVE_SESSION_INFO_PDU_DATA | The TS_SAVE_SESSION_INFO_PDU_DATA structure is a wrapper around different classes of user logon information. |
| TS_SECURITY_HEADER | The TS_SECURITY_HEADER structure is attached to server-to-client traffic when the Encryption Level selected by the server (see sections and ) is ENCRYPTION_LEVEL_LOW (1). |
| TS_SECURITY_HEADER1 | The TS_SECURITY_HEADER1 structure is attached to all client-to-server traffic when the Encryption Level selected by the server (see sections and ) is ENCRYPTION_LEVEL_LOW (1), ENCRYPTION_LEVEL_CLIENT_COMPATIBLE (2) or ENCRYPTION_LEVEL_HIGH (3). It is attached to all server-to-client traffic when the Encryption Level is ENCRYPTION_LEVEL_CLIENT_COMPATIBLE (2) or ENCRYPTION_LEVEL_HIGH (3). |
| TS_SECURITY_HEADER2 | The TS_SECURITY_HEADER2 structure is attached to all traffic when the Encryption Level selected by the server (see sections and ) is ENCRYPTION_LEVEL_FIPS (4). |
| TS_SECURITY_PACKET | The TS_SECURITY_PACKET structure contains the encrypted client random value which is used together with the server random (see section ) to derive session keys to secure the connection (see sections and ). |
| TS_SET_ERROR_INFO_PDU | The TS_SET_ERROR_INFO_PDU structure contains the contents of the Set Error Info PDU, which is a Share Data Header with an error value field. |
| TS_SET_KEYBOARD_IME_STATUS_PDU | The TS_SET_KEYBOARD_IME_STATUS_PDU structure contains the actual contents of the Set Keyboard IME Status PDU. On RDP 5.0 and later clients the latter two fields are used as input parameters to a Fujitsu Oyayubi specific IME control function of East Asia IME clients. |
| TS_SET_KEYBOARD_INDICATORS_PDU | The TS_SET_KEYBOARD_INDICATORS_PDU structure contains the actual contents of the Set Keyboard Indicators PDU. The contents of the LedFlags field is identical to the flags used in the Client Synchronize Input Event Notification (see section ). |
| TS_SHARECONTROLHEADER | |
| TS_SHAREDATAHEADER | |
| TS_SHARE_CAPABILITYSET | The TS_SHARE_CAPABILITYSET structure is used to advertise the channel ID of the sender and is fully specified in [T128] section 8.2.12. This capability is sent by both client and server. |
| TS_SHUTDOWN_DENIED_PDU | The TS_SHUTDOWN_DENIED_PDU structure contains the contents of the Shutdown Request Denied PDU, which is a Share Data Header with no PDU body. |
| TS_SHUTDOWN_REQ_PDU | The TS_SHUTDOWN_REQ_PDU structure contains the contents of the Shutdown Request PDU, which is a Share Data Header with no PDU body. |
| TS_SOUND_CAPABILITYSET | The TS_SOUND_CAPABILITYSET structure advertises the ability to play a "beep" sound. This capability is only sent from client to server. |
| TS_SUPPRESS_OUTPUT_PDU | The TS_SUPPRESS_OUTPUT_PDU structure contains the contents of the Suppress Output PDU, which is a Share Data Header and two fields. |
| TS_SURFCMD | The TS_SURFCMD structure is used to specify the Surface Command type and to encapsulate the data for a Surface Command sent from a server to a client. All Surface Commands in section 2.2.9.2 conform to this structure. |
| TS_SURFCMDS_CAPABILITYSET | The TS_SURFCMDS_CAPABILITYSET structure advertises support for Surface Commands (section 2.2.9.2). This capability is sent by both the client and the server. |
| TS_SURFCMD_SET_SURF_BITS | The Set Surface Bits Command is used to transport encoded bitmap data destined for a rectangular region of the current target surface from an RDP server to an RDP client. |
| TS_SURFCMD_STREAM_SURF_BITS | The Stream Surface Bits Command is used to transport encoded bitmap data destined for a rectangular region of the current target surface from an RDP server to an RDP client. |
| TS_SYNCHRONIZE_PDU | The TS_SYNCHRONIZE_PDU structure is a standard T.128 Synchronize PDU (see [T128] section 8.6.1). |
| TS_SYNC_EVENT | |
| TS_SYSTEMPOINTERATTRIBUTE | The TS_SYSTEMPOINTERATTRIBUTE structure is used to hide the pointer or to set its shape to that of the operating system default (see [T128] section 8.14.1). |
| TS_SYSTEMTIME | The TS_SYSTEMTIME structure contains a date and local time when the transition occurs between daylight saving time to standard time occurs or standard time to daylight saving time. |
| TS_TIME_ZONE_INFORMATION | The TS_TIME_ZONE_INFORMATION structure contains client time zone information. |
| TS_UD_CS_CLUSTER | The TS_UD_CS_CLUSTER data block is sent by the client to the server either to advertise that it can support the Server Redirection PDU (see [MS_RDPEGDI] section 2.2.3.1) or to request a connection to a given session identifier. |
| TS_UD_CS_CORE | The TS_UD_CS_CORE data block contains core client connection-related information. |
| TS_UD_CS_MCS_MSGCHANNEL | The TS_UD_CS_MCS_MSGCHANNEL packet indicates support for the message channel which is used to transport the Initiate Multitransport Request PDU (section 2.2.15.1). This packet is an Extended Client Data Block and MUST NOT be sent to a server which does not advertise support for Extended Client Data Blocks by using the EXTENDED_CLIENT_DATA_SUPPORTED flag (0x00000001) as described in section 2.2.1.2.1. |
| TS_UD_CS_MONITOR | The TS_UD_CS_MONITOR packet describes the client-side display monitor layout. This packet is an extended client data block and MUST NOT be sent to a server which does not advertise support for extended client data blocks by using the EXTENDED_CLIENT_DATA_SUPPORTED flag (0x00000001) as described in section 2.2.1.2.1. |
| TS_UD_CS_MONITOR_EX | The TS_UD_CS_MONITOR_EX packet describes extended attributes of the client-side display monitor layout defined by the Client Monitor Data block (section 2.2.1.3.6). This packet is an Extended Client Data Block and MUST NOT be sent to a server which does not advertise support for Extended Client Data Blocks by using the EXTENDED_CLIENT_DATA_SUPPORTED flag (0x00000001) as described in section 2.2.1.2.1. |
| TS_UD_CS_MULTITRANSPORT | The TS_UD_CS_MULTITRANSPORT packet is used to indicate support for the RDP Multitransport Layer ([MS-RDPEMT] section 1.3) and to specify multitransport characteristics. This packet is an Extended Client Data Block and MUST NOT be sent to a server which does not advertise support for Extended Client Data Blocks by using the EXTENDED_CLIENT_DATA_SUPPORTED flag (0x00000001) as described in section 2.2.1.2.1. |
| TS_UD_CS_NET | The TS_UD_CS_NET packet contains a list of requested virtual channels. |
| TS_UD_CS_SEC | The TS_UD_CS_SEC data block contains security-related information used to advertise client cryptographic support. This information is only relevant when Standard RDP Security is in effect, as opposed to Enhanced RDP Security. See sections and for a detailed discussion of how this information is used. |
| TS_UD_HEADER | The TS_UD_HEADER precedes all data blocks in the client and server GCC user data. |
| TS_UD_SC_CORE | The TS_UD_SC_CORE data block contains core server connection-related information. |
| TS_UD_SC_MCS_MSGCHANNEL | The TS_UD_SC_MCS_MSGCHANNEL packet is used to specify the ID of the MCS channel which transports the Initiate Multitransport Request PDU (section 2.2.15.1). |
| TS_UD_SC_MULTITRANSPORT | The TS_UD_CS_MULTITRANSPORT packet is used to indicate support for the RDP Multitransport Layer ([MS-RDPEMT] section 1.3) and to specify multitransport characteristics. |
| TS_UD_SC_NET | The TS_UD_SC_NET data block is a reply to the static virtual channel list presented in the Client Network Data structure. |
| TS_UD_SC_SEC1 | The TS_UD_SC_SEC1 data block returns negotiated security-related information to the client. See sections and for a detailed d discussion of how this information is used. |
| TS_UNICODE_KEYBOARD_EVENT | |
| TS_UNUSED_EVENT | |
| TS_UPDATE_BITMAP | The TS_UPDATE_BITMAP_PDU_DATA structure contains one or more rectangular clippings taken from the server-side screen frame buffer (see [T128] section 8.17). |
| TS_UPDATE_BITMAP_DATA | The TS_UPDATE_BITMAP_DATA structure encapsulates the bitmap data that defines a Bitmap Update (section 2.2.9.1.1.3.1.2). |
| TS_UPDATE_ORDERS | Indicates an Orders Update (see [MS-RDPEGDI] section 2.2.2.2). |
| TS_UPDATE_PALETTE | The TS_UPDATE_PALETTE_PDU_DATA structure contains global palette information that covers the entire session's palette (see [T128] section 8.18.6). |
| TS_UPDATE_PALETTE_DATA | The TS_UPDATE_PALETTE_DATA encapsulates the palette data that defines a Palette Update (section 2.2.9.1.1.3.1.1). |
| TS_UPDATE_SURFCMDS | The TS_UPDATE_SURFCMDS structure encapsulates one or more Surface Command (section 2.2.9.1.1.3.1.4.1) structures. |
| TS_UPDATE_SYNC | The TS_UPDATE_SYNC_PDU_DATA structure is an artifact of the T.128 protocol (see [T128] section 8.6.2) and is ignored by current Microsoft RDP client implementations. |
| TS_VIRTUALCHANNEL_CAPABILITYSET | The TS_VIRTUALCHANNEL_CAPABILITYSET structure is used to advertise virtual channel support characteristics. This capability is sent by both client and server. |
| TS_WINDOWACTIVATION_CAPABILITYSET | The TS_WINDOWACTIVATION_CAPABILITYSET structure is used by the client to advertise window activation characteristics capabilities and is fully specified in [T128] section 8.2.9. This capability is only sent from client to server and the server ignores its contents. |
| TS_WINDOW_CAPABILITYSET | Window List Capability Set ([MS-RDPERP] section 2.2.1.1.2) |
| TpktHeader | A TPKT packet Header. |
| UInt16Class | A class wraps UInt16. This class is used especially for some optional integer fields. To set it null means not the field of this type will not present, or else it is present. |
| UInt32Class | A class wraps UInt32. This class is used especially for some optional integer fields. To set it null means not the field of this type will not present, or else it is present. |
| UpdateSessionKeyPdu | A type of PDU to indicate the session key should be updated. |
| Virtual_Channel_Complete_Pdu | The Virtual Channel PDU is sent from client to server or from server to client and is used to transport data between static virtual channel end-points. |
| Virtual_Channel_Complete_Server_Pdu | The Virtual Channel PDU is sent from client to server or from server to client and is used to transport data between static virtual channel end-points. |
| Virtual_Channel_RAW_Pdu | The Virtual Channel PDU is sent from client to server or from server to client and is used to transport data between static virtual channel end-points. |
| Virtual_Channel_RAW_Server_Pdu | The Virtual Channel PDU is sent from client to server or from server to client and is used to transport data between static virtual channel end-points. |
| X224 | A common x224 header. |
| X224Ccf | |
| X224Crq | |
| X509_CERTIFICATE_CHAIN | The X.509 Certificate Chain packet contains a collection of X.509 certificates. |
| nested_TS_FP_INPUT_EVENT_eventHeader | |
| nested_TS_FP_INPUT_PDU_fpInputHeader | |
| nested_TS_SHARECONTROLHEADER_pduType |
