Printers randomly not mapping using papercut ports

[chrisjako]

I am after some advice and best practises for mapping printers

 

Currently we use a print server and deploy printers using the right click and deploy to group policy method under print management, this maps the printer at computer GPO configuration level

 

Often it works fine but sometimes it doesn't, usually when a member of staff or student comes to us saying they don't have any printers available a simple reboot can fix the issue

 

When I map the printers via GPP however it seems to work every time - the issue here is that it then does not register via PaperCut, even though I have set the port IP type to a PaperCut port

 

Arena, our PaperCut support company themselves say that this method of GPP is not supported with PaperCut

 

It's getting to be an annoying problem I would like to fix once and for all, we are running windows 10 1709 for client desktops and server 2016 for the print server

[keyboards]

We run our printers via script but then everyone gets the same follow me printer, obviously you can change the scripts per user group/type or location

[thimon]

Ditched our logon script last year and now install via GPP which works fine with PaperCut MF. User Config > Preferences > Control Panel Settings> Printers. Action Replace, enter path of the printer, under Common tab set Item-level targeting to Security Group for relevant users.