Guest Aaron Posted April 10, 2008 Posted April 10, 2008 Can someone either explain or point me to some documentation on how an XP client interacts with a Server 2003 print server in so far as drivers go? We're having some strange errors with a simple script that runs at logon and adds a default printer to the XP client. We recently built a new print server and modified the scripts to point to the new server. The new server has updated printer drivers and from what we can tell, if the client attempts to download the new driver, the script errors out. Our suspicion is that this is because the user doesn't have permission to update the printer drivers (which we know to be the case). If we log on as an administrator and get the drivers to update, it seems (so far) that the problem goes away. The baffling part is that the clients don't always try to update the driver. Sometimes we have to log in as an administrator 3 or 4 times before it finally goes out and grabs the new driver from the server. So my question is, I suppose, what triggers the client to try and update the driver it has with the updated one on the server?
Recommended Posts