Revision Summary Date Revision History Revision Comments 9/23/2011 1.0 New Released new document. 12/16/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 2.0 Major Updated and revised the technical content. 7/12/2012 3.0 Updated and revised the technical content. 10/25/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 4.0 Major Updated and revised the technical content. 11/14/2013 4.0 None No changes to the meaning, language, or formatting of the
technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 9/24/2015 6.0 Major Significantly changed the technical content. 10/16/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 7.0 Major Significantly changed the technical content. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content.
One of the clients has at one shared print queue, so that at least one client is of type SV_TYPE_PRINTQ_SERVER, which is a requirement for this example. Either the client or print server supports the Print System Remote Protocol but not the Print System Asynchronous Remote Protocol .<21> This precondition was chosen to illustrate the use of Print System Remote Protocol.<22> The print client is configured to not use Windows Update to obtain the . This precondition is presented to illustrate the printer driver download from the print server. The printer driver is available from the print server's print$ share. Initial System This example applies in the following initial system state. The print client does not have the printer driver for the print queue. The print client does not have the printer for the printer driver in its local . This state is presented to illustrate printer driver download from the print server. Final System State The print client obtains the list of available print servers and print queues. The print client has downloaded a printer driver for the print queue. Tasks This example is divided into four tasks. Locating a print queue in a workgroup Establishing a connection and registering for notifications Submitting a print job and receiving notifications Unregistering for notifications Task 1: Locating a print queue in a workgroup The following diagram the first part of this example, in which a print client locates a print queue in a workgroup and establishes a connection to the print queue. The sequence is described in the steps that follow the diagram. Figure 20: Print client locating a print queue in a workgroup The message group that is labeled "Locating a print queue in a workgroup" shows how the client enumerates the printers in the workgroup ([MS-RPRN] section 3.1.4.2.1). The following describe task 1 of this example. The print client calls the RpcEnumPrinters method on the print browser server by using the Print System Asynchronous Remote Protocol. It requests whatever level of printer information structure the client requires ([MS-RPRN] section 3.1.4.2.1). The server returns ERROR_INSUFFICIENT_BUFFER and sets the countBytesNeeded parameter to the size that is required to store the requested printer information structures for all shared print queues.
Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 7 Windows 8 Windows Server 2012 Windows 8.1 Windows Server 2012 R2 Windows 10 Windows Server 2016 Windows Server operating system Windows 8.1 Windows Server 2012 R2 Windows 10 Windows Server 2016 Windows Server operating system PSS 2.0 Additional capabilities described in Windows NT 4.0 Windows 2000 Windows XP Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows NT 4.0 Windows 2000 Windows XP Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 7 Windows 8 Windows Server 2012 Windows 8.1 Windows Server 2012 R2 Windows 10 Windows Server 2016 Windows Server operating system The protocol described in is supported including the RpcOpenPrinterEx method, and the OSVERSIONINFO.BuildNumber is less than or equal to 1381.
Windows 7 Windows 8 Windows Server 2012 Windows 8.1 Windows Server 2012 R2 Windows 10 Windows Server 2016 Windows Server operating system PSS 3.0 Windows 2000 Windows XP Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 7 Windows 8 Windows Server 2012 Windows 8.1 Windows Server 2012 R2 Windows 10 Windows 2000 Windows XP Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 7 Windows 8 Windows Server 2012 Windows 8.1 Windows Server 2012 R2 Windows 10 Windows Server 2016 Windows Server operating system OSVERSIONINFO.BuildNumber is greater than 1381 but less than or equal to 3790.
Windows Server 2016 Windows Server operating system PSS 4.0 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Windows Server operating system Windows Vista Windows 7 Windows 8 Windows 8.1 Windows 10 OSVERSIONINFO.BuildNumber is greater than 3790. <10> Section 2.6: This, behavior occurs in implemented in Windows Client operating system versions, except Windows 95, Windows 98, Windows 2000 Professional operating system, Windows Millennium Edition, and Windows XP. <11> Section 2.7.1.1: Windows NT, Windows 95, Windows 98, Windows Millennium Edition, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 do not support this configuration. <12> Section 2.8.3: Windows NT, Windows 95, Windows 98, Windows 2000, Windows Millennium Edition, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 implementations do not show this behavior. <13> Section 2.9.1: This functionality is not supported on Windows NT, Windows 95, Windows 98, and Windows Millennium Edition. <14> Section 3.1: In Windows, print client implementations can satisfy this precondition by disabling the PAR server endpoint on the print server, thus forcing the print server to use the Print System Remote Protocol for communication with the print client. The PAR server endpoint on the print server can be disabled through a setting on the print server. Windows NT, Windows 95, Windows 98, Windows 2000, Windows Millennium Edition, Windows XP, and Windows Vista implementations do not show this behavior. <15> Section 3.1: In Windows, the package aware flag can be set on the printer driver using the registry key "HKLM\System\CurrentControlSet\Control\Print\Environments\<Environment
Locate and establish connection to print queue 43 47 45 M 95 O Overview 11 14 15 29 14 14 11 P 34 data 12 28 13 jobs 83 92 13 queue domain 66 66 85 workgroup 73 73 12 11 11 95 Provisioning print queue 40 R 9 17 Required information print 12 13 13 12 11 11 Requirements coherency 62 62 62 62 60 14 34 14 15 14 S 63 64 64 64 63 64 27 48 28 System dependencies 32 32 32 60 failure scenarios 61 62 61 60 print spooler service 61 61 61 11 background 12 13 13 12 11 11 5 29 requirements 14 14 14 15 use 36 42 37 locate and establish connection to print queue 43 47 45 35 40 48 32 32 32 60 29