Hi we have an issue where some users are not seeing any printers listed when they try to print from any applications, not just office.

When we add a printer we get a message saying default printer cannot be set when click finish on add printer wizard.

The print spooler is running, restart doesn't help. Deleting the printer and removing all drivers and packages doesn't.

I have enabled LPR monitor in print and document features. I have created a single test printer on anew print server and still get the same issue - no printers listed.

You can add a printer through add printer in Office but you still don't see it listed.

Some users who reboot fixes the issues where others it don't. The print services are configured to MS best practices.I also noticed that if you go device and printers through control panel and select a printer you do not see any options for printing such as print properties, preferences etc.

I have no idea what else it could be, has anyone come across this before?

Is there a way to apply user/group security permissions to a printer/queue for LPD print jobs coming into a Windows Server?

Security permissions on a print queue don't appear to keep non-member users from sending print jobs via LPD server, only if we send print jobs with SMB (authentication). If I send a print job from i.e. Unix, using "lpr -P PrinterName filename.txt -U userdude", and user "userdude" doesn't exist as a local or AD user (or part of a local or AD group), the print job is still accepted by the Windows Server LPD Service and processed/printed. 

Strange behavior:  If I delete the "xyzmachine\Administrators" group from the server printer queue, the Windows LPD service will not accept any jobs via LPD for that printer queue.  Add "xyzmachine\Administrators" back to the printer queue security permissions, and LPD jobs for all users are accepted again.  So I can't whitelist specific local or AD users/groups for incoming Windows Server LPD jobs.

Has anyone found a way to deal with this issue?  Or is that part of the reason the Windows Server LPD service is depreciated and just use SMB?

Thanks,

Pete

Info:  Windows Server 2016, Print Server Installed, LPD Service installed, AD bound, printer queues configured.

Hello,

Windows has man different views, and some things can be controlled from

powershell, other not.

Here's another annoying example. Sometimes you get "Unknown" Printers.

They are listed in the Settings->Device GUI view and can be seen on the PS

prompt with:

> Get-PnpDevice -Class "PrintQueue" -Status "Unknown"

Status     Class           FriendlyName        
Unknown    PrintQueue      \\prs\pFloor0

These printers cannot be removed from powershell, in user context.

If I use the GUI dialog (Settings->Devices) its possible, they disappear

on the powershell prompt they are still visible.

I had one server with ~100 of them.

The search term is "Ghost printer windows", but I havent found a way to get grid

of them from user context.

One solution was to use devcon.exe and a powershell wrapper to get rid of them,

this needs an UAC / Admin.

Maybe there is a better solution for this?

best regards,

printersprinter

Hello,

I don't understand why : there are many printers queue on the RDS server.

I deploy printers by GPO.

Sorry, i can't join image : "Body text cannot contain images or links until we are able to verify your account." :(

I have been asked to devise a way to get information from my print server to tell how many print jobs per month a user is printing. I have already found posts regarding using a powershell script in order to pull event viewer info from Event ID's 307 and 805. However, they seem to be for the PowerShell advanced or Professional. I'm trying to not spend a whole lot of time on this, is there any way to get these audits just by using Event Viewer? Has anyone done this in the past?

Thank you,

Darin

Hi all,

We have a problem to add usb printer on printer management, used on rds application.

Scenario:

printer connected via usb: print1
computer on connect the printer: comp1

On comp1, we share the printer, with this name: \\comp1\print1

Now, we add on the printer server (server1) that contains printer management, this shared printer, with the name: shared1 
If we add new local printer in the printer management, is posible to add the printer, and the test page work properly! \\server1\shared1 

The problem: we want to use the printer on a RDS application. The printers that the application use, are mapped via GPO when the user connect to the terminal server of RDS. If we want to use the printer mapped \\server1\shared1 , the print fails with this error:

There're some way to do this redirection or use on the RDS sessions a USB printer remotly? 

Regards,

Gerardo,

HI!

help me please understand.

What will work better Microsoft enhanced Point and Print compatibility driver or native v3 driver in a network with windows server 2016 print server and windows 7 clients? Which option does Microsoft recommend?

Hello All,

I have an organization with about 15 dell thin clients around a warehouse. They pull Windows 10 from the server and all of their other resources. Whenever the thin clients power cycle every single one of them default to the same printer. An HP LaserJet. Most of the thin clients have their own printer next to them that we have set as individual default multiple times. 

Why are these thin clients all defaulting to to the same printer even though we have set the individual default on each machine? None of the printers are set as default on the server either, they are just shared out. Also no GPO in place that assigns a printer.

Any ideas are appreciated thanks. 

