Priorities are determined by the pecking order in an office or document processing department. Let's say that two working groups -- document processors and managers --print to one device. If you are a manager and print a document, you may want your document moved ahead of whatever items are being printed by document processors. Obviously, you don't want to interrupt a job that's already in progress, but you might want to jump ahead of other jobs in the queue.
To accomplish this, you need to set up two logical printers for one physical print device. (This is the "old school" info that many modern admins don't study anymore.) Understand that a logical printer is just the connection between your system and the physical print device. You install a driver for the print device and it is physically connected, but the logical connection point is the "printer" in your Devices and Printers settings. Thus, you can configure two identical logical printers for one physical print device, then go to the properties of each to set them up differently.
While you're in the properties menu, go to the Advanced pane, which has the Priority option with a number next to it. Number 1 is the highest priority and number 99 is the lowest. Next, create two logical printers, one with the priority 1 that you call ManagerPrinter and one with the priority 99 that you call DPPrinter, and then configure the managers with permission to print to ManagerPrinter and document processors the permission to print to DPPrinter. Now you have different priorities for the same physical printer. Without people in the office really being aware, the print jobs of the managers are given a higher priority level and will move up the queue.
Resume print jobs after a paper jam
Hopefully, you don't see the same number of paper jams today as you would have 10 years ago, but when it does happen, do your people know what to do? Imagine a huge document (several hundred pages) jamming midway. Do you fix the jam, go into the printer queue, and choose Restart for that job? Doing so would waste a lot of paper. Instead, choose Resume to go back and reprint only those pages that were ruined by the jam. That is the smart way to resolve this issue, especially in this green world we are moving toward. (Microsoft had this as a test question a decade years ago for NT 4.0 administrators; I guess it was ahead of the game on going green.)
Ancient IT guys still have what it takes
Ask a newbie how to do TCP/IP subnetting in his head, he might not know. Ask a newbie to define the OSI model, he'll most likely Google it. Explain NTFS permissions when combined with share permissions? Ahh, the GUI generation is now understanding the frustration that the DOS admins once felt.
It's good to progress -- but not without learning the basics first. Though the older exams may be gone and newer admins may not be forced to study topics they wouldn't investigate otherwise, you can still find solid certification venues that are great eye-catchers on a résumé. A+ and Network+ from Comptia are excellent exams that make sure newbies grasp the basic concepts. And though Windows Server exams are wildly pursued by newcomers, a solid understanding of the current desktop OS can really give you the footing for Windows Server studies.
Stay tuned for more "old school" columns in the weeks and months ahead!
This article, "Printing in Windows 7: Fancy setups using 'old school' techniques," was originally published at InfoWorld.com. Read more of J. Peter Bruzzese's Enterprise Windows blog and follow the latest developments in business software and Windows at InfoWorld.com.