What are you guys doing now to deploy printers?

[AB_IT]

Hi All,

 

So I've gotten a bit lost on the big printer deployment thread. I created a Group Policy to create the Registry Key needed to get around the issue but it hasn't seemed to fix it. Basically Group Policy or going to the print share manually can no longer deploy printers.

 

We just get the following message. I've ran a gpresult but it comes back as okay and is running the printer deployment group policy but the printers don't show up for the user.

 

I know PaperCut has that PrintDeploy software so wasn't sure if this was an option but I've just never used it before.

 

Any help would be most appreciated as since we reimaged the computers around site they now can't access the printers at all.

 

[FN-GM]

The registry key opens up the vulnerability so I would be cautious.

 

I believe if you pre deploy the drivers to the machine using SCCM or something and map the printer it should be fine.

[rogerdnixon]

Papercut print deploy at all of our sites. Works well.

[AB_IT]

Papercut print deploy at all of our sites. Works well.

Wow, that's the future! I just had a play around with it and it's running like a dream. An easy MSI to deploy also, fab!

[mavhc]

Powershell script to add the drivers and then create printers to go directly to the printer IP, no more print servers

[EssentialRug]

Papercut print deploy at all of our sites. Works well.

 

Same here...works perfectly for us and we're really happy with it. Deploys fantastically through Endpoint Manager too.

[FN-GM]

Powershell script to add the drivers and then create printers to go directly to the printer IP, no more print servers

 

I was wondering if you could share the script please?

[AB_IT]

Hey Everyone. So setup Print Deploy yesterday. Seemed to go well and added our IP ranges that it should work with. I've basically got it set on 'Everyone' Zone to add both Virtual follow me print queue's called Papercut-Colour and Papercut-Mono.

 

Just tried installing the client on a domain connected computer. It's added both printers to the computer... Great. It also shows the user as signed in automatically at the bottom left of the software. We can also look on the server side it shows up the jobs in the PaperCut print log under that username but when the user logs in to the porinter itself the job isn't waiting for them to release from the queue?

 

Have I done something wrong?

[mavhc]

I was wondering if you could share the script please?

 

It's a bit of a mess, but https://github.com/mavhc/powershell InstallPrintersIPSite.ps1

 

Install drivers in a startup script, run this script as a user, gets their current site, adds printer ports, drivers, and then creates a printer. If it's a v4 printer you can set options.

 

Only slight problem is the first user to add that printer has more privs, but we're mostly 1:1

 

Sadly Kyocera printer drivers really don't like IPP, so couldn't use that

[AB_IT]

I've also realised, under 'devices' on PaperCut it shows two new devices under the computers domain name which is very weird also...

 

[AB_IT]

So I just setup a VM as per the instructions on this video. Added the two PaperCut virtual queues from our print server and then ran the cloner tool. Added those printers into the zone from the VM and went to a client PC to test and now I get the same damn annoying print error I did when I was installing them conventionally.

 

[PaperCutterAl]

So I just setup a VM as per the instructions on this video. Added the two PaperCut virtual queues from our print server and then ran the cloner tool. Added those printers into the zone from the VM and went to a client PC to test and now I get the same damn annoying print error I did when I was installing them conventionally.

 

[ATTACH=CONFIG]66964[/ATTACH]

PaperCutter here. Clearly I'm super late to this thread. Are you still having problems?