I've tried stopping the spooler service which didn't help as you can't use the printer management interface with that service stopped and also restarting the server after hours and trying it with no one connected. Thanks in advance for your help. And if that doesn't work, try changing the owner of the printer to Administrator under Properties , resetting the permissions, and then deleting once again. Again, its a hack workaround and Print Management is a much better tool for the job. That often purges the deleted printers and solves some basic issues with redirected printers not working. This script gets executed every day on our virtual Citrix terminal servers, this way we can update drivers independently of the current released image.
Print spooler crashing is one of life's more frustrating events because it's so difficult to pinpoint the actual cause. Then add the win 7 x86 drivers using the method described by Andy T and figers crossed this will work. Is the only option to delete those 20+ printers out, remove the driver package, add the new driver package back and then recreate the 20+ printers? Our terminal servers are all running Server 2008. Rogue print drivers: Some print drivers can cause memory corruption or are simply incompatible with different devices in your environment. Interesting, I found the logon times were reduced when I went to the preferences method as it's a much more natural way for them to be handed out.
This can be solved by logging in as an administrator going into print management and deleting the print drivers. I believe it must be a fault with a 64bit Server not being able to deal with x86 print drivers, very disappointing really One quick suggestion, does your server which will be x64 have the x86 drivers installed onto it? Need to go on a course me thinks Ta JohnYou will need Client Side Extensions installed on the machines. Will let you know how I go on. This is probably the most highly recommended first step when you encounter print spooler crashing because it keeps print drivers from interfering with basic software printing processes. Server 2008 R2 Personally I don't bother with the print server role. Then, select the View Server and Manage Server permissions under the Allow column.
The first obvious sign of your print spooler crashing on Server 2008 R2 is going to be sudden print downtime for the users that depend on that particular print server. The app says that it was successful however, the following day, i run the following command and still get the drivers in the list. You won't have to deal with the hassle of redirected printers not working again. By isolating them, they inflict less damage when they choke. Performing General Printer Administration Tasks From within the Print Management console, the administrator can perform general printer administration tasks. I have read everywhere that it might be due to bad printer drivers.
I am going to delete all drivers and printers restart the server and then re add the printers. How to Join Windows Server 2008 to Active Directory Domain Select an option for setting the default printer. Again, the end result should just be that the drivers are installed on the terminal servers just using the information provided. Malformed jobs in the queue: Sometimes it isn't drivers but print jobs that cause print spooler crashing in Server 2008. Edge Out The Competition for your dream job with proven skills and certifications. I've had occasion to need to do this on a user's system running Windows 7 Enterprise 64-bit.
Store all printer settings into a file: rundll32 printui. For this reason, when reinstalling the same version of the printer driver, the driver may not be rewritten. If you are in doubt, read the entire chapter. I did not change anything else since I posted this thread, so it has to be one of those two possibilities. What am I missing in order to install these drivers without the printer being physically present? I click on the first print driver. This is the place where I am getting confused. I have checked the logs and all I get is Spooler has stopped unexpectedly.
Any help toward a solution is appreciated. This is a hack workaround because half the time if you click on a port from the list, it will change the current printer to the selected port. It's what I'm using now and it works a dream, but the drivers are a big issue as 2008R2 won't let you add in the x86 drivers manually, you have to do it from an x86 domain machine by navigating to the server, double clicking the printer in question at which point it will ask for where the drivers are and then upload them to the server for you which will allow you to deploy across your network then. So far I have tried the following wmi call, but I did not see a delete method in the objects returned. Also, is it possible to remove multiple drivers from multiple servers in bulk too? Hi Sturgeo, I think I may have to do the same and set up a 2003 R2 server simply for the printers. That's dangerous and I might not get everything Windows considers part of the driver.
Server 2008 Lesson 11 Note: If you want the server to restart automatically after the installation is completed, select the Reboot on completion check box. The built in Remote Desktop Easy Print drivers don't appear to be working for this particular printer so my assumption is that I'll need to install them myself. PrinterLogic makes that possible through its proven cost-effective, that provides all the functionality of print servers—and much, much more—with none of the usual drawbacks. Yep no problem that the computer needs to be always up. Click change button as shown above. What permission do you need to grant the user so that he can delete this job? I've got a Windows 2008 r2 server running as a print server with 70+ printers shared out. Click on File, Server Properties, Drivers tab.