Hi all,

Windows server 2016

I installed printers and shared them to some users (for me too), everything worked fine for few days. Suddenly they have an access error (users poweroff and poweron their laptops from which they print). 

Me (instead of poweroff) hibernate my laptop, and haved possibility to print without any errors. But, when I reboot my machine I got the same errors as my users.
Printer setup was not changed on server on this days, only i tryed to install the MultiPoint role, with fail (I have icons, and when I try run them I got an errors).

I changed permissions to full control to printers (allow - print, manage printer, manage documents) and still nothing.

UPDATE:

I noticed that, in event viewer there is loots of Security logs for Audit Failure:

• An account failed to log on.
  
  Subject:
  Security ID: NULL SID
  Account Name: -
  Account Domain:-
  Logon ID: 0x0
  
  Logon Type:3
  
  Account For Which Logon Failed:
  Security ID: NULL SID
  Account Name:<MY_DOMAIN_USERNAME>
  Account Domain:<MY_DOMAIN_NAME>
  
  Failure Information:
  Failure Reason:Unknown user name or bad password.
  Status: 0xC000006D
  Sub Status: 0xC0000064
  
  Process Information:
  Caller Process ID:0x0
  Caller Process Name:-
  
  Network Information:
  Workstation Name:<MY_LAPTOP_WORKSTATION>
  Source Network Address:<MY_LAPTOP_IP>
  Source Port: 50087
  
  Detailed Authentication Information:
  Logon Process:NtLmSsp 
  Authentication Package:NTLM
  Transited Services:-
  Package Name (NTLM only):-
  Key Length: 0

I work in domain network, server is not connected to domain, only connected to network, and accounts are created locally, users map shares (folders/printers) using local account created on server.

So, why connection to printers is try use Domain credentials instead of local (users already have mapped network share using server local account).

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.

I'm looking for the FAX & Scan "Sent Items" log in a server 2008 (32 bit) backup; and once I find it how do I view it?

Hello,

the following powershell script shows, that the Get_Printer Command

does not directly retrieves the complete list  of installed printers.

The more often you call Get-Printer the more printers you will

get, until you have all of them

Reproduceable with : In Logon scripts, but that not easy to debug,

its the same, after a rdp disconnect/reconnect.

best regards,

printersprinter

<#

Sample Output after rdp reconnect to Windows 2016 Server.

PS D:\TEMP> .\waitForPrintSystem.ps1
Printer System starting:6 0 0 0
Printer System starting:6 7 0 0
Printer System starting:6 7 7 0
Printer System starting:6 7 7 7
Printer System stable after 4 tries
PS D:\TEMP> .\waitForPrintSystem.ps1
Printer System starting:0 0 0 0
Printer System starting:0 1 0 0
Printer System starting:0 1 1 0
Printer System starting:0 1 1 2
Printer System starting:7 1 1 2
Printer System starting:7 7 1 2
Printer System starting:7 7 7 2
Printer System stable after 7 tries

#>


#
# During logon testing and seeing that my script
# does not work in most cases during logon,
# this is another idea.
# I found out, that calling the
# method Get-Printer a few times
# makes the result look better, each call.(Windows!)
#
# How to reproduce:
# - The problem occurs in a LOGON Script, but can be
#   reproduced with an RDP session and disconnect
# - You need some UNC Printers, I have 7
# - Leave a powershell open, disconnect your RDP session
# - wait two minutes, reconnect
# - start the script
# You will see:
# On the first call after disconnect, its empty: $null,
# On the seconod call I have one printer
# On the third: two
# On the fourth: 7 (this is correct the end result)
#
# So we implement the WarmUp phase like this:
# Do not run for more that ten seconds
# if the last four times we have the same result, we assume
# that everyting is fine.
#
# returns the "warmup array"
function WaitForPrinterSystem {

    $cnt=0
    $oldPrinterCount=0
    $lastEntries=(0,0,0,0)
    $back=@()

    while($true) {
        $List=(Get-Printer).name | select-string -pattern '^\\'
        #Write-Debug("List:$List")
        if ($List -eq $null) {
            $List=@()
        }
        Sleep 1
        $back+=$List.Count
        $lastEntries[$cnt % 4]=$List.Count
        if ($cnt -gt 3) {
            # first shortcut break out early
            $UniqueNumbers=$lastEntries | Get-Unique
            #Write-Debug("Unique Printers:$lastEntries Unique: $UniqueNumbers")
            if ($UniqueNumbers.Count -eq 1) {
                Write-Host("Printer System stable after $cnt tries")
                break;
            }
        }

        $cnt++
        if ($cnt -gt 10) {
            Write-Host("Printer System still booting. Timeout.")
            break
        }
        Write-Host("Printer System starting:$lastEntries")
    }
    return $back
}

