Revision Summary Date Revision History Revision Comments 7/20/2007 0.1 Major MCPP Milestone 5 Initial Availability 9/28/2007 1.0 Major Updated and revised the technical content. 10/23/2007 1.1 Minor Clarified the meaning of the technical content. 11/30/2007 1.2 Clarified the meaning of the technical content. 1/25/2008 1.2.1 Editorial Changed language and formatting in the technical content. 3/14/2008 1.2.2 Editorial Changed language and formatting in the technical content. 5/16/2008 1.2.3 Editorial Changed language and formatting in the technical content. 6/20/2008 1.3 Minor Clarified the meaning of the technical content. 7/25/2008 1.4 Minor Clarified the meaning of the technical content.
8/29/2008 1.4.1 Editorial Changed language and formatting in the technical content. 10/24/2008 1.5 Minor Clarified the meaning of the technical content. 12/5/2008 1.6 Minor Clarified the meaning of the technical content. 1/16/2009 1.6.1 Editorial Changed language and formatting in the technical content. 2/27/2009 1.6.2 Editorial Changed language and formatting in the technical content. 4/10/2009 1.6.3 Editorial Changed language and formatting in the technical content. 5/22/2009 1.7 Minor Clarified the meaning of the technical content. 7/2/2009 1.7.1 Editorial Changed language and formatting in the technical content. 8/14/2009 1.7.2 Editorial Changed language and formatting
in the technical content. 9/25/2009 1.8 Minor Clarified the meaning of the technical content. 11/6/2009 2.0 Major Updated and revised the technical content. 12/18/2009 2.0.1 Editorial Changed language and formatting in the technical content. 1/29/2010 2.1 Minor Clarified the meaning of the technical content. 3/12/2010 2.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 2.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 2.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 2.1.3 None No changes to the meaning, language, or formatting of the
technical content. 6/17/2011 4.1 Minor Clarified the meaning of the technical content. 9/23/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 5.0 Major Updated and revised the technical content. 3/30/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the
technical content. 6/1/2017 8.0 Major Significantly changed the technical content. 9/15/2017 9.0 Major Significantly changed the technical content. 12/1/2017 9.0 None No changes to the meaning, language, or formatting of the technical content.
The PacketId MUST be set to PAKID_CORE_DEVICE_IOCOMPLETION. For the DR_DEVICE_IOCOMPLETION header: The CompletionId MUST be set to match the CompletionId field from the corresponding I/O request (section ). The DeviceId field MUST be set to match the corresponding DeviceId field from the I/O request. The IoStatus MUST be set to the NTSTATUS value indicating the result of the operation. NTSTATUS codes are specified in section 2.3. Sending a Printer Close Response Message The client MUST fill out the various members of the DR_DEVICE_IOCOMPLETION message (as specified in section 2.2.1.5) as here. For the RDPDR_HEADER: The Component MUST be set to RDPDR_CTYP_CORE. The PacketId field MUST be set to PAKID_CORE_DEVICE_IOCOMPLETION. For the DR_DEVICE_IOCOMPLETION header: The CompletionId field MUST be set to match the CompletionId field from the corresponding I/O request (section ). The DeviceId MUST be set to match the corresponding DeviceId from the I/O request. The IoStatus field MUST be set to the NTSTATUS value indicating the result of the operation. NTSTATUS codes are specified in section 2.3. Sending a Printer Write Response Message The client MUST fill out the various members of the DR_DEVICE_IOCOMPLETION message (as specified in section 2.2.1.5) as shown here. For the RDPDR_HEADER: The Component field MUST be set to RDPDR_CTYP_CORE. The PacketId field MUST be set to PAKID_CORE_DEVICE_IOCOMPLETION. For the DR_DEVICE_IOCOMPLETION header: The CompletionId field MUST be set to match the CompletionId field from the corresponding I/O request (section ). The DeviceId field MUST be set to match the corresponding DeviceId field from the I/O request. The IoStatus field MUST be set to the NTSTATUS value indicating the result of the operation. The client MUST set the Length of DR_WRITE_RSP (see [MS-RDPEFS] section 2.2.1.5.4) to the bytes written successfully to the printer device. NTSTATUS codes are specified in section 2.3. Events No timer events are used.
Index A Abstract data model client ( 19, 20) server ( 19, 23) 27 26 8 C 19 8 34 Client abstract data model ( 19, 20) higher-layer triggered events ( 19, 20) initialization ( 19, 20) events ( 20, 23) message processing ( 20, 20) 23 20 sequencing ( 20, 20) timer events ( 20, 23) timers ( 19, 20) Client printer 30 26 30 30 9 9 D Data model - abstract client ( 19, 20) server ( 19, 23) 9 28 27 12 29 17 30 18 29 16 30 17 28 14 26 10 28 15 27 14 27 12 29 17 30 18 E 26 F 8 G 6 H Higher-layer triggered events client ( 19, 20) server ( 19, 23) I 32 32 7 Initialization client ( 19, 20) server ( 19, 23) 6 L Local events client ( 20, 23) server ( 20, 25) M Message processing client ( 20, 20) server ( 20, 23) Messages 9 9 9 10 9 9 N 7 O Other local events 23 25 7