Build a Print Queue Management Application for Managing Workstation Print Queues and Drivers

All screenshots etc in Word Attachment, budget around $2000 - $3000 for phase 1 I have links available to demonstrate how to use the Print Spooler API's to install drivers and queues. Brief Build a print management system to handle the automatic and selective deployment and deletion of print queues to workstations. System The system will comprise of 3 components 1. The client application 2. The web application 3. The Back End system The Client Application The client application is responsible for the installation and deletion of the Print Queues and Drivers on the workstation, it is also responsible for the identification of the workstation to the system to support the automatic installation or deletion of print queues based on IP Address (range), Workstation name , User or User Group etc. The client application should also act as a shortcut to the webpage for easy navigation. I suspect the client application may well need to have a windows service running as Local System to be able to leverage the rights needed to install drivers and printers. The client application will also log all installed printers on the workstation into the database, from this admin will be able to selectively opt for them to be removed. The Web Application The web application allows users to easily navigate available printers so that they can select them for installation or deletion. It should be possible for some print queues to be hidden from this system for example queues that are deployed by administrators which you would not want a user to be able to delete from their workstation, a permissions system will also be useful. The web application should support a tree structure as per the below screenshot and allow easy organization and grouping of printer by location etc. Selecting a printer on the right will give the user the ability to install or delete it from their workstation as appropriate. It would be nice if we could also highlight any printers on the same subnet as the user – this is a nice to have though. Below is a screenshot of how IP Ranges are defined in the evaluated system, they can then be associated to deployment etc: The web application will also support the administration of the system, for example organizing the print queues, setting permissions and also the auto deployment or deletion of these queues to users or workstations, below is a screenshot from a similar system on how I envisage this being performed. The right had side has a tabbed appearance due to our admin rights allowing us to create deployment rules and set permissions etc. The drivers / profiles section is where the default setting for the driver can be managed. In the system I evaluated this was achieved by the system creating a temporary copy of the print queue on the server, allowing the settings of the options which the system would then capture so it could apply it to workstations, I’m assuming most of this was via the registry. Below are screenshot of how the evaluated system managed drivers: Back End System The Back End System will support the auto import of printer queues from printer servers and communication with the client. The import will pick up relevant information from the print servers such as queue names, locations, drivers, IP Address (if relevant) etc. If a queue is removed the system will instruct the client to remove it from any workstations it knows the queue is installed on. The Back End System will also be responsible for instructing the client to install or delete administratively assigned queues. The drivers information is in the above screenshots, below is the Port information the system holds. A nice to have on this would also be an option to remove any printer queues not assigned by the system or selected by a user, with an option to ignore local printers, i.e. remove any queue not added by the system which are not using local printer ports such as connection to other print servers or tcp/ip printers.