Hp Printer Install Cannot Delete Output File

| 18-09-2021
[RAND-1-100] Comments

Learning has never been so easy!

If you have ever needed to manage printers on a computer remotely (Install, Delete, Modify, Clear a Print Queue) then this article should be helpful.

Fix HP Printer issue on macOS. With a USB cable, or an Ethernet cable, Windows 10 does not automatically install the built-in printer driver. This video shows the steps to follow if the built-in driver failed to install in Windows 10. Remove any icons for your printer from the Devices and Printers folder. Method 1: Run Printer Troubleshooter. As a first step, I would suggest you to run the Printer Troubleshooter and check if that resolves the issue. The Printer Troubleshooter can fix the common issues with printer installation, connecting to a printer and errors with the print spooler—software that temporarily stores print jobs. Sometimes you need a little help to get the best out of your HP products. HP Support created these videos to help answer questions, troubleshoot problems, and even give you some expert tips on.

I am assuming that your are on a domain, have administrative permissions and have remote management enabled for your computers.

5 Steps total

Step 1: Open Print Management as Admin

Click start and search for Print Management. Right Click on Print Manager and Run as Admin. Use credentials with Administrative rights on the remote machine

Step 2: Connect to the Remote Print Server

Right Click on Print Servers and select Add / Remove Servers

Step 3: Add Print Servers

The remote print server is simply the PC or Server you wish to manage.
Type the name of the PC (you can add multiple) and click Add to List.

Repeat until all the devices you want to work with are in the list then Click OK

Hp printer install cannot delete output files

Step 4: Expand the Print Server and open the Printers Item

Once added to the list you can expand the PC Print Server. Then click Printers and you will see the list of all install printers on that device along with the Queue and several other details

Step 5: Manage as Normal

You will now be able to do everything you would normally do when physically logged into the remote PC and using Devices and Printers locally. Including installing and deleting printers, clearing print queues and editing printer properties and defaults.

Keep in mind that this may not be as fast as sitting directly in front of the computer as you are working remotely. Especially when working across WAN Links.

But it sure beats fighting traffic and users for access to a busy PC

Managing printers on remote devices is no harder than managing printers on the local device you are sitting in front off. This feature in windows can be a huge time saver especially when dealing with many remote sites where you can't always kick the user off to fix a printing issue!

Can't Delete Output File

Published: Mar 04, 2016 · Last Updated: Mar 08, 2016

