Microsoft Network Printing

1
Microsoft Network Printing
2
Microsoft Printing Terms

• Print Server/Device/Client
• Spooling
• Shared v. Local

3
Overview

• Printing client (workstation) generates the print
  job and sends it to the print server (computer
  sharing the printer)
• Some network based fax devices are treated in the
  same manner as a print device.
• If multiple jobs are sent to a print server, it
  saves the print jobs to a temporary disk storage,
  this process is know as spooling

4
Overview

• Print Spooler Service

5
Overview

• Shared v. local Printers
• Can push drivers down to client when connecting.
• Central point for driver updates.
• Will push drivers down for previous versions of
  Windows.

6
Overview

• Printer Scheduling Priorities
• Can schedule print priorities and times.
• Print large documents after hours
• Printer priorities within a pool give a
  particular printer priority of the others.
• Can be set from 1-99
• High priority for more important print jobs

7
Overview

• Managing Print Jobs
• Print Queues-a stack of print jobs, all jobs
  waiting in line, first come, first served.
• You can manage the queues by double clicking on
  the printer in your printers folders. You will
  typically only have access to manage or cancel
  your own jobs.

8
THE WINDOWS SERVER 2003 PRINTER MODEL

• Locally attached printers Printers that are
  connected to a physical port on a print server,
  such as a USB or parallel port
• Network-attached printers Connected directly to
  the network

9
USING LOCALLY ATTACHED PRINTERS
10
USING NETWORK-ATTACHED PRINTERS
11
CREATE A LOGICAL PRINTER ON EVERY CLIENT COMPUTER
12
CREATE A PRINT SERVER
13
DEPLOYING A SHARED PRINTER

• Install the printer on the print server.
• Create a printer share on the print server.
• Connect the clients to the print server.

14
SHARING A PRINTER
15
Local Shared Printers
16
BROWSING IN WINDOWS EXPLORER
17
SEARCHING IN ACTIVE DIRECTORY
18
CONTROLLING PRINTER SECURITY
19
CREATING A PRINTER POOL
20
MONITORING PRINTERS

• Monitoring print queues
• Using Event Viewer
• Auditing printer access

21
MONITORING PRINT QUEUES
22
REDIRECTING PRINT JOBS

• Reduces the impact of a failed printer
• Enables users to continue printing without
  reconfiguration
• Destination printer must use the same driver type
  as the original

23
USING EVENT VIEWER
24
AUDITING PRINTER ACCESS
25
TROUBLESHOOTING PRINTERS

• Troubleshooting procedures can include one or
  more of the following
• The application that is attempting to print
• The logical printer on the computer on which
  the application is running
• The network connection between the client and
  the logical printer on the server
• The logical printer on the server (spooler,
  drivers, security settings, and so forth)

26
TROUBLESHOOTING PRINTERS (continued)

• The connection between the print server and the
  printer
• The printer itselfits hardware, configuration,
  and status

27
TROUBLESHOOTING PROCEDURES

• Verify that the print client can connect to the
  print server.
• Verify that the printer is operational.
• Verify that the printer can be accessed from the
  print server.
• Verify that the print servers services are
  running.

28
SUMMARY

• The printing architecture in Windows Server 2003
  is modular, consisting of the physical printer, a
  print server with a shared, logical printer
  connected to the physical printer through a local
  or network port, and a logical printer on a
  client that connects to the shared, logical
  printer on the print server.
• A local printer is one that supports a printer
  directly attached to the computer or attached to
  the network.
• Shared printers are published to Active
  Directory.
• The Add Printer Wizard is used to add a logical
  printer.

29
SUMMARY (continued)

• A single logical printer can direct jobs to more
  than one port, creating a printer pool.
• A single physical printer can be served by
  multiple logical printers, each of which can be
  configured with unique properties, drivers,
  settings, or monitoring characteristics.
• The print queue window, event logs, and
  performance counters enable you to monitor
  printers for potential signals of trouble and for
  utilization statistics.