multiples of the same network printer (x6) NO GPO DEPLOYED PRINTER?!

[chazzy2501]

I'm pulling what left of my hair out on this one... I deployed a new imaged PC to my domain (for testing from WDS) and with a user that has no printer GPOs in a computer OU that has no printer GPOs, my client PC picks up one of my network printers!

 

ok, so expecting no printers I in fact get a network printer added 6 times, the same printer. What is really strange is that if I delete all 6 in a few minutes they add them selves back?! Whilst I'm logged in, looking at installed printers.

 

wtf?

 

 

I've scoured all my GPOs for hidden scripts, deployed printers, loopback processing. The Group policy modelling shows no printers, or scripts. Can a phantom printer be brought across from the original image (after a sysprep?)

 

Local event logs contain no strings for the print server or "printer" so I don't know how this is getting added.

 

I've installed this image on other PCs and it hasn't occurred, but most PCs have this issue.

[bald_pig]

Have you checked RSOP?

[GaryPad]

Open the Event Log and expand out Applications and Service Logs | Microsoft | Windows | Print Service. You should see Admin underneath with a red dot (meaning it's enabled) see if there is anything useful in there. You can also right click on Operational and choose Enable Log (so it gets a red dot too!) and try your delete trick again to see if it logs what's happening. Printer deployment can also be a login script so try logging in as a different user to see if they get the printers installed.

[chazzy2501]

I did check the event log but didn't notice that that log @GaryPad was disabled!

[chazzy2501]

Printer {blahblahblah} was resumed. No user action is required... ?

 

pic

 

[GaryPad]

Did you try logging in as a different user and did they also get those print queues deployed to them? Just a thought - are you testing PaperCut's Print Deploy by any chance as this could push queues out (but then it would have the Print Deploy Client installed)?

There's an archaic way of adding Windows which might be in play here. Open a command prompt as Admin and run this command to delete a globally assigned printer:

 

rundll32 printui.dll,PrintUIEntry /gd /c\\%computername% /n\\server\printername

 

Where "server" is your print server and "printername" is one of those print queues - repeat for all 6. It's interesting that your log has 6 entries - I presume each one is for your 6 rogue queues?

[chazzy2501]

They seem to be part of the image, I did a vanilla install from the WDS server and the issue does not present. I'm making a new image now and will not touch the printing whilst making it.

 

Yes every user (even local users) get the printers.

 

I've deleted every regkey directory I can that are linked to the rouge printers but they pop right back

 

I've been going through this thread: https://social.technet.microsoft.com/Forums/windowsserver/en-US/71d06204-3735-4473-8bc9-20be9e19090e/problem-with-multiple-instances-of-shared-printers-being-installed-on-client-computers-when-the?forum=winserverprint