15 Comments

  • Cayenne
    Joshua King Mar 9, 2016 at 01:57pm

    Thanks for the guide. Used it and it works for me, much appreciated!

  • Anaheim
    SkyHigh Mar 9, 2016 at 03:03pm

    Print Manager is great for a small number of servers. However, if you are trying to manage installed printers on your company PCs, then, the more you add, the slower it gets!!!
    Bring back 'view remote printers' in file explorer from Windows 7!
    Good simple guide though, thanks.

  • Thai Pepper
    Jason1121 Mar 9, 2016 at 03:14pm

    Good info to have. Print Manager is without a doubt very handy. However I do miss being able to just browse to a remote computer:

    computername

    And then dig down into 'Printers and Faxes' like we could with 2003 and XP.

  • Cayenne
    mikevandenboom Mar 9, 2016 at 04:50pm

    I am overjoyed....This is the first time I ever saw this.

  • Cayenne
    MarkH3326 Mar 9, 2016 at 06:38pm

    This may or may not be off-topic a wee bit but I did a bunch of research last year to create an automated .BAT batch program as I roll out our company's printers to users' computers. I thought I would share it here in case it is of use to you all. I made it generic and deleted all the printers except one, to keep it simple. Here you go:

    @Echo ----------------------------------------------------------

    REM *** Install Printers .BAT program
    REM *** by Mark H - 201503.26

    REM *** -r = the IP address of the printer
    REM *** -h = the IP address of the printer
    REM *** /m = the label of the printer driver to install found in the .INF file
    REM *** /f = the full filepath and filename of the .INF file
    REM *** /b = The description label which will show up in 'DEVICES and PRINTERS'

    REM *** Line 1 installs the port
    REM *** Line 2 installs the printer driver
    REM *** Line 3 creates the actual printer in the 'DEVICES and PRINTERS' system

    @Echo on

    @Echo ----------------------------------------------------------

    @Echo *** (1) Install HQ - Xerox 7775 printer @ 192.168.20.9

    cscript %WINDIR%System32Printing_Admin_Scriptsen-USPrnport.vbs -a -r IP_192.168.20.9 -h 192.168.20.9 -o raw -n 9100

    rundll32 printui.dll,PrintUIEntry /ia /m 'Xerox WorkCentre 7775 PS' /f 'C:MASTERSPrintersXerox_7775_PS_x64x2DLEXP.inf'

    rundll32 printui.dll,PrintUIEntry /if /b 'HQ - Xerox 7775' /f 'C:MASTERSPrintersXerox_7775_PS_x64x2DLEXP.inf' /r 'IP_192.168.20.9' /m 'Xerox WorkCentre 7775 PS'

    @Echo ----------------------------------------------------------

  • Poblano
    ed.palmer.54 Mar 10, 2016 at 02:43pm

    MarkH3326: I do this a bit differently:

    REM Create port
    Cscript %WINDIR%System32Printing_Admin_Scriptsen-USPrnport.vbs -a -r 10.170.84.34 -h 10.170.84.34 -o raw

    REM Install driver package
    Cscript %WINDIR%System32Printing_Admin_Scriptsen-USPrndrvr.vbs -a -m 'Lexmark MX810 Series XL' -i 'C:Lexmark MX810LMADRP40.inf'

    REM Create printer using driver and port
    Cscript %WINDIR%System32Printing_Admin_Scriptsen-USPrnmngr.vbs -a -p 'Lexmark MX811dtfe' -m 'Lexmark MX810 Series XL' -r 10.170.84.34

    REM Print test page
    Cscript %WINDIR%System32Printing_Admin_Scriptsen-USPrnqctl.vbs -e -p 'Lexmark MX811dtfe'

  • Poblano
    Marek3971 May 5, 2016 at 10:57am

    Thanks so much. I didn't realize how easy I can install printers for users

  • Poblano
    joshuacrussell Oct 3, 2017 at 03:24pm

    Perhaps I'm missing something, but for whatever reason, I cannot run Print Management as Admin. I am a domain admin, my username is in the local machine's administrators group, my account is an admin account, I have full control permissions and I am set as owner for printmanagement.msc, but I still only get the 'run as...' and a permissions error if I click it.
    Any suggestions?

  • Mace
    molan Oct 4, 2017 at 01:10am

    Sounds like you have UAC disabled, make sure it is enabled

  • Poblano
    joshuacrussell Oct 6, 2017 at 08:26pm

    Nope - UAC is enabled. To muddy the waters, I put mmc.exe on my desktop, ran it as admin, then added the Print Management snap-in.
    I added computers from the network as Print Servers, and under printers, I get 'no items to show.'
    The computers have the red down arrow icon - something clearly isn't configured properly. Thoughts?

  • Mace
    molan Oct 7, 2017 at 01:36am

    Start a question thread and reference this how to, you will get better help than going back and forth in the comments section

  • Cayenne
    ChrisN315 Feb 23, 2018 at 03:53pm

    That's handy right there! Saves me a lot of travel.

    Thanks!

  • Datil
    Peter (Action1) Sep 20, 2019 at 05:48pm

    Also, try our solution Action1 to remotely add a printer, remotely remove a printer or other print management operations on remote computers. It works similarly to Print Manager or remotely installing a printer using PsExec or other command line tools, but it is centrally managed and monitored from the cloud. https://www.action1.com/p/Free-Add-or-Remove-Network-Printer-119.html

  • Pimiento
    David4299 Dec 9, 2019 at 07:55pm

    This allows me to see local printers (on the remote PC) only. I can't see any network printers.

  • Jalapeno
    brainjjohns Jan 27, 2020 at 07:31pm

    Wow! That was easy.

    I have heard of this before but didn't realize it would be this simple. I was expecting to have to set up a server specifically to do this. Thank you.

How to add a Foomatic PPD to your CUPS installation?

Author:Robert van den Aker (robert2 AT dds DOT nl)
Version:2006.05.07.0

Introduction

The (optional) foomatic-filters package includes the foomatic-rip filter script from the www.linuxprinting.org website. This script is a clever hack to allow the use of 'traditional' ghostscript devices with CUPS. Some background information about foomatic-rip, its use of traditional ghostscript devices, and how these differ from the special 'cups' ghostscript device, can be found on this page.
Native CUPS printer filters do not use any of the traditional ghostscript devices; they only use the special 'cups' ghostscript device. However, very few driver distributions provide native CUPS filters, and the foomatic-rip trick comes in handy in many cases. An excellent driver distribution that does provide native CUPS filters and accompanying PPDs for hundreds of printer models is Gimp-Print. If you installed the gimp-print-cups package, chances are that your printer is supported by it. Your printer may also be supported by one of the 'sample' CUPS drivers included in the cups package. If your printer is not supported by either of these driver packages, you may yet be able to find a Foomatic PPD for your printer. So what are those Foomatic PPDs?

PPDs and the CUPS filtering chain

PPDs are PostScript Printer Description files. The PPD specification was originally developed as an interface to control printer options for PostScript printers, but in CUPS they are used for all types of printers. If you want more background about the CUPS filtering chain and its use of PPDs, read this article. The gist is that PPDs determine the route that print jobs take through the CUPS filtering chain, most importantly the RIP filter to be used. This can be either one of the native CUPS filters or foomatic-rip. All the different native CUPS filters (controlled by PPDs for hundreds of different printer models) require only one ghostscript device: the special 'cups' device. The foomatic-rip filter does not use the 'cups' ghostscript device. It uses 'traditional' ghostscript devices such as 'cdj500', 'pcl3', 'ijs', etcetera instead. Different PPDs that use foomatic-rip often require different ghostscript devices.

