2.2.2.1 Client Device List Announce Request

This message is described in [MS-RDPEFS] section 2.2.2.9. The port redirection client generates the elements of type DEVICE_ANNOUNCE (as specified in [MS-RDPEFS] section 2.2.1.3) for the port devices it wants to redirect.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

DeviceAnnounceHeader

DeviceAnnounceHeader (4 bytes): For each redirected port a DEVICE_ANNOUNCE header (as specified in [MS-RDPEFS] section 2.2.1.3) is generated by the client port redirection extension.

The header fields are initialized as follows:

  • DeviceType: Identifies the device. This value MUST be set to RDPDR_DTYP_PARALLEL for parallel ports and RDPDR_DTYP_SERIAL for serial ports.

  • DeviceId: A unique ID that identifies the announced device. The DeviceId field follows the semantics described in [MS-RDPEFS] section 2.2.1.3.

  • PreferredDosName: This field follows the semantic described in [MS-RDPEFS] section 2.2.1.3. It describes the name of the port device as it appears on the client. This protocol does not enforce any semantic limitations on port naming. Client and server implementations determine the port naming convention.<1>

  • DeviceDataLength: Number of bytes in the DeviceData field. For port devices, this value is set to 0.

Note: The Client Drive Device List Remove message is not supported by the MS-RDPESP protocol.