Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a printer deployed to my Active Directory with GPO.

Do I need to keep that printer installed on the server? Is that necessary? Isn't the logon script creates the printer to everyone? Including the DC?

I want to add, that from one of the stations (mine) the printer icon is greyed out a bit

enter image description here

Deployed the printer with: pushprinterconnections.exe script in the logon process, within the Default Domain Policy, under windows settings of User Configuration.

I also see the printer installed on the DC enter image description here

Printer Management on the DC enter image description here

share|improve this question
There are at least 4 different ways that I can think of to deploy a printer via GPO. Can you explain exactly what template/settings you're using and where the printer is shared from? – MDMarra Sep 13 '11 at 13:18
thanks mark, I edited the question to have that data – Saariko Sep 13 '11 at 13:25
up vote 0 down vote accepted

It appears that you are using the Deploy Printers feature of the Print Management console. This makes an entry in your GPO that tells clients to connect to a printer located on a print server.

If you have a separate print server, then you never needed the printer to be connected to the DC in the first place. If you don't have a print queue shared out from a server, then you'll need to make a queue on a server and share it. Whether or not it's on the DC is up to you. If that's your only server, you have no choice. I do recommend a separate print server whenever possible, though.

Do I need to keep that printer installed on the server?

You need it installed somewhere central.

Is that necessary?

If you want to deploy printers using the Deploy Printer function of the Print Management Console, then yes. Having queues reside on a server allows you to centrally manage and audit all documents send to all printers. It makes maintenance and management a breeze compared to having each printer mapped directly via TCP/IP to the printer.

Isn't the logon script creates the printer to everyone? Including the DC?

That depends entirely on what GPO you deployed the printer to. It will only apply to the OUs that the GPO is linked to. If you deployed it to the Default Domain Policy, then it will apply to anyone.

Side note: You really shouldn't be installing printers on DCs if you don't have to. Print drivers are the devil, and the last thing that you need on a DC is stability issues. You also shouldn't be modifying the Default Domain Policy unless you really know what you're doing. You should be making new policies and linking them to the appropriate OUs.

share|improve this answer

Your Answer


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.