$warmup=WaitForPrinterSystem

Server 2012 has already group policy to add printers to client computers.

After the server reboot unexpectedly, the Print Services log shows messages on shared printers:

Group Policy was unable to add per computer connection \\Server\Printer. Error code 0x5. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.

Some printers have the same message but with Error code 0x709.

How to fix it?

Thanks,

Joe

Hi,

on an Windows Server 2012R2 RDS the spoolsv.exe is crashing randomlay.

Here is a crashdump:

FAULTING_IP:
KERNELBASE!RaiseException+68
00007fff`0b858a5c 488b8c24c0000000 mov     rcx,qword ptr [rsp+0C0h]

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff0b858a5c (KERNELBASE!RaiseException+0x0000000000000068)
   ExceptionCode: c0000002
  ExceptionFlags: 00000001
NumberParameters: 0

DEFAULT_BUCKET_ID:  STATUS_NOT_IMPLEMENTED

PROCESS_NAME:  spoolsv.exe

ERROR_CODE: (NTSTATUS) 0xc0000002 - {Nicht implementiert}  Der Vorgang ist nicht implementiert.

EXCEPTION_CODE: (NTSTATUS) 0xc0000002 - {Nicht implementiert}  Der Vorgang ist nicht implementiert.

EXCEPTION_CODE_STR:  c0000002

WATSON_BKT_PROCSTAMP:  54503ab3

WATSON_BKT_PROCVER:  6.3.9600.17415

PROCESS_VER_PRODUCT:  Microsoft® Windows® Operating System

WATSON_BKT_MODULE:  KERNELBASE.dll

WATSON_BKT_MODSTAMP:  57366075

WATSON_BKT_MODOFFSET:  8a5c

WATSON_BKT_MODVER:  6.3.9600.18340

MODULE_VER_PRODUCT:  Microsoft® Windows® Operating System

BUILD_VERSION_STRING:  6.3.9600.17415 (winblue_r4.141028-1500)

MODLIST_WITH_TSCHKSUM_HASH:  0c04458e9b82b37bf1472dfed3614a132c51736b

MODLIST_SHA1_HASH:  6b54b7e88e6922f58844e8953c82585173197b90

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

DUMP_FLAGS:  94

DUMP_TYPE:  1

ANALYSIS_SESSION_HOST:  T13800

ANALYSIS_SESSION_TIME:  01-27-2017 17:27:36.0288

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

THREAD_ATTRIBUTES:
OS_LOCALE:  DEU

PROBLEM_CLASSES:

    Tid    [0x0]
    Frame  [0x00]
    String [STATUS_NOT_IMPLEMENTED]
    Data Bucketing

BUGCHECK_STR:  STATUS_NOT_IMPLEMENTED

LAST_CONTROL_TRANSFER:  from 00007ffeebb4877f to 00007fff0b858a5c

STACK_TEXT: 
000000ff`410cde70 00007ffe`ebb4877f : 000000ff`41753a98 00007ffe`ebb2d214 000000ff`410ce060 00000000`00000000 : KERNELBASE!RaiseException+0x68
000000ff`410cdf50 00007ffe`ebb4811f : 000000ff`419ceed0 00000000`00000000 00000000`00000000 000000ff`40766fc0 : win32spl!NCSRCommon::VariantGetEncapsulatedType<NCSRCommon::TIniSpooler>+0x73
000000ff`410cdf90 00007ffe`ebbb2f99 : 000000ff`41a344b0 000000ff`41a344b0 00000000`00000000 00000000`00000000 : win32spl!NCSRCommon::GetAttribute<NCSRCommon::TIniSpooler * __ptr64>+0x67
000000ff`410ce010 00007ffe`ebb7c5e9 : 00000000`80070057 000000ff`417f0110 000000ff`410ce160 00000000`00000000 : win32spl!NCSRMonitor::TPortMonitor::NewIniSpooler+0xc9
000000ff`410ce0e0 00007ffe`ebb7cb50 : 000000ff`41838388 000000ff`41891970 00000000`00000002 00007ffe`f1c65760 : win32spl!NCSRMonitor::TPortMonitorTable::InitializePortMonitorTable+0xa1
000000ff`410ce150 00007ffe`f1c56b0a : 000000ff`417f0100 000000ff`41891970 00000000`00000000 000000ff`41891970 : win32spl!InitializePrintMonitor2+0x30
000000ff`410ce180 00007ffe`f1c57c78 : 00000000`000011cc 00000000`00000000 00000000`0000001a 00000000`00000000 : localspl!CreateMonitorEntry+0x29f
000000ff`410ce670 00007ffe`f1c57a27 : 000000ff`00000000 00000000`00000001 000000ff`410cf000 000000ff`41891970 : localspl!BuildAllPorts+0x150
000000ff`410ceb20 00007ffe`ebb86092 : 00000000`00000001 00007ffe`ebbe0efc 00000000`00000001 00000000`00000000 : localspl!SplCreateSpooler+0x577
000000ff`410cefe0 00007ffe`ebb4c5e3 : 00000000`00000001 00000000`00000001 000000ff`40767920 000000ff`406fdd08 : win32spl!NCSRCommon::TIniSpooler::CreateSpooler+0x1e2
000000ff`410cf120 00007ffe`ebb4e4a6 : 00000000`00000000 000000ff`4078aba0 000000ff`406fdd08 000000ff`40767420 : win32spl!TPrintOpen::FillInCacheAtAPC+0x9f
000000ff`410cf160 00007ffe`ebb4ec10 : 00000000`00000000 00000000`00000000 000000ff`419bc300 000000ff`41a18e20 : win32spl!TPrintOpen::ReEstablishCacheConnection+0xe2
000000ff`410cf1f0 00007ffe`ebb4e950 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : win32spl!TPrintOpen::ReEstablishPrinterConnection+0x20c
000000ff`410cf2c0 00007ffe`ebb3c194 : 00000000`00000036 00007ffe`ebb25c30 00000000`00000000 00007ffe`00000000 : win32spl!TPrintOpen::ReEstablishConnectionFromKey+0x1b0
000000ff`410cf3c0 00007ffe`ebb21286 : 000000ff`00000000 00000000`00000000 000000ff`406fdcf0 00000000`00000000 : win32spl!TPrintOpen::RediscoverPrinterConnections+0x19244
000000ff`410cf4e0 00007ff6`b4b1fccd : 00000000`00000088 00000000`00000000 00007ffe`f1c192b0 00000000`00000088 : win32spl!TPrintProviderTable::forwardEnumPrinters+0x50e
000000ff`410cf6b0 00007ff6`b4b20b1c : 00000000`00000006 00000000`00000000 000000ff`00000002 000000ff`41868b00 : spoolsv!EnumPrintersW+0xed
000000ff`410cf750 00007ff6`b4b209ca : 000000ff`00000006 00000000`00000000 00000000`00000002 000000ff`4070d5f0 : spoolsv!YEnumPrinters+0xec
000000ff`410cf7d0 00007ff6`b4b20336 : 000000ff`00000000 00007fff`00000002 00007fff`00000006 00000000`00000000 : spoolsv!TFunction8<unsigned long,unsigned short * __ptr64,unsigned long,unsigned char * __ptr64,unsigned long,unsigned long * __ptr64,unsigned long * __ptr64,enum Call_Route>::Run+0xca
000000ff`410cf860 00007fff`0e30678e : 00007ff6`b4b202d0 000000ff`416ffcc0 000000ff`410cfa48 000000ff`416ffd70 : spoolsv!NThreadingLibrary::TWorkCrew::tpSimpleCallback+0x62
000000ff`410cf890 00007fff`0e328e2d : 000000ff`416ffd70 000000ff`42021650 00000000`00000000 000000ff`4019a208 : ntdll!TppSimplepExecuteCallback+0x7e
000000ff`410cf8d0 00007fff`0e1b13d2 : 00000000`00000000 00007fff`0e3289b0 000000ff`401a4b20 00000000`00000000 : ntdll!TppWorkerThread+0x47d
000000ff`410cfcb0 00007fff`0e3054e4 : 00007fff`0e1b13b0 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x22
000000ff`410cfce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34

THREAD_SHA1_HASH_MOD_FUNC:  3ffb06851e5d1577bb7a832702456151524547ee

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  4f17eb346ee9b4fe0522ddaed0fb8c9903f83d69

THREAD_SHA1_HASH_MOD:  682b6604ce70a3e2d769d192b70f848f40b90dd5

FOLLOWUP_IP:
win32spl!NCSRCommon::VariantGetEncapsulatedType<NCSRCommon::TIniSpooler>+73
00007ffe`ebb4877f 8bf8            mov     edi,eax

