Intune Printer Deployment Guide

[EssentialRug]

Just checked mine, you need the Value name to be Name

It to looks for the string called Name then the value of what you have set the printer to be called.

[ATTACH=CONFIG]71055[/ATTACH]

 

Cool...so it was definitely me just being a massive idiot. Reading back the instructions it's so obvious I had to put Name in there rather than my printer name. What an idiot. Thank you so much, all working perfectly now.

[Jonesy1276]

Really useful, thanks.

[crazyplace]

In the end I abandoned the deployment via Intune. With the help of our Printer Supplier I ended up installing PaperCut Mobility Print on the Print Server and set the printer up to be accessed through it. Deployed the PaperCut software via Intune (worked a treat and was a doddle with a full guide for it) and published the needed link via Teams so it was always available. Wish I had gone down this route to start, works well and is reliable. Pupils just need to click that link through Teams and it sets the printer up for the and away it goes.

 

Doesn't this method require giving the user admin access? I wanted to do this but then when I tried it, the user needs local admin access on the workstation to be able to setup the printer on the device for the first time. Can anyone comment on this?

 

Thanks

[Reverend_Dan]

Not if you deploy this way with system context at least for canon drivers. I couldn't get this to work with oliveti drivers but I think that was more to do with our outdated drivers for older printers.

[crazyplace]

Not if you deploy this way with system context at least for canon drivers. I couldn't get this to work with oliveti drivers but I think that was more to do with our outdated drivers for older printers.

 

Was this reply to me? I am talking about Papercut mobility print. at first i thought it was my perfect solution but then i realized every user requires having admin access, but since the person i replied to is using it with students, i am guessing there is a way to avoid needing admin rights that I am missing.

[Reverend_Dan]

Was this reply to me? I am talking about Papercut mobility print. at first i thought it was my perfect solution but then i realized every user requires having admin access, but since the person i replied to is using it with students, i am guessing there is a way to avoid needing admin rights that I am missing.

Yes, sorry, and I meant no it doesnt need admin rights.

[crazyplace]

Yes, sorry, and I meant no it doesnt need admin rights.

 

Sorry, i just want to make sure we are clear we are talking about mobility print here, not their paid product? Everything I have found says mobility print is for BYOD and requires admin rights: (1) Print Installation Client needs Admin Rights : Intune (reddit.com)

 

 

If you can share a guide that shows up to setup mobility print without admin rights required I would appreciate it.

[jtsvirinko]

Thank you for posting this, it is very helpful. I'm running into an issue where the printer is not getting installed successfully so the script fails. I'm deploying to Windows 11 devices and I'm attempting to deploy a queue that doesn't have an IP address and uses a canon driver. Here is the error I'm getting when trying to run the script manually on the device:

 

[Reverend_Dan]

Are you runing uniflow secure print by any chance ?

If so you can just upgrade the msi installer in uniflow to use the canon driver and then install that as Windows MSI line-of-business app.

Log on to an administrator uniflow account, go to Extenstions > uniflow smartclient > Installer configuration and creation >Manage installers

click on the verion you want click the edit button change the printer driver and click the update installer button

[ITJAY2023]

The script is telling you that the driver doesnt exist, isnt the correct driver name or it isnt installed

[jtsvirinko]

Thank you for this information. I ended up going about this by creating two Win32 apps and deploying the driver and printer share separately which is working well. Thank you for the information regarding SecurePrint that is helpful, unfortunately we are still using a locally hosted Uniflow server.

[cheekycharly]

I did mine differently in the end and I now deploy it as an Intune package that I can update and uninstall with ease.

[talksr]

Hi All,

A big massive thank you to Ben Whitemore!

After countless hours spent researching how to bypass universal print and deploy out a network printer I found a 100% working solution. The best thing is that it is actually really simple to deploy.

So...

The process is the following, we are going to create a Win32 App which has all of the printer drivers and two powershell scripts, one is a install script and the other is a uninstall script. We do not edit the scripts at all and instead set all of our parameters for printer ip, driver names etc in the install command itself.

1. Create a folder wherever you want to work out of, I chose C:\Temp

2. Download IntuneWinAppUtil.exe and place it in the temp folder

3. Create a new folder in Temp called Printer (C:\Temp\Printer)

4. Create two powershell scripts in the Printer folder by copying and pasting the code below

 

Install-printer.ps1 Uninstall-printer.ps1

5. Download the printer driver for the printer and place all the files in the C:\Temp\Printer folder, the printer driver files will be where the .inf file is

6. Find out what the printer driver name is by opening the .INF file or by installing the printer driver and getting the driver name from the list

7. Open CMD as a Administrator and run the following command

cd C:\Temp\

.\IntuneWinAppUtil.exe

Source Folder: C:\Temp\Printer

Setup File: Install-Printer.ps1

Output Folder: C:\Temp\Printer

Catalog: N

We have now created the Win32 App in C:\Temp\Printer and are now going to deploy the app via Intune

8. Go to Intune Admin Center, Apps, Add a App, Win32App and select the Win32App you just made

9. Enter the Install and Uninstall command and obviously change it to your driver name, ip etc (the bits in bold)

Install Command:

powershell.exe -executionpolicy bypass -file .\Install-Printer.ps1 -PortName "IP_192.168.1.1" -PrinterIP "192.168.1.1" -PrinterName "Printer Colour" -DriverName "TOSHIBA Universal Printer 2" -INFFile "eSf6u.inf"

 

Uninstall Command:

powershell.exe -executionpolicy bypass -file .\Uninstall-Printer.ps1 -PrinterName "Printer Colour"

 

10. Set the requirements to the below:

11. Set the Detection Rule to the following but change the bold text, so at the end of the keypath needs to be the printer name and the value needs to be the printer name.

Rule Type: RegistryKey Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\Printer ColourValue Name: NameDetection Method: String ComparisonOperator: EqualsValue: Printer Colour

12. Set your deployment groups / users

13. Thank this post

14. Have a great day!

 

Hi, thanks, very useful.

I am getting Invalid Detection Rule errors when I deploy to any station.

 

I added Rules format as Manually Configure Detection Rules, path/code:

Key = HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\ICTSuitePrinter

Value Name = NameDetection Method: String ComparisonOperator: EqualsValue:ICTSuitePrinter

 

Detection Method = Value Exists

Associated with a 32-bit app on 64bit clients = No.

 

Where have I gone wrong?

[EssentialRug]

Hi, thanks, very useful.

I am getting Invalid Detection Rule errors when I deploy to any station.

 

I added Rules format as Manually Configure Detection Rules, path/code:

Key = HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\ICTSuitePrinter

Value Name = NameDetection Method: String ComparisonOperator: EqualsValue:ICTSuitePrinter

 

Detection Method = Value Exists

Associated with a 32-bit app on 64bit clients = No.

 

Where have I gone wrong?

 

Can you post a screenshot of your detection rules?

[talksr]

Can you post a screenshot of your detection rules?

 

Sure, no problem...

 

[EssentialRug]

Sure, no problem...

 

[ATTACH=CONFIG]71876[/ATTACH]

 

So you just need to amend it so that it looks like the below.

[talksr]

So you just need to amend it so that it looks like the below.

[ATTACH=CONFIG]71877[/ATTACH]

 

Thank you. I have just updated it. Will wait for it to refresh on the clients and I will let you know if it worked!

[talksr]

Thank you. I have just updated it. Will wait for it to refresh on the clients and I will let you know if it worked!

 

Doesn't seem to be going still.

 

So this is the install command:

powershell.exe -executionpolicy bypass -file .\Install-Printer.ps1 -PortName "IP_10.75.44.160" -PrinterIP "10.75.44.160" -PrinterName "ICTSuitePrinter" -DriverName "Canon Generic Plus PCL6" -INFFile "CNP60MA64.inf

 

It is a Canon copier.

 

The uninstall command is:

powershell.exe -executionpolicy bypass -file .\Uninstall-Printer.ps1 -PrinterName "ICTSuitePrinter"

 

This is how it is configured now:

 

[EssentialRug]

Doesn't seem to be going still.

 

So this is the install command:

powershell.exe -executionpolicy bypass -file .\Install-Printer.ps1 -PortName "IP_10.75.44.160" -PrinterIP "10.75.44.160" -PrinterName "ICTSuitePrinter" -DriverName "Canon Generic Plus PCL6" -INFFile "CNP60MA64.inf

 

It is a Canon copier.

 

The uninstall command is:

powershell.exe -executionpolicy bypass -file .\Uninstall-Printer.ps1 -PrinterName "ICTSuitePrinter"

 

This is how it is configured now:

[ATTACH=CONFIG]71879[/ATTACH]

 

[ATTACH=CONFIG]71880[/ATTACH]

 

Can you remove entirely and create a new one from scratch? I've just copied my install/uninstall commands and input your information in them. Maybe give that a go? Everything in your detection rules looks ok unless I'm missing something glaringly obvious.

 

