Hello,

here is a script, which can be used to demonstrate that scripting IPP printers is not really possible with windows.It works forone printer at a time, but not for many.

Setup:

You need a IPP server, the correct drivers in the driver directory and the real available printers need to be pre-configured in the script.

If I use this script with ~10 printers, and enable multi selection in the script, windows becomes unresponsive,the CPU fan is getting louder and louder, a short time after this, a ResourceBroker.exe takes over and says that windows is overloaded, and no printer is working at all. After that, windows needs to be rebooted.

But the script works, if you install one printer after another.

The good thing, is that IPP printing works fine after it is setup, for example simple laptop usage, with one printer. But it does not scale into normal terminal server environments, simply because Microsoft does not support this properly:

 v4 printer drivers and custom port monitor options

One start would be to add an IPP port with Powershell, and not using this rundll32  workaround, then make it work to install printers fast enough, without crashing windows.

You can add an lpr/tcp printer ports with powershell, but not an IPP printer port.

Additionally, using the "native" RPC/smb based printing solution, with a windows print server 2016 does not work reliable too. For example I need to reboot one Terminal server in a week (of around ~40), because it cannot connect to a shared printer anymore. The printing client (TS-Server) error message is: "insufficient system resources", but that is another story. But maybe someone knows a solution for this (?)

This script only shows, that scripting ~10 IPP printers with powershell crashes windows.

best regards,

printersprinter

# interactive Printer installer
# This installs the PCL driver for Konica Minolta
# 
# - switch from get-wmiobject, because it takes ages (queries printer states)
# - switch to multiselection, but deactivated it, installing many printers "overloads" windows somehow
# 


#Setup:
# In this directory a direcory "driver" is needed, which contains
# the .inf installer


#Catch error
try
{

# Messagebox
$IPP_SERVER="http://192.168.42.42:631"

Add-Type -AssemblyName System.Windows.Forms
[System.Windows.Forms.MessageBox]::Show("Connect PC to a network where IPP server $IPP_SERVER is available ","Printers can only be installed if the IPP Server is available",0)


# helper function to get the current start location
function Get-ScriptDirectory {
    $Invocation = (Get-Variable MyInvocation -Scope 1).Value
    Split-Path $Invocation.MyCommand.Path
}

$scriptpfad = Get-ScriptDirectory
$treiberpfad_hp =  "$scriptpfad\driver\hp"
$treiberpfad_canon =  "$scriptpfad\driver\canon"        
$treiberpfad_KM_PS =  "$scriptpfad\driver\KonicaMinolta\ps"     
$treiberpfad_KM_PCL =  "$scriptpfad\driver\KonicaMinolta\pcl"   
#$DruckerTreibercmdhp= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_hp\hpcu190v.inf /m "HP Universal Printing PS" /h "x64" /v "Type 3 - User Mode" }
#$DruckerTreibercmdcanon1= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_canon\CNS30KA64.inf /m "Canon LBP7780C/5480 PS3" /h "x64" /v "Type 3 - User Mode" }
#$DruckerTreibercmdcanon2= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_canon\CNS30KA64.inf /m "Canon iR C1028/1030 PS3" /h "x64" /v "Type 3 - User Mode" }
#$DruckerTreibercmdcanon3= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_canon\CNS30KA64.inf /m "Canon LBP6680/3480 PS3" /h "x64" /v "Type 3 - User Mode" }
#$DruckerTreibercmdcanon4= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_canon\CNS30KA64.inf /m "Canon iR-ADV C2225 PS3" /h "x64" /v "Type 3 - User Mode" }
$DruckerTreibercmdKM_PS= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_KM_PS\KOAXNA__.inf /m "KONICA MINOLTA C360iSeriesPS" /h "x64" /v "Type 3 - User Mode" }
$DruckerTreibercmdKM_PCL= {rundll32 printui.dll, PrintUIEntry /ia /f $treiberpfad_KM_PCL\KOAXNJ__.inf /m "KONICA MINOLTA C360iSeriesPCL" /h "x64" /v "Type 3 - User Mode" }

#$Printercmdhp= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_hp\hpcu190v.inf /r $IPP_SERVER/printers/$Drucker /m "HP Universal Printing PS"}
#$Printercmdcanon1= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_canon\CNS30KA64.INF /r $IPP_SERVER/printers/$Drucker /m "Canon LBP7780C/5480 PS3"}
#$Printercmdcanon2= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_canon\CNS30KA64.INF /r $IPP_SERVER/printers/$Drucker /m "Canon iR C1028/1030 PS3"}
#$Printercmdcanon3= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_canon\CNS30KA64.INF /r $IPP_SERVER/printers/$Drucker /m "Canon iR-ADV C2225 PS3"}
#$Printercmdcanon4= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_canon\CNS30KA64.INF /r $IPP_SERVER/printers/$Drucker /m "Canon LBP6680/3480 PS3"}

