4.1 Product Behavior
<1> Section 1.3.1: Print server implementation is not supported in Windows 95 operating system, Windows 98 operating system, and Windows Millennium Edition operating system.
<2> Section 1.3.2: Print server implementation is not supported in Windows 95, Windows 98, and Windows Millennium Edition.
<3> Section 2.1.2.2.2: RAP is supported on Windows NT operating system, Windows 2000 operating system, Windows XP operating system, Windows Server 2003 operating system, Windows Vista operating system, and Windows Server 2008 operating system.
<4> Section 2.3.2: Windows implementations attempt to locate a driver from the following sources, in this order, when a driver cannot be obtained from the print server:
The Print Store, which is the driver store; or the local driver cabinet file in Windows NT, Windows 2000, Windows XP, and Windows Server 2003.
Windows Update.
<5> Section 2.3.2: The maximally allowed number of shared print queues in a Windows workgroup is 256,
<6> Section 2.3.2: Group Policy settings can be applied to print clients and print servers, except those that are running Windows NT, Windows 95, Windows 98, and Windows Millennium Edition.
<7> Section 2.5.3.8.3: Windows NT, Windows 95, Windows 98, Windows 2000, Windows Millennium Edition, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 print clients and servers support the net print command.
<8> Section 2.6: Print Services system functionality is grouped by version:
PSS 1.0 (Windows NT, Windows 95, Windows 98, and Windows Millennium Edition)
PSS 2.0 (Windows NT)
PSS 3.0 (Windows 2000, Windows Server 2003, Windows XP, and Windows Server 2008)
PSS 4.0 (Windows Vista, Windows Server 2008 R2 operating system, Windows 7 operating system, Windows 8 operating system, Windows Server 2012 operating system, Windows 8.1 operating system, Windows Server 2012 R2 operating system, Windows 10 operating system, Windows Server 2016 operating system, Windows Server operating system, Windows Server 2019 operating system, Windows Server 2022 operating system, and Windows 11 operating system)
<9> Section 2.6: The Print Services system versions described in section 2.6 are supported in Windows releases as noted in the following table.
|
Print Services system version |
Print server release |
Print client release |
Method used by client to determine support level |
|---|---|---|---|
|
PSS 1.0 |
Windows NT 3.1 operating system Windows NT 3.5 operating system Windows NT 3.51 operating system Windows NT 4.0 operating system Windows 2000 Windows XP Windows Server 2003 Windows Server 2003 R2 operating system 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 Server 2019 |
Windows 95 Windows 98 Windows Millennium Edition Windows NT 3.1 Windows NT 3.5 Windows NT 3.51 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 Windows Server 2019 |
The protocol described in [MS-RPRN] is not supported. The client detects this if the RPC binding to the endpoint for the protocol described in [MS-RPRN] fails. |
|
PSS 2.0 |
Windows NT 3.1 Windows NT 3.5 Windows NT 3.51 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 Windows Server 2019 |
Windows NT 3.1 Windows NT 3.5 Windows NT 3.51 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 Windows Server 2019 |
The protocol described in [MS-RPRN] is supported except for the RpcOpenPrinterEx method. |
|
PSS 2.0 Additional capabilities described in [MS-RPRN] |
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 Windows Server 2019 |
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 Windows Server 2019 |
The protocol described in [MS-RPRN] is supported including the RpcOpenPrinterEx method, and the OSVERSIONINFO.BuildNumber is less than or equal to 1381. |
|
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 Server 2016 Windows Server operating system Windows Server 2019 |
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 Windows Server 2019 |
OSVERSIONINFO.BuildNumber is greater than 1381 but less than or equal to 3790. |
|
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 Server 2019 Windows Server 2022 |
Windows Vista Windows 7 Windows 8 Windows 8.1 Windows 10 Windows 11 |
OSVERSIONINFO.BuildNumber is greater than 3790. |
<10> Section 2.6: This, behavior occurs in print clients 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 registry 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 name>\Drivers\Version-3\<print driver name>\PrintDriverAttributes". This key can take the following values:
|
Value |
Description |
|---|---|
|
0x00000001 PRINTER_DRIVER_PACKAGE_AWARE |
The printer driver is part of a driver package. |
|
0x00000005 PRINTER_DRIVER_SANDBOX_ENABLED |
The printer driver supports print driver isolation. |
Windows uses the Environment name strings "Windows NT x86", "Windows IA64", "Windows x64", and "Windows 4.0".
<16> Section 3.1: Print server support for the Print System Asynchronous Remote Protocol [MS-PAR] can be disabled by using a local Windows registry setting.
<17> Section 3.1: This precondition does not apply if the print client is implemented in Windows 95, Windows 98, or Windows Millennium Edition.
<18> Section 3.1: The printer driver directory is not required by the Windows print client to complete this scenario; the print client merely preemptively queries this piece of print server configuration data.
<19> Section 3.1: After registering for print status notifications, Windows print clients call the RpcRouterRefreshPrinterChangeNotification method on the print server with the dwColor parameter value 1. The print server then returns the RpcRouterRefreshPrinterChangeNotification method call with a success code.
Until a print client calls the RpcRouterRefreshPrinterChangeNotification method again with a different dwColor parameter value, the Windows print server uses 1 as the dwColor parameter value when calling the RpcReplyOpenPrinterEx method on the print client, as described in task 3 of this example. Windows print clients and print servers use this mechanism to avoid order reversal of print status notifications due to network latency.
<20> Section 3.2: The maximum number of shared print queues allowed in a Windows workgroup is 256.
<21> Section 3.2: Print server support for the Print System Asynchronous Remote Protocol [MS-PAR] can be disabled by using a local Windows registry setting.
<22> Section 3.2: This precondition does not apply if the print client is implemented in Windows 95, Windows 98, or Windows Millennium Edition.
<23> Section 3.2: The printer driver directory is not required by Windows print clients to complete this scenario. Print clients merely preemptively queries this piece of print server configuration data.
<24> Section 3.2: After registering for print status notifications, a Windows print client also calls the RpcRouterRefreshPrinterChangeNotification method on the print server with the dwColor parameter value 1. The print server then returns the RpcRouterRefreshPrinterChangeNotification method call with a success code.
Until a Windows print client calls the RpcRouterRefreshPrinterChangeNotification method again with a different dwColor parameter value, a Windows print server uses 1 as the dwColor parameter value when calling the RpcReplyOpenPrinterEx method on the print client as described in task 3 of this example. As described in [MS-RPRN], Windows print clients and print servers use this mechanism to avoid order reversal of print status notifications due to network latency.
<25> Section 3.3: The example described in this section does not apply to print clients implemented on Windows NT Workstation operating system, Windows 95, Windows 98, Windows 2000 Professional, Windows Millennium Edition, and Windows XP, or to print servers implemented on Windows NT, Windows 2000 Server operating system, and Windows Server 2003.
<26> Section 3.4: This precondition does not apply if the print client is implemented in Windows 95, Windows 98, or Windows Millennium Edition. A registry setting is used to disable the Print System Asynchronous Remote Protocol [MS-PAR].
<27> Section 3.5: This precondition does not apply if the administrative client is implemented in Windows 95, Windows 98, or Windows Millennium Edition. A registry setting is used to disable the Print System Asynchronous Remote Protocol.
<28> Section 3.6: The example also applies to print clients running on Windows 95, Windows 98, and Windows Millennium Edition, and when a user sends a print job to a print queue by using the command to copy a file to a printer share.
<29> Section 3.6: Windows NT, Windows 95, Windows 98, Windows 2000, Windows Millennium Edition, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 print clients and servers support the copy /b and net print command [MSFT-NETPRINT] functionality.