FAULT_INSTR_CODE:  c085f88b

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  win32spl!NCSRCommon::VariantGetEncapsulatedType<NCSRCommon::TIniSpooler>+73

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32spl

IMAGE_NAME:  win32spl.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  57d2c162

STACK_COMMAND:  .ecxr ; kb

BUCKET_ID:  STATUS_NOT_IMPLEMENTED_win32spl!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_+73

PRIMARY_PROBLEM_CLASS:  STATUS_NOT_IMPLEMENTED_win32spl!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_+73

FAILURE_EXCEPTION_CODE:  c0000002

FAILURE_IMAGE_NAME:  win32spl.dll

BUCKET_ID_IMAGE_STR:  win32spl.dll

FAILURE_MODULE_NAME:  win32spl

BUCKET_ID_MODULE_STR:  win32spl

FAILURE_FUNCTION_NAME:  NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

BUCKET_ID_FUNCTION_STR:  NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

BUCKET_ID_OFFSET:  73

BUCKET_ID_MODTIMEDATESTAMP:  57d2c162

BUCKET_ID_MODCHECKSUM:  dd346

BUCKET_ID_MODVER_STR:  6.3.9600.18470

BUCKET_ID_PREFIX_STR:  STATUS_NOT_IMPLEMENTED_

FAILURE_PROBLEM_CLASS:  STATUS_NOT_IMPLEMENTED