$PrintercmdKM_PS= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_KM_PS\KOAXNA__.inf /r $IPP_SERVER/printers/$Drucker /m "KONICA MINOLTA C360iSeriesPS"}
$PrintercmdKM_PCL= {rundll32 printui.dll, PrintUIEntry /if /b $Drucker /f $treiberpfad_KM_PCL\KOAXNJ__.inf /r $IPP_SERVER/printers/$Drucker /m "KONICA MINOLTA C360iSeriesPCL"}

Write-Output "Testing $treiberpfad_KM_PCL"
$lexist=Test-Path -Path $treiberpfad_KM_PCL

if (-not (Test-Path -Path $treiberpfad_KM_PCL)) {
    # we cannot install without driver 
    Write-Output "The drivers are not available"
    exit
}
$PCL=$true

# Postscript
#$PCL=$false

if ($PCL) {
        $PrintercmdKM=$PrintercmdKM_PCL
        $DruckerTreibercmdKM=$DruckerTreibercmdKM_PCL
} else {
        $PrintercmdKM=$PrintercmdKM_PS
        $DruckerTreibercmdKM=$DruckerTreibercmdKM_PS
}


# create fixed list of printers
$printersE="printerE1", "printerE2", "printerE3"
$printersF="printerF1", "printerF2"

$printersX=($printersE+$printersF)


# create List of printers
$arrayPrinters=New-Object System.Collections.ArrayList
for($i=0; $i -lt $printersX.Length ; $i++) {
   #$arrayPrinters.Add($printersX[$i])
   $arrayPrinters+=$printersX[$i]
}

for($i=0; $i -lt 10 ; $i++) {
   #$arrayPrinters.Add($printersX[$i])
   $arrayPrinters+="dummy$i"
}
# Ask user which printer to install
# supports multiselection
$DruckerListe = $arrayPrinters |Out-GridView -PassThru -Title "Select your printer!"

# I testet multiselection, but when I selected many printers, a "resourcebroker" messages
# pops up, saying that windows is overloaded and all printers do not work with
# varying error messages (even after reboot)
# Therefore this script only allows one printer installation at a time.
if ($DruckerListe.Count -ne 1) {
        [System.Windows.Forms.MessageBox]::Show("Unsupported Selection", "You can install only one Printer at a time",0) 
        exit
}
#Install Driver
        Invoke-Command -ScriptBlock $DruckerTreibercmdKM
        # remove printer if it is already installed with that name
        # The WMI Object lookup takes around 20 Seconds for 5 installed printers, Get-printers is much faster
        # (less than a second)
        #$Installierteprinter = @(get-wmiobject win32_printer |select name)
        $Installierteprinter = Get-Printer | Select Name
        #remove any existings printer
        foreach ($i in $Installierteprinter){
                #Write-Output "Teste $($i.name)"
                foreach($wantName in $DruckerListe) {
                        #Write-Output "Teste $($i.Name) in $wantName"
                        if ($wantName -match $i.Name) {
                                Write-Output "Removing: $($i.Name)"
                                remove-printer -Name $i.Name
                        }
                }
        }
        # all printers are removed
        #exit 
        # install the printers
        # If multiselection is on, this will overload windows
        # until a message appears "Resourcebroker.exe"
        foreach($Drucker in $DruckerListe) {
                # Drucker installieren
                #Write-Output "Installing: $PrintercmdKM"
                Invoke-Command -ScriptBlock $PrintercmdKM
                Write-Host -ForegroundColor DarkYellow "Printer $Drucker was installed"
        }  

}
 
catch  
    {
    $ErrorMessage = $_.Exception.Message
    $FailedItem = $_.Exception.ItemName
    Write-Host $ErrorMessage + " " + $FailedItem
    }

We have a print server that is running the Print Management utility built into Windows Server 2012 R2. Many users keep calling to report thatsome (not all) of their printers keep disappearing. Running gpupdate /force usually brings all the printers back but that's not a worthwhile fix since we have to keep doing it.

I have all company the printers deployed to me and even when I run gpupdate /force, some missing printers will appear. Why aren't they all showing up in the first place?

