Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We want to add our network printers (Dell 5100cn) to Active Directory, so that it is easier for users to find them on the network, but don't see a need to place a "print server" between the clients and the printers, as the latter have their own IP addresses and the built-in capability to queue print jobs originating from multiple clients.

Yet all the documentation I have seen on adding a printer to Active Directory seems to start with the assumption that the printer has been added to a Windows computer that "shares" it. Is it not possible to add such network printers into AD directly?

I think of a network printer as being a specialized host that should be able to have an independent entry in the directory. Is this the wrong concept?

share|improve this question
    
Here's a related post: serverfault.com/questions/218686/… –  Jan Hettich Oct 8 '11 at 15:57
add comment

2 Answers 2

Others may correct me, but I've been told good practice is to have a print server (Windows server) set up with the printer then that computer, in turn, shares it out to Active Directory. That way it also acts as a repo for the Windows drivers for the clients to download when connecting. You just add the network printer as a "local printer" using a network/tcpip port.

Also the Windows server acts as a print spooler from which you centrally manage permissions and print jobs.

We share all our printers out using this model.

share|improve this answer
    
This seems to be one of the documented approaches, but wasn't the way I had wanted to set it up. I'm not keen on making the server a possible single point of failure. Also, the story about getting the server to provision the drivers to clients seems more complicated to set up in practice than it is conceptually, when you have a 64-bit Windows Server 2008 R2 and some clients with 32-bit OS (XP, Vista, 7). –  Jan Hettich Oct 8 '11 at 8:06
    
RE:Drivers-no, it's not hard. You install the driver for the printer on the server. If you need others you can go to the properties and the driver tab to add other drivers. You can mix 64 bit and 32 bit clients...in theory. We have had some problems but we've found it usually an issue with the printer driver manufacturers. With Windows 7 we've had fewer problems on a Win2008 printer server. –  Bart Silverstrim Oct 8 '11 at 14:03
    
RE: Drivers. When you go to the tab to add other drivers, it prompts you to specify the location of the .inf file. But for some of our printers, the manufacturer only supplies an .exe installation file. Is there a work-around for that? –  Jan Hettich Oct 8 '11 at 15:33
    
May have to expand them if it's a self-extracting .exe file. –  Bart Silverstrim Oct 8 '11 at 20:59
add comment

I agree with Bart as it's easier to maintain and setup printers via a Windows server, you can deploy them with Group Policy Preferences. See Deploying TCP/IP Printers with Group Policy Preferences or Configure a TCP/IP Printer Item

Just remember that you will have ensure that the printer driver is installed on the machines before you deploy it via GPP

share|improve this answer
1  
This seems to be the other documented approach. I had already read and tried implementing the steps outlined in Clay Moore's excellent blog post (which you referenced). But in this case, the first step is still to install and share the printer on a server. - I guess the option of adding a network-enabled printer directly to AD exists only in my head! –  Jan Hettich Oct 8 '11 at 8:23
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.