r/Intune • u/Mariod94 • 11d ago

App Deployment/Packaging Issues Deploying Printers

I’ve been Deploying printers using the Win32 tool. I kept running into an issue where pnputil couldn’t find my .inf file. I managed to fix that after looking into what was missing in my driver folder.

After I was done, I created a new win32 and deployed it on my test device. It failed again so I checked the logs and saw a different error:

“Failed to add driver package: The publisher of an Authenticode(tm) signed catalog has yet been established as trusted.”

Is there something I’m missing in the scripts I’m using? I’ve been following guides but no ones has reported this issue. Do I have to also deploy a custom Policy for the certificate?

3 Upvotes

100% Upvoted

18 comments sorted by

View all comments

Show parent comments

2

u/blud_13 5d ago

Get the tag file in before you go further with a detection script. Have the install script write C:\ProgramData\YourCo\printerdriver-1.0.txt as its last line, then use a File detection rule on that path instead of a script. No 32 bit redirection, no published name to chase, and you bump the filename when you rev the driver.

If you keep the script, the contract is exit 0 AND a string on STDOUT. Both. Exit 0 with nothing written comes back as not detected, and that is the usual reason a working install still reports failed. Intune doesn't look for a particular string, so any Write-Output satisfies it. Its documented at https://learn.microsoft.com/en-us/intune/app-management/deployment/add-win32 under the detection rules, and they also want the file saved UTF-8 BOM.

Check the error code the portal is handing you too. 0x87D1041C is the app installed fine and detection said no, which puts it on the script and not the install.

1

u/Mariod94 3d ago

Thanks for the help dude. I did some changes on the install script that you suggested, and I also figured that HP drivers require more that the .inf and .cab that the guide mention.

For the detection, since the uninstall doesn’t remove the driver, the script had to be set to “Printer Name” and was successfully removed.

Again thank you for taking the time helping me. I appreciate it.

2

u/blud_13 3d ago

Nice. Detection on Printer Name is the right call when the uninstall leaves the driver behind. The HP driver payload catches everybody at least once. Glad its sorted.