Once you have the Print Server role added to your machine, you can now open the Print Management console from Administrative Tools Figure 2 :. Figure 2: The Print Management console. Print Management can actually scan the network to find any printers present and install drivers and create printer queues for them using the local server as your print server. To do this, start by expanding the Print Servers node in the console tree to display the local server:.
Right-click on this local server and select Automatically Add Network Printers. This opens a dialog box that will scan the local subnet for any network printers present:. Figure 4: Dialog box to scan for network printers on the local subnet. Click the Start button and the scanning process begins, and once the subnet has been scanned the information gathered will be processed, printer drivers will be installed, print queues will be created, and the printers will be shared.
The only time you might have to manually intervene is to provide a driver for a printer if Windows doesn't have one for that particular brand of printer. Alternatively, let's say you already have your network printers set up and installed, as I do, and that there are two other Windows Server machines currently functioning as print servers, namely BOX and BOX Let's add BOX to the list of print servers and see what happens.
Figure 5: Adding a print server to Print Management. Figure 6: BOX is added to the list of print servers. By right-clicking on any of these printers you can perform tasks such as the following:. There's also an option to deploy printers using Group Policy, but we'll cover that one in a future article.
Let's go ahead and add BOX as a print server to make the next topic more interesting:. Figure 7: Three print servers listed in Print Management. Say you want to get a quick picture of what's happening with different printers on your network. For example, say you want to know which printers currently have jobs in their print queues. Using the Print Filters feature of Print Management, this is easy—a lot easier than browsing all the print queues of all your network printers!
Figure 8: Using the default printer filter named Printers With Jobs. Note that both Accounting Printer 1 and Sales Printer 2 have one job in their queue, and that the Accounting printer is ready but the Sales printer is in an error state. Opening the printer queue for the Sales printer lets you see the details of what's in the queue:.
Figure 9: Test page is stuck in the queue for Sales Printer 2. That doesn't tell us what's wrong with the printer of course—maybe that could be a feature request for R3! Print Management on the new print server: exporting printers from the old print server. Change to Tpms. Powershell and convert the export files created above — here W2k3-printers. Merge both PowerShell files to a single file. At the end of this new PowerShell file add the following lines :.
Powershell migration cript:. You can create a Windows Server file server and print server manually, or you can use the wizards that are provided in the Configure Your Server Wizard administrative tool. Click Print server in the Server role box, and then click Next. On the Printers and Printer Drivers page, click the types of Windows clients that your print server will support, and then click Next.
Click Local printer attached to this computer , click to clear the Automatically detect and install my Plug and Play printer check box, and then click Next. Click the printer make and model or provide the drivers from the printer manufacturer media, and then click Next.
If you are prompted to keep or not keep your existing printer driver, either keep the existing driver or replace the existing driver. If you replace the driver, you must provide the manufacturer driver for this printer.
Click Next to continue. Accept the default name of the printer or provide a different name, and then click Next.
0コメント