2.3.2 Dependencies on Other Systems/Components
The Print Services system member protocols require the following protocols:
SMB access protocols:
Used as transport for the Print System Remote Protocol [MS-RPRN]. It uses RPC over named SMB pipes.
Used for driver download from a print server by using the copy file functionality of the SMB access protocols.
RAP [MS-RAP], used to browse for printers.
CIFS [MS-CIFS], used to copy drivers from the server and to submit print jobs over redirected ports.
SMB Version 1.0 [MS-SMB] and RAP. SMB Protocol Versions 2 and 3 [MS-SMB2], however, are not compatible with RAP:
Used for managing SMB print scenarios by using RAP.
Used for managing SMB file copy functionality of the print server by using RAP.
Used as transport for the Web Point-and-Print Protocol [MS-WPRN].
RPC over TCP/IP:
Used as transport for the Print System Asynchronous Remote Protocol [MS-PAR].
Used as transport for the Print System Asynchronous Notification Protocol [MS-PAN].
Group Policy: Core Protocol [MS-GPOL] [MS-NRPC] [MS-DRSR].
Used for the Group Policy: Deployed Printer Connections Extension [MS-GPDPC].
Used for publishing and query of shared print queues.
Used by the Group Policy: Deployed Printer Connections Extension.
Used as transport by LDAP [RFC4511].
Used as transport by the Line Printer Daemon Protocol [RFC1179].
Used as transport by HTTP.
Used as transport by HTTPS.
Used as transport by RPC over TCP/IP.
Used as transport by the SMB protocol family unless on an IPX or NetBEUI network [NETBEUI].
Common Internet File System (CIFS) Browser Protocol [MS-BRWS].
Used for workgroup preconditions.
The Print Services system member protocols [MS-RPRN], [MS-PAR], and [MS-PAN] are RPC-based and require RPC bindings between print servers and print clients to registered RPC endpoints. If a print client or print server is unable to register an RPC endpoint or create RPC bindings, then Print Services, which are provided by the local print spooler, only enable the management and use of locally connected printers. Firewalls that are implemented on print clients or print servers are configured so that all ports that are required by member protocols are open for RPC-based communication, or at least open for SMB-based communication to support the Internet printing scenario by using IPP and the Web Point-and-Print Protocol.
The Print Services system can run in a domain-based network and a workgroup environment. Print Services require that File Share services be installed and enabled for Point-and Print-driver download and for SMB and Remote Administration Protocol support. On creation of a printer queue connection to a print server, the print client tries to copy the driver from the print server. For more information, see the use cases in sections 2.5.3.3 and 2.5.3.4. If copying the print driver fails, the print client tries, in turn, to locate:
Any available implementation-specific driver sources or repositories.<4>
The print client prompts the user to supply an appropriate printer driver from a disk, an Internet location, or other media.
If the print client cannot obtain a suitable printer driver from any of these sources, the print queue connection cannot be created.
The Print Services system requires the CIFS Browser Protocol for workgroups. Availability of this protocol and the Active Directory system is not determined at startup, but only on request. If neither the CIFS Browser Protocol nor the Active Directory system are available, a print client does not list any available shared print queues in the network; as a result, only local functionality of the print spooler is available unless the user of the print client knows the name of the print server and enters it manually.
The Print Services system uses the Windows Update Services: Client Server Protocol [MS-WUSP], if available, to find the most up-to-date or best matching printer drivers for a print queue connection. If Windows Update Services are unavailable, the Print Services system use other methods to find an appropriate printer driver. For more information, see the use cases in sections 2.5.3.2 and 2.5.3.3.
All member protocols can be used between print clients and print servers, depending on circumstances.
The Print Services system uses the Active Directory system in domain-based networks. The LDAP protocol is used between the print server and the Active Directory system and between the print client and the Active Directory system. In workgroup environments, the CIFS Browser Protocol [MS-BRWS] is used for communication between print clients and print servers, and between print servers.
The file system access that is used by clients to download printer drivers only assumes a directory-structured file system. The print server generally restricts access by using access control lists (ACLs), so that print clients have only read access to the printer driver files. The file system supports file date/time stamps for comparing driver versions.
Any number of print servers and print clients can be operated in a domain-based network. The number of shared print queues of which clients retain knowledge in a Windows workgroup is limited to an implementation-defined maximum,<5> which limits the useful number of shared printers in a Windows workgroup network. From the system perspective, the entirety of print clients and print servers in a given network represents a single instance of the system.
The Print Services system also depends on the following components and infrastructure:
The Windows Authentication Services system [MS-AUTHSOD].
The Active Directory system in a domain environment: If the Print Services system is deployed within a domain, print servers can publish shared printers to the Active Directory system by using LDAP. Print clients that are joined to domains also require access to the Active Directory system to discover published printers.
The networking system to connect print server, print clients, and the Active Directory system.
Printers.
Application software that provides printing functionality, such as Microsoft Office Word.
The Print Services system is influenced by the following:
The Active Directory system can propagate policy settings that control local spooler behavior to print clients and print servers.<6> by using the Group Policy: Core Protocol [MS-GPOL].
These policies control aspects of print spooler implementation, for example, which print servers are considered trusted for printer driver download in Point-and-Print scenarios.
The Group Policy: Deployed Printer Connection Extension [MS-GPDPC] influences the Print Services system in regard to deployed printer connections.