This mostly happens on our RDS servers (running Server 2012 R2), but it does occasionally happen on our local computers (all running Windows 10 Pro 1809 and 1903) as well. All computers are running with the latest updates and all print drivers are up to date.

Does anyone know what's causing this and how we can fix it?

I configured Hybrid Cloud Print on this page:

https://docs.microsoft.com/en-us/windows-server/administration/hybrid-cloud-print/hybrid-cloud-print-deploy 

all the way to Publish printer. The Publish-CloudPrinter powershell command won't work. I get an IIS Web Core MapRequestHandler error 0x8007002. No folder https://internalserver.local:443/mcs/publish.

Same when I test Mopria via accessing https://mopriadiscoveryservice-tenant-name.msappproxy.net/mcs/services (with my tenant set). I get HTTP error 404.0 - Not found.

There are no Service or Publish folders in the Mopria folders in IIS so it should be running code. I'm not a dev so not sure how to work out why it isn't running it. All looks correct according to the article.

If I switch the https://mopriadiscoveryservice-tenant-name.msappproxy.net/mcs/ to directory browsing I can see the contents in a client pc so authentication is working fine.

Any ideas?

Hi,

We have a Windows 2012 R2 Print server with Samsung printers installed,

The printers are configured and shared properly with the latest drivers and all users can print to them successfully with the below exception:

if user open a JPG file with the 'Microsoft Photos' application and try to print, the file is sent for printing but eventually the printer does not print anything,
If user open the same file with the Paint (mspaint.exe), the user can print to the same printer successfully and file really getting printed,

Same issue with Microsoft Edge, if trying to print from Microsoft Edge nothing is being printed, but if trying to print via IE or Chrome it is getting printed successfully,

When looking in the print service event log on the server, I can see that when the printer doesn't print anything I see the below events:

Document 65, Print Document owned by XXXX on XXXX was printed on Samsung SCX-5835 6th Floor Reception through port XXXX.  Size in bytes: 20036.Pages printed: 0. No user action is required.

The print spooler failed to delete the file C:\Windows\system32\spool\PRINTERS\00066.SHD, error code 0x5. See the event user data for context information.

When it is printing successfully I can see that the 'Pages printed' is not 0 and I don't get the error,

If the printer is installed locally as a standard TCP/IP port (without printing to a print server) the file is being printed successfully even with the 'Microsoft Photos' application, it only happens when using 'Microsoft Photos' or 'Microsoft Edge' when printing to the Print server, 

Could anyone please help how this can be solved?

Thanks

I am unable to install any networked HP printers on windows 2012 R2.

Using a Print Server errors with "Windows cannot connect to the printer" 0x0000003eb

Using the TCP/IP or print server with Universal PCL6 driver (6.5)

errors with "Unable to install printer. Cannot complete this function".

Using the TCP/IP with the printer specific driver (64 bit)

errors with Unable to install printer. %1 is not a valid win32 application.

The only way to successfully install a HP printer is to use class drivers (version-4) however the printer preferences and properties are not accessible and receive %1 is not a valid win32 application error.

I have tried several suggested solutions found on the internet (delete version-3 printers in reg, delete "3" folder in C:\Windows\System32\Spool\Drivers\x64) but none of them worked. Please help!

I enabled enhanced icons in Devices and Printers on a print server running 2012 R2, which initially worked great.  However, the next day one of the icons reverted back to a non-enhanced icon.  I'd like to refresh this.  

I have two specific questions:

1. How can I force a refresh on the "enhanced" printer icon?
   
2. Where are the settings for toggling this feature on and off?  I also want to prevent print drivers from being automatically being updated, which I initially enabled. Now I cannot find the way back to those settings, which initially showed under the menu bar until activated. 

Thanks.

Windows 2008 R2 Server, running Print Services.

I am able to create printers/queues without problem.  If I open a browser and go to \\server  I can see the printers and connect to them just fine.

My next step is to add the printer to Active Directory.  I open MMConsole, browse to the container, right click, select New-Printer, and type in the printer name (\\server\Printer Name).  Upon hitting enter I get the following error.

"The printer cannot be published. To publish printers on computers running the Windows 2000 or Windows Server 2003 operating systems, use the Printers folder."

This is occurring on new or old print queues.  Doesn't matter what container it's in.  We were able to add printers via this method a couple days ago.  The only change made on the printer server was adding a SSL certificate for Papercut (print paper management software).

Thoughts? Solutions? Ideas?

