Problem using Multifunctional Laser printer

Hi All,

I have server 2003 that has Fileserver, Terminalserver, Printerserver roles installed.

Some of my clients are connecting with Remote Desktop Connection, and they want to use they local printers or Scanners or sometimes Multifunction Laserprinters.
I get the spoolsv.exe application error sometimes and the spooler service is stopping and needs to restart manually.
I should install scanner drivers for these MFP laser printers:
Philips LaserPro 6050
Samsung SCX-4521F

Can somebody help me in this?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

agriboy1980Author Commented:

Has anybody ever managed to install a scanner driver on a Windows 2003 Terminal Server enviroment?

Larry Struckmeyer MVPCommented:
Plain printer drives are (usually) going to be fine.  Scanner drivers on a TS, not so much.  Printing will work if the exact printer name and driver are on both systems.  There are third party programs to manage TS/RDS printing, most think they are very worthwhile.
agriboy1980Author Commented:
I have found some drivers for this Multifunctiom laser printer. All the drivers are there even for scanner and compatible with Win Server 2003.

The problem is that he server is still logging an event:"SmarThru Pc Fax" driver is not installed!

The server has print server, fileserver, DC, GC, terminal server roles installed.

How should I apply this missing driver "SmarThru Pc Fax"

Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Larry Struckmeyer MVPCommented:
I have never seen a scanner driver work over TS.  Not sure it would make any sense for it to do so, as the device and the human and the computer that are needed are all at the "local" end.  If the scanner driver was installed on the remote server, what use would be made of it?  There (normally) is no such scanner there, and if there was, there is no human to put anything  in it to be scanned.
Spike99On-Site IT TechnicianCommented:
Is the driver event you're seeing repeated in the System event log an Event ID 1111?

You can ignore those errors: they just indicate that a local printer on a client pc is using a driver that the terminal server doesn't "recognize" (in other words, it's not installed).  So, it's basically a warning that the printer isn't going to be redirected to the terminal server because the driver isn't installed on the TS.

Those errors are no cause for concern: they're a way for Admins to find out which drivers users have installed for their local printers that may need to be installed on the server.  It's up to you whether or not you'd like to install them.

In this case, I wouldn't worry about installing the fax driver: it probably won't work on the terminal server anyway.

I hope this helps!

agriboy1980Author Commented:
ok, and is there a way to make these
errors dissappear from event log ?
Larry Struckmeyer MVPCommented:
Not that I know of.  But still trying to differentiate between the printer part and the scanner part.  If you can find a printer only driver you should be able to install that on the TS/RDS server to allow the user to print.  In some cases the manufacture requires the device to be present via usb  on the target system before you can install any of its drivers, which can be a pain.  As the administrator, you have to decide if you want to deal with this or require that your users purchase a standard inexpensive printer that you can support.  Still, the warnings for devices for which there is no driver on the TS/RDS server will continue.
Spike99On-Site IT TechnicianCommented:
There is a way to keep them from being logged:
1.  From the printers folder, click on File > Server Properties.
2.  Click on the Advanced tab
3.  Uncheck the options to "Log spooler error events," Log spooler warning events" and "Log spooler information events"
4.  Click OK to apply the change

However, I don't think it's a good idea to do that because if users experience problems printing, you won't see any of the events that can help you troubleshoot the issue.

But, it is ridiculously easy to turn logging back on for printing issues, so I guess that's up to you.

I personally wouldn't worry about the Event ID 1111 errors: we have TONS of them on our terminal servers. If you're concerned about your event log filling up, uncheck the options to log spooler information and warning events, but I would advise logging spooler error events.

I hope this helps.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Larry Struckmeyer MVPCommented:
@spike99/Alicia:  Good catch.  I learn something here every day.  Thanks for that.
Spike99On-Site IT TechnicianCommented:
No problem! Always happy to help out. :)

thanks for the points!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.