Intune Printer Deployment Guide

[UpsideDownAndHappy]

Evening,  is anyone able to help me please? 

 

I've been using the excellent script that was provided on the earlier posts, I created the printer-install.ps1, packaged it into InTune along with the inf and catalog files (please see screen shot) 

 

But - when I deploy it through InTune, it doesn't work, I get the dreaded message to say that it doesn't find the registry key for the detection at the end.

 

I have done some trial and error testing, and if I run the Ricoh supplied EXE manually - which then installs the driver - the script works and creates the port, and the printer.  We have an identical Ricoh at another site, so I created another InTune deployment pointing to the different IP, and it worked perfectly.

 

I can use the script if the driver has already been installed - I cant get the script to work if its a blank canvas.  Does anyone know what I'm doing wrong?

[talksr]

10 minutes ago, UpsideDownAndHappy said:

Evening,  is anyone able to help me please? 

 

I've been using the excellent script that was provided on the earlier posts, I created the printer-install.ps1, packaged it into InTune along with the inf and catalog files (please see screen shot) 

 

But - when I deploy it through InTune, it doesn't work, I get the dreaded message to say that it doesn't find the registry key for the detection at the end.

 

I have done some trial and error testing, and if I run the Ricoh supplied EXE manually - which then installs the driver - the script works and creates the port, and the printer.  We have an identical Ricoh at another site, so I created another InTune deployment pointing to the different IP, and it worked perfectly.

 

I can use the script if the driver has already been installed - I cant get the script to work if its a blank canvas.  Does anyone know what I'm doing wrong?

Hmm it's been a long day so forgive me if I am not understanding this but on the basis it is working on Intune for another site, same model, your .intunewin is working, so all I can think is for the problem site, do the devices in question already have that IP as a prexisting port for a printer? I am referring to the bit where if you added it manually, it would be Device Type: TCP/IP, Hardware IP Address: xxx.xxx.xxx.xxx, Port Name: Whatever you call it. 

Is it that the IP and Port Name combo has already been used? 

 

[UpsideDownAndHappy]

4 minutes ago, talksr said:

Hmm it's been a long day so forgive me if I am not understanding this but on the basis it is working on Intune for another site, same model, your .intunewin is working, so all I can think is for the problem site, do the devices in question already have that IP as a prexisting port for a printer? I am referring to the bit where if you added it manually, it would be Device Type: TCP/IP, Hardware IP Address: xxx.xxx.xxx.xxx, Port Name: Whatever you call it. 

Is it that the IP and Port Name combo has already been used?

 

 

Evening

 

apologies, I didn't phrase that right.  I have two different versions of the script, for 2 different sites, and they both work, but only if the driver has been installed previously.  Neither of them work if the PC's are a blank canvas and haven't had the driver installed previously.  

 

During the testing I found that I didn't necessarily have to create an identical port, or printer name - I crashed the Ricoh EXE out before we got to the config part, so it just installed the driver.  Once that's installed  manually I can use my InTune scripts to create the printers pointing to any old port I like.

 

Seems like the script isn't deploying the actual drivers as part of its process?

4 minutes ago, talksr said: