Terminal Server Spool Directory Huge at 3.5GB

Win2k Terminal server has a 3.5GB directory at C:\WINNT\system32\spool\drivers\w32x86\3. I only have around 20 drivers installed for various printers in the print server properties. Can anyone tell me how to isolate what is not needed so the space can be reclaimed? Thanks!
forteksAsked:
Who is Participating?
 
forteksAuthor Commented:
V2sha, I have looked at the monitors and have the ones you have listed minus 6 as there are apple talk does not apply in this environment. I did fix the problem with C:\WINNT\system32\spool\drivers\w32x86\3 having 3.5GB of files. As stated, I only have about 20 drivers loaded for various printers on this server. I went to the printers folder, File, server properties, drivers tab. From there I looked at each printer property sheet and copied the driver files listed from C:\WINNT\system32\spool\drivers\w32x86\3 to a temp directory. Once I copied all files for each printer (many are shared amongst printers), I deleted the contents of C:\WINNT\system32\spool\drivers\w32x86\3 and replaced them with the copied files in the temp directory. This directory went from 3.5GB to 135MB. I was looking for a quick way to isolate the unneeded files, and this process took a couple of hours to manually complete, but now the directory is extremely small as a result. I have tested every printer in a session and they all work properly. Thanks for the suggestions though!
0
 
NetcraftCommented:
Maintaining the spool directory on the C: drive is bad practice for Terminal Servers. You should move it to another drive using http://support.microsoft.com/kb/123747

Can you determine which file(s) is/are the culprit? Is it the drivers or the spool files?

Do you have "Keep Printed Documents" enabled? You can check/change is in the registry: http://www.undocprint.org/winspool/registry
0
 
forteksAuthor Commented:
Thanks for the tip on moving the spool dir to another drive, however I dont have enough space on this server which is why it is on C. That was my ultimate goal In freeing up the space on C, but I need to cut the size of the noted directory down as far as I can to see if I can move it. I am not keeping printed documents for any printers. I can view the C:\WINNT\system32\spool\PRINTERS and watch the jobs move in and out of the directory. Everything appears to be driver files in C:\WINNT\system32\spool\drivers\w32x86\3. Dll's, Cfg's, and Cab's. There are about 48 thousand files in this dir. This dir is taking all of the space.
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

 
NetcraftCommented:
Is local printer redirection enabled? That is, do users get their printers remapped in the Terminal Server session? In that case, it is possible that all those drivers get installed on the Terminal Server.

Are there Print-events in the System eventlog indicating a large number of drivers are being installed?

Can you see a large number of printers under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers, on the Terminal Server?
0
 
v2shahaCommented:
forteks

You need to clean the Print hives in order to get free space and before that you need to delete the following extention files (*.Bud,*.Spl,*.Shd) as these are temporary files and need to be deleted once print job is done. then perform the Print hive clean process by using the documents i have attached in this e-mail, i hope it will help you to resolve your problem.

Cheers
How-to-remove-third-party-Print-.doc
Steps-to-Manually-Remove-3rd-Par.doc
0
 
forteksAuthor Commented:
Netcraft, I do have printer redirection enabled. When the users login to the TS- a session printer is created. Upon logoff, they are removed. I do not have a large number of printers in the key you specify- just the locally installed printers- two in all. The rest get added and removed as the users come and go. The only events regarding the printers are when they are set at login, and the deletion at logoff. This is a server that I began managing after the drivers directory was already bloated. On the server, I only have about 20 drivers loaded so the session printers can be created. The problem is, I dont know how to identify which files of the 48,000 in this directory are safe to removed. I guess I could remove all drivers from the server, purge the directory, and then reinstall the drivers on the server through the server properties, drivers tab- but I wanted to just identify what is not needed and remove the files that way. Any better way to handle this would be welcomed. Thanks for the response.
0
 
forteksAuthor Commented:
V3shaha, I've reviewed the docs you've posted. I don't have any of the temp files you mention. It looks like the docs are primarily related to cleaning up the registry; although there is the section on identifying which dll the printer is using and to rename it. Unless I misunderstood the procedure outlined, if the server only has 20 drivers installed, I would only be able to identify 20 dll files (even though a specific printer may use many files) that could potentially be removed after changing the processor to use. I have 48,000 dll's, cab's. and cfg files in this directory- no temp files. I really dont see that it will help me identify what can be removed. I also dont see the advantage of making the change over to WinPrint. Can you clarify this procedure and the ultimate results it will produce? Especially how I will be able to identify and remove most of the 48,000 files in the directory. Thanks!
0
 
v2shahaCommented:
Forteks:
========
Winprint is the print processor of microsoft and all printers must use winprint when they are ready to print. when we install any printer (like HP) they would use windprint most of the times but they have their own print processor as well. In the registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentCuntrolSet\Control\Print\enviroment you must have only following monitor listed .
1)BJ Language monitor.
2)PJL Language Monitor
3)Local Port
4)Standard TCP/IP Port
5)USB Monitor
6)Apple Talk Monitor(If you have apple computer in your enviroment)

And if you will rename the .DLL it means spooler will not load the same .DLL  which is related to the 3rd party print monitors. I have applied this on many cases and resolved them you will not face any poblem in order to print after this process. its sure.

Thank you

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.