Printer drivers install every time we print?

Source Print  
Type Warning  
Description Printer Driver <printer model> for Windows NT x86 Version-2 was added or updated. Files:- <list of driver files>.  
Comments Adrian Grigorof
Normally, this event is generated when a new printer is installed on a system. However, in many instances, it has been reported that this event keeps occuring without any change to the printing hardware or software. Here are some explanations:

From a newsgroup post: "This event is also generated when a computer without the required drivers connects to the print server and downloads the printer driver to their workstation. You could test this by removing the printer and its drivers from one of your workstations and then re-adding the printer. This should cause the driver files to be downloaded again, and should generate this event."

From another newsgroup post: "This may occur when you have printers from different NT print servers that have different versions of drivers for the same printer model. Either standardize driver versions on all servers or stop using conflicting printers on the same PC. E.g. \\SERVR1\HPLJ4-12 is HP driver version 3.0.7 and \\SERVR2\HPLJ4-33 is MS driver v X.X...or HP v. 2.00... Everytime you open a printer on your NT PC it checks and updates the driver versions from server, but it couldn't have different versions installed for the same model (HP LaserJet 4 in example)."

From another newsgroup post: "Here is my solution for the repeated event id 20:
1. Go to the actual print server, open the print dialog box, click Server properties, click the driver tab and remove all of the unused drivers (note: if you don't know which ones to delete just go through and delete them all, windows prompts you when the driver is in use and cannot be deleted).
2. After you cleaned up the server side of useless driver info go the the client. Delete the logical printers first on the client, then go into printer dialog box and go into the server properties driver tab and remove the unused drivers as indicated in the previous text,
3. Reboot the client, install the printers, that should be all you need.
4. After you install the printers you will see one entry in the event viewer at the time you installed the printer but you should see that only once."

Michael P. Piron
There are two Microsoft Knowledge Base Q articles that also offer two explanations for this error message displaying in the Event Logs. I have seen several instances of this when using SNA print devices, information on SNA causes of this message are detailed in the second Q article (Q229046)

Microsoft Q234330: These events are logged when a Terminal Services client with a local printer attached connects to a server. The server loads the drivers for the client''s local printer to enable the client to print to its local printer from within the client session. Note: Microsoft''s explanation sounds somewhat similar to Event ID 1105 for source: TermServDevice

Microsoft Q229046: If the drivers for a remote printer are not installed on the SNA Server computer, the Windows NT spooler service will copy the drivers locally in order to print.

If the drivers for the remote printer ARE installed on the SNA Server computer, the spooler service still checks the remote printer server for updated drivers. If the drivers are newer than the ones installed on SNA Server, then the newer ones are temporarily copied locally to print the job.

Note: These events can occur for every print job that is sent through an SNA Server print session. The message does not cause any problems with printing, and can be considered an informational message.