Network Print Driver Configuration via Centralized Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large enterprises face difficulties in changing enterprise-wide print driver defaults across networked printers, particularly in non-point and print-based servers like Novell NDPS and Microsoft IPP, due to limitations in modifying certified driver configurations and the need for time-consuming manual processes to update printer queues.
Innovation Solution
A system and method for configuring client print queues through central storage of driver configuration files that can be updated by administrators, allowing client devices to access and apply enterprise-wide settings post-installation, ensuring that print drivers maintain WHQL certification while enabling dynamic reconfiguration of printing defaults.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a custom configuration file is used to change print driver defaults, then the ability to modify printing defaults is improved, but the WHQL certification is invalidated and driver installation is prevented
Solution Approach 1:
The patent extracts the configuration file from the WHQL certified driver package. The driver package maintains its digital signature and certification, while the configuration file is separated and stored externally. This allows the driver to remain WHQL certified while the configuration can be customized without invalidating the certification.
Solution Approach 2:
The patent introduces an intermediary configuration file that acts as a bridge between the WHQL certified driver and custom printing defaults. The configuration file is read by the driver at runtime, allowing customization without modifying the certified driver package itself.
2Adaptability or versatility
If print driver defaults are changed in non-point and print-based servers, then the ability to update printing defaults is improved, but the process requires deletion and reinstallation of print queues which increases time consumption
Solution Approach 1:
The patent performs preliminary action by storing the configuration file with the driver package during installation. The configuration file is placed in a known location and registered with the driver, so that future updates can be applied by simply replacing the configuration file without reinstallation.
Solution Approach 2:
The patent makes the configuration dynamic by allowing the configuration file to be updated independently of the driver installation. The driver reads the configuration file at runtime, enabling dynamic updates to printing defaults without requiring deletion and reinstallation of print queues.
3Adaptability or versatility
If manual cleanup tools are deployed to change enterprise-wide print driver defaults, then the ability to enforce corporate policy is improved, but the deployment complexity and operation time increase significantly
Solution Approach 1:
The patent creates a universal solution where a single configuration file format can be used across different print drivers and printer types. The configuration file structure and update mechanism work universally across the enterprise, eliminating the need for multiple specialized cleanup tools for different scenarios.
Solution Approach 2:
The patent enables self-service by allowing the system to automatically detect and apply configuration updates. When a configuration file is updated, the system automatically reads and applies the new defaults without requiring manual intervention or complex deployment procedures.
Data Source
AI summary
What is disclosed is a novel system and method for configuring a client print queue in a networked printing environment. In one embodiment, a client print queue corresponding to a server print queue is initialized on a client device. The server print queue is configured with a default location of a configuration file that contains at least one print queue configuration parameter. In response to a command at the client device to utilize the client print queue, the client device receives the default location of the configuration file and retrieves at least one print queue configuration parameter from the configuration file. The client print queue is then configured, also in response to the command at the client device to utilize the client print queue, according to the retrieved at least one print queue configuration parameter.


