More importantly, though, several tech user forums are reporting that the Image Writer is most likely the cause of problems with the service "spoolsvc.exe" bringing CPUs to their knees. A user may accidentally try to print to the Image Writer when they think that they're printing to a physical printer. Noting that the physical printer isn't printing, the user tries several more times to send documents to it. The cache for the Image Writer fills up and spoolsvc.exe pegs at 99% CPU utilization.
This Image Writer is most likely not used by anyone in your organization. So one way to preempt future problems with spoolsvc.exe on your network is to remove this virtual printer from all workstations. My recommendation is to create a new group policy object (GPO) that executes this short script at user logoff:
c:
cd \windows\system32\cscript
prnmngr.vbs -d -p "Microsoft Office Document Image Writer"
I've tested and implemented this type of GPO and haven't had any problems thus far. But be aware that prnmngr.vbs is an 1161-line VBscript. Executing a script of this length at logon or logoff may cause system delays due to its length.
By giving this script its own GPO, you can enable it for a short period of time (a few weeks), giving all your users a chance to log on and log off once. When you're satisfied that "Image Writer" has been removed from all user accounts, you can disable the GPO.
