| Name | Description |
|---|---|
| CAPABILITY_HEADER | This is a header that is embedded in the Server Core Capability Request and Client Core Capability Response. The purpose of this header is to describe capabilities for different device types. |
| CAPABILITY_SET | The CAPABILITY_SET structure is used to describe the type, size, and version of a capability set exchanged between clients and servers. All capability set messages conform to this basic structure. The Capability Message is embedded in the Server Core Capability Request and Client Core Capability Response messages |
| DEVICE_ANNOUNCE | This header is embedded in the Client Device List Announce message. Its purpose is to describe different types of devices. |
| DRIVE_CAPS_SET | This packet is embedded into Server Core Capability Request and Client Core Capability Response messages. It indicates that file system devices are supported. |
| DR_CLOSE_REQ | This header initiates a close request. This message can have different purposes depending on the device for which it is issued. The device type is determined by the DeviceId field in the DR_DEVICE_IOREQUEST header. |
| DR_CLOSE_RSP | This message is a reply to a Device Close Request. |
| DR_CONTROL_REQ | This header initiates a device control request. This message can have different purposes depending on the device for which it is issued. The device type is determined by the DeviceId field in the DR_DEVICE_IOREQUEST header. |
| DR_CONTROL_RSP | A message with this header describes a response to a Device Control Request. |
| DR_CORE_CAPABILITY | |
| DR_CORE_CAPABILITY_REQ | The server announces its capabilities and requests the same from the client. |
| DR_CORE_CAPABILITY_RSP | The server announces its capabilities and requests the same from the client. |
| DR_CORE_CLIENT_ANNOUNCE_RSP | The client replies to the Server Announce Request message. |
| DR_CORE_CLIENT_NAME_REQ | The client announces its machine name. |
| DR_CORE_DEVICELIST_ANNOUNCE_REQ | The client announces the list of devices to redirect on the server. |
| DR_CORE_SERVER_ANNOUNCE_REQ | The server initiates the protocol with this message. |
| DR_CORE_SERVER_CLIENTID_CONFIRM | The server confirms the client ID sent by the client in the Client Announce Reply message. |
| DR_CORE_USER_LOGGEDON | The server announces that it has successfully logged on to the session. |
| DR_CREATE_REQ | This header initiates a create request. This message can have different purposes depending on the device for which it is issued. The device type is determined by the DeviceId field in the DR_DEVICE_IOREQUEST header. |
| DR_CREATE_RSP | A message with this header describes a response to a Device Create Request. |
| DR_DEVICE_IOCOMPLETION | A message with this header indicates that the I/O request is complete. In a Device I/O Response message, a request message is matched to the appropriate Device I/O Request header. There is only one response per request. |
| DR_DEVICE_IOREQUEST | This header is embedded in all server requests on a specific device. |
| DR_READ_REQ | This header initiates a read request. This message can have different purposes depending on the device for which it is issued. The device type is determined by the DeviceId field in the DR_DEVICE_IOREQUEST header. |
| DR_READ_RSP | A message with this header describes a response to a Device Read Request. |
| DR_WRITE_REQ | This header initiates a write request. This message can have different purposes depending on the device for which it is issued. The device type is determined by the DeviceId field in the DR_DEVICE_IOREQUEST header. |
| DR_WRITE_RSP | A message with this header describes a response to a Device Write Request. |
| GENERAL_CAPS_SET | This packet is embedded into Server Core Capability Request and Client Core Capability Response messages. It describes nondevice-specific capabilities. |
| PORT_CAPS_SET | This packet is embedded into Server Core Capability Request and Client Core Capability Response messages. It indicates that parallel and serial port devices are supported. |
| PRINTER_CAPS_SET | This packet is embedded into Server Core Capability Request and Client Core Capability Response messages. It indicates that printer devices are supported. |
| RDPDR_HEADER | This header is present at the beginning of every message in this protocol. The purpose of this header is to describe the type of the message. |
| RdpefsPDU | |
| RdpefsUnknownPdu | |
| SMARTCARD_CAPS_SET | This packet is embedded into Server Core Capability Request and Client Core Capability Response messages. It indicates that smart card devices are supported. |
