2.5.3.8.2 Managing Print Jobs Submitted by All Users Using the Protocols Described in MS-RPRN or MS-PAR
Goal: For an administrator to manage print jobs that are submitted by all users, which include pausing, resuming, canceling, changing their priority, changing their order in the queue, or restarting.
Context of Use: An administrator might have to override or reconfigure print jobs that various users have submitted to multiple print queues to effectively manage or maintain printing resources. An administrator can use an administrative client or a print client to manage print jobs that are submitted by all users.
Direct Actor: The direct actor is the administrative client or the print client.
Primary Actor: The primary actor is the administrator.
Supporting Actors: The supporting actor is the print server.
Preconditions: An administrator has administrative permissions for the print queue, enabling the print server to grant the request to open a job handle of any job, regardless of who submitted the job.
Stakeholders and Interests:
Print client: The print client is used to display the print jobs that are submitted by the user, to enable the user to select a print job to manage, and to select management functions.
Administrative client: The administrative client is used to display the print jobs that are submitted by all users, to enable the administrator to select print jobs to manage, and to select management functions.
Print server: The print server receives and executes job management functions that are requested from a print client or an administrative client.
User: A user wants to manage the printing of a print job, pausing, canceling, or changing the priority of the print job, for example.
Administrator: An administrator wants to manage all the print jobs that have been submitted to a print queue to service the printer, free up the printer for alternate uses, or to intervene when discovering that a very large print job has been sent to a printer not capable of handling such volume.
Preconditions: An administrator has administrative permissions for the print queue by enabling the print server to grant the request to open a job handle of any job, regardless of who submitted the job. The print spooler services are operational on the print client and the print server. Both are members of the domain and are connected to a network. The network is operational.
Minimal Guarantee: The user or administrator attempting to perform management functions on a print job will be denied permission via the user interface on the print client or the administrative client.
Success Guarantee: The user or administrator attempting to perform management functions on a print job will successfully be able to pause a job, resume a job, cancel a job, or perform other functions.
Trigger: The user opens the print queue user interface and reviews queued jobs before modifying them with functions such as cancel, reorder, pause, and resume.
Main Success Scenario:
In the following scenario, the print client performs actions by using the Print System Remote Protocol [MS-RPRN].
The print client opens a printer handle.
The print client enumerates jobs that are scheduled for printing on the printer.
The print client opens a handle to a specific job. The print server denies this request for any job that is not submitted by the user of the print client.
The print client modifies job settings or job priority.
The print client closes the printer handle.
Variation (a) - Performing the use case by using the protocol as described in [MS-PAR]: All details are identical to the use case described in this section except that the Print System Asynchronous Remote Protocol [MS-PAR] is used instead of the Print System Remote Protocol.