powershell.exe -executionpolicy bypass -file Install-Printer.ps1 -PortName "IP_10.75.44.160" -PrinterIP "10.75.44.160" -PrinterName "ICTSuitePrinter" -DriverName "Canon Generic Plus PCL6" -INFFile "CNP60MA64.INF"

 

powershell.exe -executionpolicy bypass -file Uninstall-Printer.ps1 -PrinterName "ICTSuitePrinter"

[talksr]

Can you remove entirely and create a new one from scratch? I've just copied my install/uninstall commands and input your information in them. Maybe give that a go? Everything in your detection rules looks ok unless I'm missing something glaringly obvious.

 

powershell.exe -executionpolicy bypass -file Install-Printer.ps1 -PortName "IP_10.75.44.160" -PrinterIP "10.75.44.160" -PrinterName "ICTSuitePrinter" -DriverName "Canon Generic Plus PCL6" -INFFile "CNP60MA64.INF"

 

powershell.exe -executionpolicy bypass -file Uninstall-Printer.ps1 -PrinterName "ICTSuitePrinter"

 

Thanks,

Did it again, this time, it is installing to devices in the deployed group with success but NOT the one I am testing on.

I have a feeling this may be to do with the port number assigned in the client app.

This bit = -PortName "IP_192.168.1.1"

 

I am wondering if where I have manually added the printer before as a local Administrator, that port is already used so it is causing an issue when this client app goes on. Could I re-name the portname to something different such as "IP_192.168.1.1MDM"?

 

EDIT: It has worked. Seems to be a lengthy time delay but it has gone through, I just had to remove and re-do as you advised. Thank you 👍🏻

[nschoeggl]

I'm using the canon driver as well. I'm able to get the printers/ports/driver added. The issue I'm running into with with the related to job accounting. When printing, it's not prompting for the accounting codes. Any ideas on how to get the other extra stuff installed? I have the cab, cat and inf file along with the scripts for installing/uninstalling.

[Esanchez]

This is an excellent guide so please forgive my lack of expertise with Intune. Client wants to have all printers installed via Intune so any new devices added to Intune will have all network printers installed. I understand the Win32 process, but reviewing this guide I am guessing that I would need to create a Win32 app for each printer and corresponding driver versus a single Win32 app deployment that would install all 4 printers?

I am also curious about the order of operations, should I be updating the Install-printer.ps1 with my IP, Printer name and driver file name prior to converting to Intunewin file?

[talksr]

This is an excellent guide so please forgive my lack of expertise with Intune. Client wants to have all printers installed via Intune so any new devices added to Intune will have all network printers installed. I understand the Win32 process, but reviewing this guide I am guessing that I would need to create a Win32 app for each printer and corresponding driver versus a single Win32 app deployment that would install all 4 printers?

I am also curious about the order of operations, should I be updating the Install-printer.ps1 with my IP, Printer name and driver file name prior to converting to Intunewin file?

 

 

That’s literally what I did. Just remember that the install and uninstall commands need attention also as they contain the printer name and respective IP within them. So don’t forget those.

 

Once I had completed all of mine, I assigned to groups so if you were in an upstairs room, I would assign the apps for printers upstairs only and vice versa for downstairs.

Just focus on getting one added first. Check it all works and then repeat the process for each additional one. All of mine were Canon and identical models which made life much easier.

[Esanchez]

In this client's case it is two Savin/Ricoh printers same model and then two HP printers again same model. So at least I am only dealing with 2 drivers, but glad I confirmed I will need to create a Win32 policy per printer. I will read and reread the PS script again to make sure I identify all the spots that need customized input. I just stumbled upon this website today searching for a means to deploy the printers via Intune. I must say I am excited and humbled to find such a resource. Thank you for the quick reply.

[talksr]

In this client's case it is two Savin/Ricoh printers same model and then two HP printers again same model. So at least I am only dealing with 2 drivers, but glad I confirmed I will need to create a Win32 policy per printer. I will read and reread the PS script again to make sure I identify all the spots that need customized input. I just stumbled upon this website today searching for a means to deploy the printers via Intune. I must say I am excited and humbled to find such a resource. Thank you for the quick reply.

 

 

Two isn’t too bad, I pity the organisations with multiple ones though. Thankfully with Canon, they all seem to use the same driver so even if there are differences in model, they take the same driver which is very helpful.

 

With the number of printers you have, it should be nice and easy. I did have a small issue with my script, but when I posted on this thread, someone helped me out and I was up and running in no time.

It is an excellent resource and a perfect example of why Edugeek is such a fantastic forum. Good luck, I hope the deployment goes without a hitch, but if not, just leave a post here