[22h2] Printer Deployment (Intermittent Success)

[MYK-IT]

Despite using GPP method of printer deployment, and putting in some additional settings related to PrintNightmare etc. (e.g. specifying FQSN for Point and Print restrictions etc, disabling security prompts etc) the success of an end-user obtaining all their printers is still intermittent. Sometimes they just get the follow-me printer (which is the first within GPP), other times none. A log off/on sometimes has success. But there appears to be no consistency. The printer drivers are installed on the computers.

 

What are the alternative options?

 

Having the GUI for GPP, was (is) useful as have numerous rules configured to determine which printers are connected and which are default etc (based on computer / OU etc). But if spending some time via scripts / PowerShell etc will fix this then so be it!

 

We do have Intune / PaperCut Deploy (although not used it) as alternative options to a login script etc.

 

Many Thanks,

Edited September 13, 2023 by MYK-IT

[Olliedawg]

Have you ran gpresult as the user to see if the printer policies are applying with no errors? Is there possibly some rogue policy somewhere mucking things up? I deploy our printers using GP (we run papercut too)

[MYK-IT]

Frustratingly, we're still suffering from intermittent printer mapping connections. More so, as it is not always the same computer / user affected. As previously mentioned, although deleting local profile and logging in again can resolve - it does not all of time.

 

The other twist, is in relation to the PaperCut client, which is run as a login script (e.g. so as when updated, it runs the latest client version etc.) but sometime users are not prompted (for cost centre, summary) when printing anything; so they are unable to print. This is the client that runs from C:\Cache\ folder.

 

One thing that I have noted, is that PaperCut creates a new sub-folder for each (newer) version, (e.g. incrementally increases etc.) But with v23.0.1 the numbering process has been reset.

 

For example, (for v22.x)

 

C:\Cache\pc-client.exe-109.32.0.6787-F868576

C:\Cache\pc-client.exe-109.33.0.6950-E0288DF

 

But for v23.0.1

 

C:\Cache\pc-client.exe-1.0.0.0-0

 

Probably totally irrelevant, but we use a script that would clear out the older (folder) versions; so currently we cannot use that.

 

 

To summarise, I would appreciate some suggestions to alternative methods of deploying printers (instead of GPP) and if anyone has come across the same issue with PaperCut MF Client not working.

 

Maybe @PaperCutterBrenda could help? I have emailed our Print Managed Provider for assistance too, to see if they have workarounds.

 

Many Thanks,

[ITGURU]

since changing our login script from running the cache version to just pc client we've had zero calls about papercut not loading