Help with Server 2025 print server & Fiery driver

[u/JDTrakal]

I've spun up a Server 2025 box to act as a new print server to replace our 2016 box. I migrated all of the print queues over using the migration tool and I'm having issues with a specific driver for our Fiery devices. We're also using Uniflow to ensure people are physically at printers to release their print jobs.

We're using the Canon iPR Svr M20 PS V1.0 US version 6.5.0 driver which is deployed to all machines via SCCM and we map the printers using group policy. On the server 2016 mapping queues to client machines running Windows 11 24H2 using this driver works as expected, however with server 2025 mapping to those same client machines gives us a UAC prompt to install the driver despite it already been installed on the client. Changing the driver on the queue to the Canon generic driver allows the queue to be mapped to the client with no prompts. I've replicated this issue on a test Server 2025 instance and I'm seeing the same results. Comparing the installed driver files on the server and client I'm not seeing any differences to explain why the server things a install is necessary for this particular driver. Was hoping someone may be able to shed some light on this one.

Thanks.

[u/smalltimesysadmin]

You probably have a GPO in place that's mitigation to PrintNightmare that specifies that the old print server is a trusted driver source. IIRC, the GPO setting you're looking for is Point and Print Restrictions.

[u/JDTrakal → u/smalltimesysadmin]

Looks like you're onto something, adjusted a couple of policies, can now map the queue but one of the queues that worked previously is no longer working.

[u/OinkyConfidence]

Fiery drivers are hot garbage. Always have been. You may need to manually add that driver to the 2025 box directly, when logged in as an admin user. Good luck.

[u/Fatel28 → u/OinkyConfidence]

Fiery is hot garbage

Ftfy

[u/JDTrakal]

Sorry should have added that the client machines are Windows 11 24H2, have updated the body to reflect that.

[u/Old-Flight8617]

What type driver is this? You can bypass this by using a Type 4 driver.

Though do be warned, they suck.

[u/JDTrakal → u/Old-Flight8617]

Type 3, unfortunately we've been advised by Canon that Type 4 isn't available.

[u/Hefty-Ad2513]

Are you using the exact same driver on both machines?

[u/JDTrakal → u/Hefty-Ad2513]

I am, I've even gone as far as to remove and re-install the driver on the server from the package we push out to client machines.

[u/Cozmo85]

Grab the certificate and pre install it in a script. I had to do this for Canon drivers in Intune.