I have a remote office that connects to our main office server via router-based VPN (not running a VPN server on Win16 itself, just letting the ASUS router handle it). The remote sites router is set to autoconnect to the main sites router, so everything that hits it is on the VPN. Everything works peachy, but my life would be a lot easier if I could install a couple of the remote printers directly on the main server and share out from there...Seems like there should be a simple way to see the remote site printers via IP but I can't seem to puzzle it out.

FYI I do have different subnets at each site to prevent conflicts (32.xxx remote, 62.xxx local). 

Hello,

This may seem like a dumb question, but I'm starting this project from scratch.  

We deployed a new print server 2016.  The older servers I've inherited, but this is the first one from scratch. My question is: when I'm adding drivers via Print Management, do I install/add the drivers of the clients that will be connecting and installing the printers (Windows 10) or the print drivers for the server for that particular printer (Server 2016 Drivers)?  

Reason I ask is some of the models of printers have Windows 10 Drivers, but no Server 2016 Drivers.  I've seen that some drivers are the same versions no matter what OS you pick. Could always use the HP Universal Print Driver (UPD).

Unsure about what the best practices for this are.

Hi All,

I have a Windows Server 2016 Standard x64 server installation which can't print using either the built-in "Microsoft XPS Document Writer" or "Microsoft Print to PDF". The system has all the latest updates applied up until August 2017.

Actions Performed Before Noticing Malfunction

- Utilized Print Management > Export printers to file from Windows Server 2012 R2 x64 system

- Took exported file from Windows Server 2012 R2 system and used Print Management > Import printers from file into Windows Server 2016 server

What Works?

- All non-Microsoft printers that were imported work without error. These include Lexmark and HP printers and their drivers.

What actions performed produce the problem?

- Open notepad > file > print > Microsoft XPS Document Writer > Print button is grayed out

- Open Print Management > Print Servers > Local Server Name > Printers > Right Click on "Microsoft XPS Document Writer" > Select Properties > Error Message"The 'Microsoft XPS Document Writer v4' printer driver is not installed on this computer. Some printer properties will not be accessible unless you install the printer driver. Do you want to install the driver now?"

    a. If you say yes to install it now and go through the motions to use the driver in "C:\Windows\System32\spool\tools\Microsoft XPS Document Writer" it comes up with"Unable to install Microsoft XPS Document Writer v4, Type 4 - User Mode, x64 driver. The system cannot find the file specified."

I've run the DISM tool to check for corruption, none found.

Admin CMD Prompt > "DISM /Online /Cleanup-Image /CheckHealth"

No corruption found.

Running a file system check using "sfc /scannow" from and admin command prompt came back clean.

Notes of Interest

The one thing I've found so far that is interesting is when comparing the XPS Printer driver on a working system against the non-working system.

Driver Details Working System

Non-Working System Driver Details

On the working system image above you'll see it has a configuration file defined and the dependent file of UNIRES.DLL uses a full path. On the broken system the configuration file is missing and UNIRES.DLL does not use a full path. Same thing for the driver"Path:" value.

Going to try and use process monitor next to see if I can spot any permission problems, etc.

Does anyone have any other suggestions on how to repair the built-in Microsoft XPS Document Writer short of reinstalling the operating system? I've been unable to get this problem to reproduce on our other working systems.

Problem: Win 10 creates multiple instances of the same printer.

Request: Fix this bug so it stops happening.

I know how to delete the printers and reinstall the ONE printer that I want to use. Win 10 keeps creating multiple copies of it.

THIS IS OLD. PLEASE FIX THE BUG.   [Please understand this line to be screaming in frustration.]

Yes, I have search the KB and Support Community (so called) and there is fix found.

Any idea why Excel 2016 would print b&w on a color printer?  Is that a default setting?  All Windows Apps do it too, by the way (Photos, Edge...)

Hi All,

I am in the middle to creating a plan to upgrade our print server from W2008 to W2012 or W2016. This is due to W2008 Server sunset.

I am unsure how to approach this whole process. Its the first time I have ever migrated a print server that has in excess of 100 print queues.

My thoughts are

1. Install server 2012 or 2016 as an in place upgrade. Basically upgrade the current Operating system and leave everything else intact.

2. Create a new Server. Copy the print queues over to the new server and test.

Are there any other ways that could be considered. Any help would be greatly appreciated.

Regards.

hi,

my dad just requested me call oki about horizontal lines appearing on print-outs. is there any way to fix this problem? 

Is there any way to show what client machines are connected on a windows 2012 print server?

In other words which windows 7 machines are currently using a network printer shared off of the print server?  Something like in computer management where you get to see open files on server.