I want users to print in black and white by default, while still allowing them to choose color for an individual job. If they choose color, the next print should automatically return to black and white.
The print server is already configured with black-and-white printing defaults, but those settings are only applied when the printer is first mapped. After a user changes their local preference to color, that choice persists and overrides the server defaults. We currently reset the user-specific printer settings by removing registry entries, but the newer unified Windows print dialog appears to bypass that process, and some applications such as Microsoft Edge may manage their own print settings.
The options we are considering are forcing the legacy print dialog or moving our HP printers to the HP Universal Print Driver and managing settings through Group Policy. What approach works best in practice, or is there a better way to enforce black-and-white as the recurring default?
3 Answers
The most reliable approach is usually to publish the same physical printer as two separate queues: one called something like “Printer - Mono” and another called “Printer - Color.” Configure the mono queue to use black-and-white by default, and deploy the appropriate queue through Group Policy. Users then choose the queue when they need color instead of changing a persistent preference that affects future jobs.
I would use the HP Universal Print Driver if it is supported properly in your environment, but I would still favor separate Mono and Color queues rather than trying to reset user preferences. Configure each queue’s printing defaults, restrict printer-management permissions, and deploy them with Group Policy. Only administrators should be able to change queue-wide defaults, since changes made by someone with printer administration rights can affect everyone using that queue.
Server-side printing defaults are only defaults, not enforced values. A user’s profile can store its own printer preferences and override them later, so changing the Advanced or Printing Defaults settings alone will not guarantee that every future job returns to black and white. A universal driver and Group Policy may provide more consistent management, but applications can still behave differently with the modern print interface.
That matches our testing. The server settings apply initially, but once a user changes the option locally, it persists in the user profile and takes precedence.
We solved the same problem this way. Users were constantly leaving their printer set to color, and separate mono and color queues made the choice explicit.