Jump to content

Recommended Posts

Posted

Hi,

 

Bit of a strange one. We have a 2008r2 server that is also a print server. The school had a new printer delivered. I deleted the old one from print management and the removed the group policy object deploying the printer and I removed the printer from the devices and printers section on the server. However, when the domain clients log on the printer is still there and it is coming from the server with the "printer name..on server1" tag on the name.

 

Anyone any clues as to why it would still be visible even though it is no longer deployed from nor connected to the server?

 

Stuck in profile perhaps?

 

Thanks.

Posted
No idea, but to mitigate the effect, how about adding an extra 'delete all printer connections' object in the preferences of the GPO that deploys your printers?
Posted

Is that policy > control panel > new > TCP/IP printer > set to delete all IP printers?

 

Tried that, but it was still there, but so was the printer deployed via print management so not sure it worked.

Posted
I reckon your right with its in the user profile, either delete the profile or add a logoff script to remove the printer connection (its easier to removeallprinterconnections)
Posted

Is there a legacy script applying?

 

If not, I never got deploying via Print Management working the way I liked it so used Group Policy Preferences to deploy. Can't remember if that's feasible on 2008, but running the "delete all shared printers" seems to get rid of any old 'uns on 2012.

Posted

I had an issue years ago with staff collecting printers as they logged on in different areas of the school, so I found the following VBS script that's worked perfectly ever since - it runs just before the Add Printers script at logon...

 

' don't display any error messages
On Error Resume Next

strComputer = "."

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set colInstalledPrinters = objWMIService.ExecQuery _
   ("Select * From Win32_Printer Where Network = True")

For Each objPrinter in colInstalledPrinters
   objPrinter.Delete_
Next

  • Thanks 1
Posted
Thanks guys!

@RichCowell, is there anything to modify on that script or just save it as .vbs and run it as a logon script?

 

Not a problem... Shouldn't be anything to modify, I don't think I did - it's worked on 32 and 64bit PCs... Just save as VBS and run at login as you said...

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...