TCP/IP Printer removal (also drivers)

Follow
Brandon Carder

Hello all,

I need help with a script that will not only remove *every* existing TCP/IP printer, but also purge the drivers (if possible). The environment I'm at now never had a print server,and the existing sysadmins just added TCP/IP printers. Every department has different printers. You can imagine, it's going to be a lot of manual work to rip and replace. I've tried just about everything I could via 3 days of research, and nothing is working.

I obviously want to automate this through PDQ Deploy, but just can't find the magic script/command.

Has anyone been successful in doing this?

0

Comments

7 comments

Date Votes
  • Valerie L Boss

    I just tried the Clean Up All Printers package under Utilities, and it did not remove the printers on my test machine.  Interestingly, if I run it from the local machine, it runs just fine and deletes the printers.  Have you tried this utility?  

    0
    Comment actions Permalink
  • Brandon Carder

    Hi Valerie,

    Where is this tool? Thanks!

    0
    Comment actions Permalink
  • Valerie L Boss

    I have attached the batch file.  I believe it is in the most recent PDQ Deploy Repository release, v39.1 // 2016-02-04.  You can find it here: https://www.reddit.com/r/sysadmin/comments/427fy2/pdq_deploy_packs_v390_20160122_full_refresh/

     

     

     

    v39.1 // 2016-02-04

    0
    Comment actions Permalink
  • Dan Sadler

    I run into the same issue, where if I deploy this with PDQ it does nothing, but if I run the .bat locally it removes it fine. 

    0
    Comment actions Permalink
  • Dan Sadler

    Where is Stephen when you need him? :)  I know he can write up something to Remove Network Printers. 

    0
    Comment actions Permalink
  • Valerie L Boss

    @Dan, 

    I've run into this before, and am unsure how to get around this issue.  The issue:  Some batch files or install programs must be run manually to work, and deploying a package with the commands does not work, regardless of the user chosen by the package.  I would love to get some clarification as to why this happens and how to prevent future issues like this.

     

    0
    Comment actions Permalink
  • Aholgate

    Would it be possible to push the batch file to the local machine and then run the batch file from the machine executing it with PDQ?

    I'm running into this exact issue now that we are doing branch updates with the same past printer install issues.

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post