Deploying Packaged Print Drivers

From Wiki.CoreyBlair.US
Revision as of 14:05, 14 September 2018 by Corey (talk | contribs) (Created page with "Deploying print drivers that are not package aware can be troublesome and an I.T. nightmare in the enterprise. In order to work around this issue, an administrator of the prin...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Deploying print drivers that are not package aware can be troublesome and an I.T. nightmare in the enterprise. In order to work around this issue, an administrator of the print server can make some easy modifications to the registry of the print server.

  • Inside of the registry, edit the "PrinterDriverAttributes" key in the following for 64bit drivers. Change the attribute to an odd integer

HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\...\Driver name\[1]

  • Next, edit the "PrinterDriverAttributes" key in the following for 32bit drivers. Change the attribute to an odd integer

HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx86\Drivers\...\Driver name\[1]

Now reboot the print server since registry values require it. Once back up, check in the Print management mmc to see if the driver is showing "true" to being packaged.

References

  1. 1.0 1.1 grei_70, Cannon Forums, August 17, 2016