Hello all,
We have 2 different domains with their own printer servers. All are running Server2008R2x64 and here is what we are seeing:
All the machines have the same base image being Win7x64 Enterprise. We have approx. 600 computers total
One domain is called ABC had the Print server initially with HP Universal Drivers 5.4 PCL that were upgrade to 5.5 PCL
This domain suffer from the random unable to print Event 372 issue with the the error of 5 Access Denied. Were get random calls about the inability to print and most of the calls tend to be on a Monday.
The other Domain is called DEF has 3 Print Servers. Two of the Print severs are in the USA and one is in LDN. The two PS in the states originally were configured with HP universal Drivers 5.4 PCL and both were upgraded to 5.5 We get calls from users of these 2 print servers ever single day. Aproxximately 5 a day complaining that they cant print.
Built a brand new SVR2008r2x64 server with only HP universal 5.7 PCL and added only 20 machines of known people whose machines were having printing issues. We have purged out all the old drivers and their settings etc with the registry changes shown below. Even on a brand new PS with the HP 5.7 drivers added initially we see the same printing error Event 372 Access Denied 5......
The LDN PS that only the London users connect to for printing is still using 5.4 pcl and hasnt been upgrade. These users have NEVER had a client lose their ability to print. They are in good shape.
We have Lumension Sanctuary Device control on all our machines. I use to believe that this was the culprit in such a way that is was too restricted on the machines but if it was all the machines would suffer and not simply a random handful which is the case for us.
This is the script we run on machine that are afflicted. Even doing this doesn't prevent the same machine from becoming a victim again.
FYI the last 2 lines of the regkey are added as of today per the new thread so I can't confirm if the LOADTRUSTEDDRIVERS and TRUSTEDDRIVERPATH work or don't work for us. I will update as i get more info.
pushd %~dp0
ECHO OFF
Echo You must run this as Local Administrator to allow write access to the registry
pause
regedit.exe /S "HPDriversCleanUp.reg"
Echo The Registry has just been modifed.
net stop spooler
net start spooler
Echo The Print Spooler has Sucessfully been stopped and restarted
Echo Add back the necessary HP user's printers to the machine
Echo You might need to restart the computer in order to finalize these changes
Echo Hit any key to exit this CMD Window
popd
pause
Below is the contents of the HPDriversCleanUp.reg key Basically it cleans up the junk files and whatver we believe needs to be purged. A compliation of all the posts for the internet and their remedies.
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 5 (v5.5.0)] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 5 (v5.7.0)] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.4)] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Universal Printing PCL 6 (v5.5.0)] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HPMLM135] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HPMLM121] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HPPMOPJL] /f
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\HP Universal Print Monitor] /f
[-HKEY_CURRENT_USER\Printers\Connections] /f
[-HKEY_CURRENT_USER\Printers\Settings] /f
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers] /f
"LoadTrustedDrivers"=dword:00000001
"TrustedDriverPath"="(“”)"
I know we aren't alone with this issue and it is a very serious problem in my organization that needs resolutiion. Hopefully my scenarios can shed new light on this. It been ongoing for over 8 months. Any suggestions are welcome. Thanks for reading.