2.4 Assumptions and Preconditions

The following assumptions and preconditions are necessary for the Print Services system to operate successfully:

  • A network is available to provide a viable transport for the communication between the server and its clients.

  • The transport protocol for that network is available and configured. For example, the TCP transport is configured with a valid IP address.

  •  Security providers are available to the system to provide message authentication and security.

  • The durable storage devices that are used to store the system's state are on all participating computers.

  • The print spooler service is in the running state on the server and each of the clients participating in the interaction.

  • The print spooler is installed on all the participating computers.

  • The local print client connecting to a remote print server supports impersonation if the remote spooler requires authentication.

  • The remote print spooler is not required to use impersonation, nor does it require that local clients support impersonation, except when using the Print Asynchronous Notification Protocol [MS-PAN].

  • The file SMB Protocol Family support server service is in the running state on the server.

  • The print client and print server support the Print System Remote Protocol [MS-RPRN].

  • The system is configured so that participants can access its services locally or remotely.

  • It is assumed that each participant is trusted by the system.

  • If member protocols that are supported by the system, as listed in section 2.2, have additional assumptions and preconditions for when that protocol is in use, see the relevant member protocol specification for details.

  • Print servers have a durable store to place the following objects in:

  • Print clients have a durable store to place the following objects in:

    • Printer drivers

  • Print clients and print servers have access to local storage to persist ADM and state information; in the Windows, this local storage is in the registry.

  • In a domain configuration, print clients and print servers have access to the Active Directory system that is provided by the domain.

  • Authentication services supporting Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) [MS-SPNG] are available to the print servers and clients.

  • The Print System Remote Protocol is a RPC interface and therefore has the prerequisites common to RPC interfaces ([MS-RPCE] section 1.5).

  • The Print System Asynchronous Remote Protocol [MS-PAR] is an RPC interface and therefore has the prerequisites common to RPC interfaces.

  • The Print Asynchronous Notification Protocol is an RPC interface and therefore has the prerequisites common to RPC interfaces.

  • The print client has obtained the name of the print server that supports the Print Services system. Various protocols can be used, including the Active Directory Lightweight Directory Services Schema [MS-ADLS], Active Directory Schema Classes [MS-ADSC], and the CIFS Browser Protocol [MS-BRWS].