Printer share keeps turning off! anyideas?

[PaperCutterAl]

Hey now, PaperCutter here (without technical knowledge but good at finding brainy people). We're diving deep into this one at the moment. I suggest if you're battling with this that you create a support request (if you haven't already) with our tech team so that you're kept up-to-date with progress. I'll endeavor to come back and share the resolution for the forum's posterity when it comes. Click on CONTACT SUPPORT here: https://www.papercut.com/contact/

 

EDIT: I just re-read this and thought I'd add some more info. We're investigating this to see if this is related to Print Deploy or whether it's a Windows behaviour affected configuration. TBH it might not have anything to do with PaperCut. But we're looking (And when I say WE I mean the brainies).

Edited February 14, 2024 by PaperCutterAl

[Paulwads]

Hi - we noticed this started to happen shortly after we updated Papercut, not sure if this is relevant. Keeps happening with the same Domain Admin account each time it happens - looking in the logs. W ehave now disabled this specific account and I shall report back if it happens again.

[stevenlong1985]

Hi - we noticed this started to happen shortly after we updated Papercut, not sure if this is relevant. Keeps happening with the same Domain Admin account each time it happens - looking in the logs. W ehave now disabled this specific account and I shall report back if it happens again.

 

Hey what version of papercut are you running?

[Paulwads]

Hi - We are using: PaperCut MF - Version: 23.0.5 (Build 68385) - Built on: Jan 17, 2024

[Squelch]

It's just happened to us (again). I updated to PaperCut 23.0.7 on the 14th. I've been doing printery things this morning specifically with print deploy and then the virtual queue unshared itself.

[JSpaced]

We identified the offending account (our utility systemadmin) and amended the security on the printers to DENY that account permission to change the printer settings. This seems to have fixed it.

[Squelch]

I opened a ticket with PaperCut who pointed me to the known issues article here: https://www.papercut.com/support/known-issues/?id=PD-1911#mf

[Netwacky87]

I'm so pleased we could get to the bottom of this with some acknowledgement! Bravo All!

[psynegy]

One of our admins just logged into an MDM device that uses Print Deploy, and once again our printer shares have become unshared! So annoying!

 

Has there been any progress on finding the cause of this?

[Squelch]

I followed the good advice of others in this thread to determine which account was unsharing the printer and then denied print management to that account. I haven't heard anything from PaperCut about the issue.

[psynegy]

Can't deny print management without also denying print sadly... I suppose I could just remove permission from the group rather than explicitly deny... Sigh.

[willemgroenewald]

Willem here, product manager at PaperCut looking after Print Deploy.

 

The latest Print Deploy release fixed an issue that could cause print server queues to get unshared. Still, we want to confirm with customers who reported the issue that it addressed their issue and that there isn't potentially another cause that we haven't fixed. Let me know if this release fixes this issue for you.

 

To test, deploy print server queues to a user running Windows Print Deploy client version 1781 and who has manage printer privileges on the server.

 

This known issue includes some tips on getting the latest client: https://papercut.com/support/known-issues/?id=PD-1911#mf

[kidtrebor]

I have noticed that the print deploy clone tool doesn't recognise a printer queue using a type 4 driver.

 

At my organisation we are keen to move away from using type 3 drivers due to the legacy of Print Nightmare and are reticent to give users admin rights, much less disable the fix Microsoft put in place 3 years ago.

 

Has anyone been able to work around this limitation and deploy type 4 Papercut follow-me queues?

 

Are there plans to address the issue with the cloner queue directly by Papercut?

 

Many thanks indeed.

 

Regards,

Robert

[willemgroenewald]

The real fix for Print Nightmare is Windows Protected Print mode (https://www.papercut.com/discover/the-complete-guide-to-windows-protected-print-wpp/), which was released last week. Windows protected print mode removes support for manufacturer drivers all together, and instead uses IPP. You can sign-up for early access for our first release that supports Windows protected print mode here: https://www.papercut.com/products/percolator/windows-protected-print-for-papercut-mf-ng/

 

With Print Deploy, users don't need admin rights to install print queues. If you only require basic finishing options, you can deploy Mobility Print queues with Print Deploy using this quick guide: https://www.papercut.com/help/manuals/print-deploy/set-up/import-printers/import-mobility-print-queues-quick/. If you need manufacturer drivers to support options like stapling, follow this guide: https://www.papercut.com/help/manuals/print-deploy/set-up/import-printers/import-mobility-print-queues-advanced/