Printer drivers, ghostscript devices and external ghostscript filters

In the olden days, every printer driver was a separate ghostscript device. This meant you had to recompile ghostscript for every new printer driver. A newer method is to have a common ghostscript device call an external program (also called a filter; distinct from CUPS filters), which controls the printer options for the different models supported by the filter. This means you do not need to recompile ghostscript every time a new printer model comes out; you just update the external filter program. One of these external ghostscript filters is 'hpijs'. It can be used in tandem with either the (oldish) 'hpijs' ghostscript device or the (new) 'ijs' ghostscript device.
Foomatic PPDs for the hpijs ghostscript filter are provided by the hpijs-ppds package and will already be installed and available for selection in the CUPS web interface if you installed that package. Other Foomatic PPDs need to be downloaded from the www.linuxprinting.org website and installed according to the instructions below.

Example installation of a Foomatic PPD

Printer

In this example we'll locate, download, and install a Foomatic PPD for my HP DeskJet 400. This printer -- like almost all HP printers -- is already supported by one of the 'sample' CUPS filters and by Gimp-Print, which I also have installed, so I do not strictly need a Foomatic PPD to use this printer. In addition, if I want to use a Foomatic PPD, the Foomatic PPD for hpijs for this printer was already installed by the hpijs-ppds package, so I can use the hpijs driver (the recommended driver for this printer, as we shall see) right away. However, I'll add another Foomatic PPD for my printer for the sake of the example.

Step 1: locate the Foomatic PPD for your printer model

Go to www.linuxprinting.org and choose 'Printer Listings' under 'The Database', or go there directly by following this link.
I choose the HP DeskJet 400, which takes me to this page.
As you can see, there are many drivers to choose from for my printer: hpijs, cdj500, hpdj, pcl3, stp, hpijs-rss, gimp-print, and gimp-print-ijs. We can quickly discard three of these: stp is the old 'traditional' ghostscript device from the Gimp-Print distribution; gimp-print is the new 'stp' ghostscript device; gimp-print-ijs is the external ghostscript filter from the Gimp-Print distribution that uses the 'ijs' ghostscript device. We're not going to use any of these: if we want a Gimp-Print driver, we'll use the native CUPS filters provided by the gimp-print-cups package.
We can also discard hpijs-rss as an older, albeit patched, version of hpijs than the one we have installed, and hpdj as an older version of the pcl3 driver.
This leaves us with three choices: hpijs, cdj500, and pcl3. hpijs is the recommended driver for the HP DeskJet 400 and we would normally download the PPD for hpijs, but since it was already installed by the hpijs package, we'll choose the cdj500 driver for this example.
The page says that the type of the cdj500 driver is 'Ghostscript'. This means that you need to have the 'cdj500' device compiled into ghostscript if you want to use the cdj500 PPD. To find out what devices were compiled into ghostscript, examine the output of the gs -h command (the 'ghostscript' command executed with the 'help' switch). You may want to pipe the output through 'less' for easier reading ( gs -h |less ). Lucky for us, 'cdj500' is listed, so we can use this PPD. The astute will have spotted the 'pcl3' device, the 'ijs' device, which is used by the hpijs ghostscript filter, and the 'cups' device, which is used by the native CUPS filters, among the available devices.

Cannot Open Output File

Step 2: download the Foomatic PPD for your printer model

Click the 'download PPD' link. If your browser has trouble setting a reasonable filename for the PPD, you can rename it after downloading to the name suggested in the PPD. The extension must be .ppd and the file must be world-readable.

Step 3: install the Foomatic PPD for your printer model

Hp Printer Install Cannot Delete Output Files

After downloading (and possibly renaming) the PPD, you need to put it in the right place. PPDs go in /usr/share/cups/model/. You can put it in a subdirectory if you prefer. You can also compress it with gzip if you like. I put the compressed PPD HP-DeskJet_400-cdj500.ppd.gz in the /usr/share/cups/model/foomatic-ppds/HP/ directory that was created by the hpijs package.

Step 4: reload cupsd

Next you need to reload cupsd (as root) to register the new PPD.

[root@hostname root]# /sbin/e-smith/service cupsd sighup

Step 5: add a printer that uses the new Foomatic PPD

Finally you need to add a (filtering) printer that uses the new PPD, as explained in this howto.
The PPD adds a new 'model' to the CUPS web interface. The PPD that I installed in the example adds the 'HP DeskJet 400, Foomatic + cdj500 (en)' model in the 'Hewlett-Packard' category. I had to change some of the driver settings (this is done through the 'Configure Printer' option on the printers page in the CUPS web interface) before I was able to successfully print a test page. The only 'color mode' that worked with my black ink cartridge was 'Floyd-Steinberg Gray'. I was not pleased with the result of the test page: printing was dead slow and the output quality rather poor. I then installed the PPD for the 'pcl3' driver, and that was much better, so I removed the printer that used the 'cdj500' driver and kept the 'pcl3' printer.

This document is Copyright 2003-2006 by Robert van den Aker. It may be freely redistributed in its entirety provided that this copyright notice is not removed.