Windows 2000 uses the following printing terms :
|Print device. A print device is the hardware device that produces the
prints. Windows 2000 supports local print devices and network-interface
print devices. Local print devices are connected to a physical port on the
print server. Network-interface print devices are connected to the print
server via the network. They have their own network interface card and
network address or are connected to an external network adapter.
|(Logical) printer. A logical printer is a software interface
between the operating system and the print device. The printer defines where
a document will reach the print device (local, via network, to file), when
it will be printed, and various other aspects.
|Print server. A print server stores the information of the print
devices and the printers. It receives and processes documents from the
|Printer driver. A printer driver is one or more files containing
information that Windows 2000 needs requires to convert print documents into
a specific printer language.
|Print job. The code that contains the information to be printed and the way it should be printed.
When connecting a printer to a machine, Windows 2000 will use the
A printer connected via USB or IEEE 1394 serial block protocol 2 will be automatically detected. (hot-swapping) If a printer is connected via a parallel
port, the machine has to be reboot unless the Discover new hardware wizard is
used. Windows 2000 also supports infrared printers. (plug-and-play) Printers
using a serial port or printers connected via the network are supported but do
not use plug-and-play.
You don't have to be administrator to connect plug-and-play printers.
Options for network printing :
|Windows 2000 server can handle large numbers of connections and supports Macintosh, Unix computers and NetWare clients. Microsoft recommends a dedicated print server installed as a member server with sufficient RAM and disk space for spool files.
|Windows 2000 Professional supports up to 10 network connections for file and print servers. It does support Unix computers but does not support Macintosh and NetWare.
When defining a network-interface print device you have to add additional port info :
|Network protocol. The default protocol for Windows 2000 is TCP/IP.
|Printer name or ip address. Enter the location of the print device by using an ip-address or a DNS name. When using an ip-address Windows 2000 will suggest a port name in the form of IP_ip address.
|Port name and other settings. The name of the port that Windows 2000 has to use in the wizards. Via the wizard you can also specify various port settings like the protocol (RAW or LPR), Port number (default 9100), LPR settings and SNMP status information.
The preferred port monitor in Windows 2000 is the Standard TCP/IP Port Monitor (SPM) which uses TCP/IP to transport the documents. It uses SNMP to configure and monitor the printer ports.
Port can be modified and deleted via File - Server properties in the printers folder. (ports-tab)
Windows 2000, NT, 98 and 95 clients will automatically download the printer driver when connected to a shared printer on a Windows 2000 server, as long as a copy of the driver is available on the print server. (Point and print) Keep in mind that different hardware platforms use different drivers (e.g. Alpha) A client using Windows 3.1x or MS Dos needs a manually installed local printer driver.
Users of non-Microsoft clients can use the Windows 2000 print server if additional services are installed :
|Macintosh. Services for Macintosh are included with Windows 2000 server but are not installed by default. This option is not available on Windows 2000 Professional.
|Unix. TCP/IP printing (Line Printer Daemon) service should be installed. This can be done on Windows 2000 Professional and server.
|NetWare. File and Print Services for Netware should be installed. This option is not included in Windows 2000 Professional.
A Windows 2000 client can connect to a printer by searching the Active Directory, using the UNC-name or browsing the network. A client using Windows NT, Windows 95 or 98 can only use the UNC-name or browse the network. MS Windows 3.x users use the Print Manager. MS Dos users use the net use command (net use lptx \\server_name\share name).
Windows 2000 can also use a web interface to connect to a printer. Use the http://server_name/printers URL to view all servers. Select Connect to add the printer. You also connect directly to a printer by using the http://server_name/share_name and use the Connect option to copy the printer drivers to the client or use http://server_name/printers/printer_name/printer to connect the print via the add printer wizard. The main benefit of the web interface is that users without access to the LAN can remotely access the printers. You can disable the web interface by adding the registry key HKLM\Software\Policies\Microsoft\WindowsNT\Printers\DisableWebPrinting (DWord value 1 and restart)
A printer pool is one printer that is connected to multiple print devices through multiple ports on the servers. These pools can be local or network-interface print devices. The print devices must use the same printer driver. When a user sends a document to the printer pool, the printer checks the for the first available port. The benefits of a printer pool are fast printing in a high volume environment and a single administration point for various print devices. Windows 2000 supports and unlimited amount of print devices in a printer pool. Select 'Enable printer pooling' at the ports-tab of the printer the enable print pooling for a device.
If you point two or more printers to the same print device, you can set priorities for each printer. This enables the possibility to print high priority prints first by sending them to a separate printer with a high priority. The lowest priority is 1, the highest priority is 99. It gives also the ability to create separate queues for various functions of one print devices, e.g. double sided printing.
|The graphic device interface (GDI). This portion of Windows 2000 calls the video driver to produce screen output and uses the printer driver in cooperation with the application to initiate prints.
|The printer driver. The printer driver is the interface
between the operating system and the print device. Printer drivers are not
compatible across operating system. If you want to let a Windows 98 client
print via a Windows 2000 print server, you have to install the Windows 98
printer drivers on the Windows 2000 print server. A printer driver has three
You can view the installed printer drivers via File - Server properties in the printers folder. (drivers tab)
|The printer spooler. The printer spooler (%systemroot%\system32\spools.dll)
is a collection of dll's and device drivers that receive, process, schedule
and distribute print jobs. The spooler directory can be changed at the
advanced tab of the server properties of the printers-folders. By default
the directory is %systemroot%\system32\spool\printers. It is also
possible to define a separate spool directory for a printer by changing the
registry: \SYSTEM\CurrentControlSet\Control\Print\Printers \<specific
The printer spooler is composed of the following components :
RAW files are fully rendered when created and are a bit bigger than EMF files. Windows 9x uses them for remote printing, Windows NT 3.51 for local and remote printing.
The default type the Windows NT/Windows 2000 print processor (winprint) uses is RAW. This so Windows 9x client can print via the network. If a Windows 2000 client is able to send an EMF file, EMF will be used to handle the printjob.
RAW (FF appended) will always add a form-feed character to a print, RAW (FF auto) will try to detect if a form-feed should be add.
|The print monitor. The print monitor consists of two monitors who
maintain the communication with the print device :
|A plug-and-play printer will be automatically detected if you use the 'Automatically detect my printer' option when you have to choose for a local- or network printer.
|If you want to print to a file, select the File-option at the 'Use the following port' item.
|You can use the Windows update functionality to download a newer driver from the Microsoft web site.
|The default printer name is the printer's model name. The name can be up to 220 characters but cannot contain a comma, backward slash or exclamation point. As some programs cannot connect to printers with more than 31 characters, keep the name shorter than 32 characters.
|The share name can be up to 220 characters. If you have DOS-clients, limit the name to 8 characters to be compatible.
|Information entered into the comment box will be displayed to DOS, NT and Windows 9x clients. Information in the location box will only be shown to Windows 2000 users.
|Printer drivers are stored in \winnt\system32\spool\drivers. (print$-share)
|Printer information is stored in HKLM\System\CurContrSet\Control\Print\Printers
|Additional drivers for other operating systems can be add at the Sharing tab of the printer's properties.
|Select 'Print directly to printer' in the Advanced tab if you do not want to create a spool file.
|Windows 2000 can install printer drivers for Alpha (NT3.1 - 4), Intel (Windows 2000, NT 3.1 and 4.0, Windows 9x), PowerPC (NT3.51 and 4), MIPS (NT 3,1-4). MS Dos and Windows 3.x clients need local printer drivers.
A printer is automatically published in the Active Directory when the default settings are in place. This allows users to find printers by defining location, paper sizes, ability to print color or double-sided, etc. Some group policies that control printer defaults with respect to publishing printers in active directory are :
|Automatically publish new printers in Active Directory. (enabled by default)
|Allow printers to be published. (enabled by default)
|Display the down level page in the Add Printer wizard (enabled by default) Can be disabled to prevent the Add Printer wizard from browsing the network for shared printers.
|Prune printers that are not automatically republished (how the pruning
service, which automatically removes printers, handles printers on
non-Windows 2000-based print servers when a printer is not available.
Down level printer pruning properties determines how orphaned PrintQueue objects representing down level printers are to be pruned. A printer is down level if the server hosting the printer is not running Windows 2000.
|Printer Browsing: If enabled printers are offered for printer browsing. By default only shared printers that are not published in the active directory are published.
Non-Windows 2000 printers can be published by using the Active Directory Users and Computers tool.
Print permissions can only be set when using NTFS. You can set the following permissions :
|Print. Users are allowed to print to the print device and to pause, cancel, restart or resume their own documents. (By default Everyone group is allowed to print)
|Manage documents. Same as print permissions and users are also able to manage other users prints.
|Manage printers. Same as manage documents and users are able to add and remove printers, set permissions, change shares and manage printer settings. (By default administrators, print operators and power users)
To add/remove printers, share printers, take ownership of a printer and the change the printer properties or permissions you must have the Manage printer permission. Default Administrators, Print- and Server operators and Power Users (professional and stand-alone server) do have these rights.
When a job is send to a printer outside the available hours, the job will be queued until the printer is available again. If you want different access hours for different users, create more than one printer for a printer device.
Printers installed on a server are shared by default, printers installed on Windows 2000 Professional are not automatically shared.
Any client that supports Internet Printing Protocol (IPP) 1.0 can print to a
Windows 2000-based print server using HTTP. (Windows 9x-based and Windows 2000
clients using IE 4.0 or higher) if Internet Information Services (IIS) or
Microsoft Peer Web Services (PWS) is installed on the Windows 2000 print server.
When IIS is installed, IPP is enabled by default and all printers on that server
can be accessed via IPP. A Windows 95/98 client can install the IPP client from
the installation cd-rom. (\clients\win9xipp.cli\wpnpins.exe)
A user can connect to the printer by providing an URL. When the driver is available on the server, it will create a .cab-file and offer the driver as a point-and-print service. Security is provided by IIS. This means if all clients should be supported, clear-text authentication is needed but MS challenge/response, kerbores, digest authentication and SSL 3 can be used.
An administrator can disable Internet printing with the group policy setting Disable Web-based Printing. More info : http://support.microsoft.com/support/kb/articles/Q234/2/70.ASP
Windows 2000 contains four separator pages stored in \winnt\system32 :
|Sysprint.sep. Prints a separator page for each document. Compatible with postscript.
|PCL.sep. Switches to PLC for HP-printers and adds a page for each document.
|Pscript.sep. Switches to Postscript for HP but does not print a page before a document.
|Sysprtj.sep. Sysprint.sep with Japanese characters.
A separator file is set at the Advanced tab of a printer.
Windows 2000 Server supports the UniDriver 5.0 printer driver and the PostScript 5.0 printer driver. UniDriver 5.0 is, a 32 bits printer driver that support all non-Postscript printers also called a raster driver. The driver support various color depths, truetype-, opentype- and device fonts. It has an extension interface for which manufacturers write specific data files. The drivers use the Unidrv.dll (printer driver), Unidrui.dll (configuration file/user interface) and xxx.gdp. (data/characterization file, file name is based on printer model)
The postscript 5.0 printer driver creates structured postscript and support postscript level 1,2 and 3. The driver is Adobe 4.3 and Document Structuring Convention (DSC) 3.0 compatible. It uses the pscript5.dll (printer driver), ps5ui.dll (configuration file) and x.ppd (data/characterization file, file name is based on printer model) files.
The Windows 2000 plotter driver supports diverse plotters that use the
This Windows 2000 component provides line printer remote (LPR) and line printer daemon (LPD) services to allow cross-platform printing between Unix and Windows 2000. LPR is the client-side Unix printing utility that enables a user to send a job to a Unix print server running LPD.
In Windows 2000, the two new services provided by Print Services for Unix are:
|LPRMON, which enables Windows 2000 print servers to send print jobs to Unix print server running LPD. In other words, LPRMON enables Windows clients to print to Unix printers via the Windows 2000 print server running LPRMON.
|LPDSVC, which emulates LPD on Windows 2000 print servers. In other words, LPDSVC enables Unix clients to send print jobs to the Windows 2000 print server running LPRMON.
Note that once you have installed these services, you must change the startup configuration of LPDSVC from Manual to Automatic. Note also that not all Unix systems use the same LPR specification, so establishing printing interoperability between Windows 2000 and Unix platforms can sometimes be problematic.
Windows 2000 supports Image Color Management (ICM) 2.0 in conjunction with better halftone and image processing technologies. This lets users reproduce documents on a printer faster, easier, and with greater color accuracy and consistency.
The Con2prt.exe tool is a command-line utility for adding or removing network printers on Windows NT-based computers. You can use the Con2prt.exe tool in a Windows NT login script or in conjunction with an unattended setup of Windows NT. For more info see http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP?LNG=ENG&SA=ALLKB&FR=0
This program is a powerful tool for working with printer driver issues on Windows NT 4.0 and Windows 2000-based print servers. Fixprnsv.exe can help you resolve printer driver incompatibility issues, as well as perform an on the fly replacement of printer drivers that are known to have problems. Fixprnsv.exe replaces incompatible or problem printer drivers with Microsoft provided printer drivers. Fixprnsv.exe will not install drivers for printers that are not already configured on the print server.
Fixprnsv.exe is in the Printers\Fixprnsv folder on the Windows 2000 Server CD-ROM. The command-line switches for Fixprnsv.exe are:
|/?. When this switch is used, Fixprnsv.exe displays a list of the command line switches with their appropriate syntax.
|/diag. When this switch is used, Fixprnsv.exe scans the computer for incompatible print drivers only. No changes are made.
|/fix. When this switch is used on a Windows NT 4.0-based computer, Windows 2000 print drivers can be installed. This permits Windows 2000-based clients to connect to the print server and download the appropriate printer drivers. When this switch is used on a Windows 2000-based computer, any incompatible Windows NT 4.0 printer drivers will be replaced.
|/q. Quiet Mode. When this switch is used, Fixprnsv.exe does not prompt the user. Fixprnsv.exe displays any appropriate messages.
Within XP/.Net server there are additional option to set the notifications to end-users. On the Advanced tab of the Print server properties you can set the following options :
|Show informational notifications for local printers.
|Show informational notifications for network printers.
Printer notifications for downlevel clients :
|Notify when remote documents are printed.
|Notify computer, not user, when remote documents are printed.
|Technical overview of Windows Server 2003 print services
|Print server upgrade, migration and interoperability
|Effectively using internet printing
|Print services features
|Print services technical overview
|Point and print technical overview
|Creating high-availability print servers
|Terminal services and printing
|Printing connectivity technical overview
|Print server scalability and sizing technical overview
|Choosing the right printer drivers
|Print clustering high level overview
|File- and print services technical overview
|Adding a new file- and print server to the network
|Integration of Windows 2000 printing with Active Directory
|Microsoft article about EMF
|Microsoft article about the spool directory
|Microsoft article about network printing
|Microsoft article about internet printing
|Connecting to printers (Windows .NET magazine)
|Easy printer management with Active Directory (Windows 2000 magazine aug 2000)
|Print operator permissions (Windows 2000 magazine)
|Automatically moving users to a new print server (Windows 2000 magazine)
Resource kit printer migration utility (Windows 2000 magazine)
|Print anywhere on the web with Windows 2000 internet printing (TechRepublic)
|Laser printer terms and technology (TechRepublic)
|Search for 'printer' in knowledge base
|Search for 'spooler' in knowledge base
|Search for 'emf' in knowledge base
|Search for 'raw' in knowledge base
|Search for 'ipp' in knowledge base
|Search for 'separator' in knowledge base
|Search for 'icm' in knowledge base
|Enable or disable print job notifications in Windows XP (Q308217)
|Installing and using printers in Windows XP Professional (InformIT)
|Equitrac printlog manager
|Blackice internet print server
Last update : 27 January 2003
|file: /Techref/os/win/ddk/Win2KprnSum.htm, 66KB, , updated: 2004/7/14 17:54, local time: 2024/2/22 12:04,
|©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions?
<A HREF="http://techref.massmind.org/techref/os/win/ddk/Win2KprnSum.htm"> Summary Printing</A>
|Did you find what you needed?
Welcome to massmind.org!
Welcome to techref.massmind.org!