Bad Printers on Domain Controllers

[chris.thompson]

To start, for our setup, we have two Domain Controllers, both running Hyper-V. One of the VMs, a member server, is acting as a print server. It has print services installed, and we have added 8 network printers to it. It works pretty well.

What I've noticed is that somehow, both domain controllers have picked up 4 printers from the print servers, and at the end of each printer name is (Redirected 1). So, if a printer is named "Accounting" on the print server, on the domain controllers it is named "Accounting (Redirected 1)".

None of these printers work. It seems like they don't have any drivers. My bigger problem is that I can't remove them, I get an "Printer cannot be removed. Access is denied." message. I'm logged onto the domain controller with the domain administrator account. They're also causing a lot of errors in the event log, mostly related to Terminal Services.

I'm not really sure what I can do to get rid of these, I'm hoping someone can help. It is possible that another person screwing around somehow added these there, but I'm mostly concerned with getting rid of them. Thanks for any help!

[iamtheky]

http://blogs.technet.com/askperf/archive/2...edirection.aspx

Printer Redirection can also be configured through Group Policy. The setting to prevent client printer redirection is located in the following container: Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Client / Server Data Redirection. The name of the policy setting is "Do not allow client printer redirection" as shown below

[chris.thompson]

Thanks a lot, that seemed to do the trick.