We have been having trouble with print spooler failures with a Terminal Server Farm recently and I recently discovered a cool feature of the 2008R2 Printer Manager.
You can select a driver and set it to isolate which means the driver will have it's own isolated virtual print spooler , This means it wont share the common print spooler and in the event of a buggy driver it wont pull the whole print spooler down , only the printer using that particular driver.
Remote Desktop Easy Print and a HP Universal Print Driver can act in similar ways and therefore can clash, witch would make sense to isolate each driver.
Its a really cool feature that not many people know about and can really help troubleshoot print spooler problems.
If your having trouble with a driver which is isolated , it will then have its own process and you can use Process Explorer from sysinternals to analyse that process.
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
Not sure process explorer will help with print spooler issues. I've written several articles on this topic - print spooler keeps stopping error fix
ReplyDelete