• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1604
  • Last Modified:

Lexmark T650 (MS) print driver. Terminal Server support?

Is there a way for us to add support for this printer on our 2003 terminal server?   Our boss uses this printer at home, and when he logs on the the event log error shows the unsupported printer as being a "Lexmark T650 (MS)".  We did sucessfully install the "Lexmark T650" driver from their website, but it does not match for the "Lexmark T650 (MS)".
0
JReam
Asked:
JReam
1 Solution
 
Spike99On-Site IT TechnicianCommented:
In order for printer redirection to work, the driver name on the server must be an exact match for the driver on the client PC, otherwise you will get Event ID 1111 errors in the event log.

If you can't load a driver with the exact same name, you can "map" the print driver to a different model.

Here is the Technet article on Event ID 1111 that also gives some tips on how to set up printer driver mapping (see the "Create or modify a custom printer mapping file" section at the end):
http://technet.microsoft.com/en-us/library/cc775141(v=ws.11).aspx

Basically, what you need to do to set that up is to add two registry entries on the server (PrinterMappingINFName and PrinterMappingINFSection), then create the print driver mapping INF file.

You can use the sample on that page to create your own INF file.  Following the example, they have the "Printers" section as the section where you would place the drivers you want to map, it would look something like this:

[Printers]

"Lexmark T650 (MS)" = "Lexmark T650"

Open in new window


So, when a user logs on with "Lexmark T650 (MS)" driver, the server will use the installed "Lexmark T650" driver instead.

I hope this helps.

Thanks,

Alicia
0
 
nobusCommented:
not only the driver name, but also the driver must match
i had this problem when installing a 5850 deskjet - no 64 bit drivers; but you can use the 5600 model driver
i was never able to install this on my xp PC, and use the same printer, since it won't accept the 5600 driver
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now