FAILURE_SYMBOL_NAME:  win32spl.dll!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

FAILURE_BUCKET_ID:  STATUS_NOT_IMPLEMENTED_c0000002_win32spl.dll!NCSRCommon::VariantGetEncapsulatedType_NCSRCommon::TIniSpooler_

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/spoolsv.exe/6.3.9600.17415/54503ab3/KERNELBASE.dll/6.3.9600.18340/57366075/c0000002/00008a5c.htm?Retriage=1

TARGET_TIME:  2017-01-27T12:03:46.000Z

OSBUILD:  9600

OSSERVICEPACK:  17415

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  16

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 Server TerminalServer

USER_LCID:  0

OSBUILD_TIMESTAMP:  2014-10-29 03:45:30

BUILDDATESTAMP_STR:  141028-1500

BUILDLAB_STR:  winblue_r4

BUILDOSVER_STR:  6.3.9600.17415

ANALYSIS_SESSION_ELAPSED_TIME: 2a1d

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:status_not_implemented_c0000002_win32spl.dll!ncsrcommon::variantgetencapsulatedtype_ncsrcommon::tinispooler_

FAILURE_ID_HASH:  {95d9f5a4-50c1-9c0e-7448-501172d643fa}

Followup:     MachineOwner

I do not know, how to debug this forther. It seems, that is it not a Driver related Problem. Anyonce can help ?

WinServer2012R2 - Print server role - LPD service active

I can apply changes to the configured printport tcp/ip settings (default 515) to 516 (regedit or script).

I can open the port after changes have been applied but after 10-15 seconds this Raw Setting Port Number is reset to 515.

This behavior is not consitent because on some printports the changes are kept in the system.

What do I overlook?



After installing Windows 10, I found another something that doesn't work. It's my HP Desktop 3050A J611g All in One Printer.  I am getting an error message 0x0000007e

Can someone please help me with this one?

Thanks!

Manuel Robles

Hello!

I got a really delicate problem that I'm unable to figure out. And I would like some input from Reddit before I take the big step of opening a case at Microsoft.

I'm working as a consultant in the SMB-segment of IT. With that I have daily fights with regular PCs, virtual enviorments, networking and of course: Printers.

A couple of months ago we deployed a new printserver (Windows Server 2012), dedicated to a printing software for labels (Nicelabel). This printserver takes care of about 30 labelprinters, all from the same brand (Datamax-O'Neil MP Nova4). In the beginning of the deployment everything went stunning! Printing a label would'nt take less than 2-3 seconds and everybody was happy!

But since a couple of weeks back, we've seen horrible performance of the printing. Printing a label takes 10 seconds now days (exactly 10 seconds) on all the printers on that server. The label that's about to get printed (weather it's generated from the printing software, or simply a test page in Windows) gets stuck in the Printspool, and let's go after 10 seconds.

I've tried to disable bidirectional support, disabled "Advanced Printing Features" and changing the VLAN (so the printserver is on the same VLAN as the printers). Still the same problem. We are using the recommended driver from DATAMAX themself (according to them, there is no problem with the driver at all).

The printers has been deployed on the server with two simple Powershell-commands (see below):

add-printerport -name "$portname" -printerhostaddress "$portip"​
add-printer -name "$printername" -drivername "$driver" -port "$portname".

If I add another printer, let's say a HP 2055dn with Universal Print Driver, the printing process is working like a charm.

So, printer gurus at TechNet. What would you do?

Best regards, sad-consultant-who-deals-with-printers