vb.net barcode freeware print job. Can also hold, release, or delete print jobs. in Visual C#.NET

Printing Data Matrix 2d barcode in Visual C#.NET print job. Can also hold, release, or delete print jobs.

Lpq Displays information about the specified LPD print queue. Net start Starts the specified service. Can be used to start or stop the

spooler service. Windows Small Business Server 2003 also comes with the following print management scripts that you can run from a command line as long as you switch to the %windir%\system32\ folder first:

| 255

Cscript Prnport.vbs Administers all things related to printer ports Cscript Prndrvr.vbs Adds, deletes, or lists printer drivers on a Windows

You can use the free Microsoft Printer Migrator utility (also called the Print Migrator) to back up, restore, or migrate print server settings including printer drivers and print queues. This utility makes moving to a new server much easier simply back up the print server configuration on the old server and restore it to the new one even when the servers are running different versions of Windows. (Don t try to restore a Windows Server 2003 print server configuration on a Windows NT 4.0 server, though). To use this program, you can download it from the Microsoft Web site. Then launch the program (Figure 11-14) and choose Backup from the Actions menu. This saves the configuration to a compressed .CAB file. Move the .CAB file to the desired server and run Printer Migrator again, this time choosing Restore from the Actions menu. Voil ! The settings and drivers are restored. (Keep in mind that if you migrate from Windows NT 4.0, you ll want to promptly upgrade the migrated level 2 drivers to native level 3 drivers for maximum stability.)

Figure 11-14.

256 |

Under the Hood Level 2 and Level 3 Printer Drivers Windows Small Business Server 2003 can use two types of printer drivers: level 2 printer drivers, which are written for Windows NT 4.0; and level 3 printer drivers, which are written for the Windows 2000, Windows XP, and Windows Server 2003 families. Level 2 drivers run in kernel mode, and can destabilize the operating system or force a reboot when they crash. Level 3 drivers run in protected user mode, where unstable drivers can t cause operating system instability (at worst they can crash the spooler service, which restarts automatically without requiring a reboot). Level 2 drivers can be used only on an upgraded system they can t be installed on a running Windows Small Business Server 2003 system, except by using the Printer Migrator utility.

The following sections address a number of common printing problems. If you re having trouble pinpointing the problem or solution, first use the following steps to troubleshoot the printing process: 1. Print from the client experiencing the problem and pay attention to any errors. If the document prints properly, you probably have a user error, in which case you might need to educate the users as to the proper printing procedure. Otherwise, you might have a problem with a particular program, or the printer driver might be improperly configured for the users. 2. Check the print server status. When no errors are listed, check to see whether any documents are printing correctly. If not, check that sufficient free disk space exists on the drive holding the spool folder. If documents print garbled, the printer might be using the wrong data type (EMF or raw). Try using the raw data type to see whether this corrects the problem. You might also want to clear the Enable Advanced Printing Features check box on the Advanced tab of the printer s Properties dialog box. (See Changing Spool Settings earlier in this chapter for more information.) If some documents in the print queue don t print and you can t delete them, the print spooler might be stalled. Restart the Print Spooler service to see whether this corrects the problem. You might also want to add