I'm replacing a Windows Server 2016 print server with Server 2025. I migrated the queues with the print migration tool, but queues using the Canon iPR Svr M20 PS V1.0 US driver, version 6.5.0, prompt users for UAC approval to install the driver when mapped through Group Policy. The same driver is already deployed to Windows 11 24H2 clients through SCCM, and the queues work normally when mapped from the Server 2016 system. We also use uniFLOW so users must release jobs at the physical printer.
If I change the queue to Canon's generic driver, the mapping completes without a prompt. I've reproduced the behavior on multiple Server 2025 test systems and compared the driver files on the server and clients without finding an obvious difference. What Server 2025, Point and Print, or driver-signing policy could be causing it to believe this Type 3 Fiery driver needs to be installed again?
3 Answers
Fiery drivers can be particularly troublesome during migrations. Try installing the exact driver package directly on the Server 2025 print server while logged on with administrative rights, rather than relying only on the migrated queue. Make sure the server and clients are using the same package version and architecture. The generic Canon driver working is a good indication that the issue is specific to the Fiery package or its trust metadata.
A Type 4 driver can avoid some of the older Point and Print installation behavior, but it may not support the same finishing and Fiery features. Since Canon has confirmed that a Type 4 version is unavailable for this device, the practical route is to keep the Type 3 driver and correct the approved-server and driver-installation policies instead.
Check the Point and Print security policies introduced as mitigations for PrintNightmare. The older server may be listed as a trusted print or driver source, while the new Server 2025 host is not. Review the Point and Print Restrictions settings and any related package-point-and-print or approved-server policies, then add the new print server as a trusted source if that matches your security requirements.
That pointed me in the right direction. After adjusting a couple of the policies, the queues can map without the prompt, although one queue that worked before still needs separate troubleshooting.
Unfortunately it is a Type 3 driver, and Canon has told us there isn’t a Type 4 replacement for this model.