Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2755
  • Last Modified:

How do I install 64 bit print drivers on a 32 bit Windows 2003 printer server?

I am running terminal services on 32 bit Windows Server 2003. I have clients running 64bit systems. The server will not host 64 bit print drivers so they aren't able to print from their sessions. Any suggestions? Thanks in advance.
0
2629326
Asked:
2629326
  • 6
  • 4
  • 3
  • +2
1 Solution
 
mhasle1974Commented:
Hi,
You will have to install alternate drivers.
To do so, extract your 64 bit drivers on your print server, right clic on the printer object.
Then click on additional driver.
You should have a Windows XP x64 and/or Windows Server 2003 check box. Check it.
When you will apply it, you'll be prompted for the drivers location.

You might also be prompted for the Windows 64 bit system files if the printer manufacturer driver package does not contain the MS system files. In that case, you'll have to put you Windows 64bit client CD on your print server CD Rom drive.
0
 
Death_RatCommented:
You have to create a folder with the drivers, not the installation (setup) files, then you could add the printer usng a script that actually points to get the drivers from the newly created folder.

I will work on something for you.
0
 
mhasle1974Commented:
You do not necessarily need a script to install the drivers.
You just need to provide the path to the INF file of the installation files.

What type of printer do you have ?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
2629326Author Commented:
Let me re-phrase the question; do I need to install any additional software/drivers on a 32 bit Windows 2003 server running TS so that anybody connecting to it from a terminal running 64 bit Windows are able to print to their own local printers?
0
 
mhasle1974Commented:
The only you need to do in that case is to install on that Terminal Server the exact same driver name.
The plug'n play name for the drivers needs to be the same like on both server.
You do not need to add additional drivers, but just a driver with the exact same name.
Then, when you connect from the clients, you need to make sure that the local printers are installed on the server.
0
 
tigermattCommented:

In theory, since the clients are connecting to the Terminal Server, this should not be an issue. Drivers only tend to cause a problem if the Terminal Server is also a Print Server and printer connections are being pushed direct to the client machines.

However, in most cases the 32-bit drivers for a printer are different to the 64-bit drivers, and they are not interchangeable.

The above comments seem to be missing the point on how to install the 64-bit drivers on the 32-bit Terminal Server. You cannot simply go to the server and load 64-bit drivers, as the server will say the drivers are for the wrong architecture.
Instead, browse to the server from a 64-bit workstation (\\servername) and expand the 'Printers' folder. Go to File > Server Properties and click on the 'Drivers' tab. From here, you can load the 64-bit driver file for each printer and watch the drivers uploaded to the server.

Since Windows references drivers based on name, the 32-bit and 64-bit drivers must have the same driver name. If there are any differences, you will not be able to use the printer in both 32-bit and 64-bit modes at the same time.

-Matt
0
 
2629326Author Commented:
I guess that my issue would be that I don't have any 64bit clients. I have terminal users that own 64 bit machines and they aren't able to print to their printers from home while logged onto the terminal server. The goal is to enable them to print from home. If they had 32 bit machines then I'd simply install their printers' drivers on the terminal server and they'd be good to go. The problem is they have 64bit Windows Vista, etc. etc.
0
 
tigermattCommented:

The Printer driver needs to be installed from a 64-bit client. Can you get access to a 64-bit device or one of the home users' machines which runs 64-bit?

Due to the way the driver model works, you cannot install 64-bit drivers from a 32-bit client.

-Matt
0
 
2629326Author Commented:
Can I install the drivers from the server console? Anything out there that would enable me to do that?
0
 
tigermattCommented:

Not that I am aware of. The only advice I have ever been able to find is that you must use a 64-bit machine to install the 64-bit drivers, a 32-bit machine to install the 32-bit drivers.

This is due to the architectures and the way the drivers are processed when being installed.

-Matt
0
 
mhasle1974Commented:
Hi,

Matt, I really do not agree with you.
using a 64bit workstation to add the additional driver is not mandatory. You just need to install an additional driver.

Moreover, the situation here does not need to have both drivers installed on the same system. The problem is that the Terminal server and the clients do not have the same drivers installed. When using printer autocreation, then the Terminal server will list the printers installed on the client. To map a printer object from the TS session to the printer object on the client, we need to make sure that the same driver (for the correct architecture) is installed on both side.

So if you've got on the TS 32bit the driver for your printer (like "Lexmark T650"), and the client comes with a printer object with the 64bit driver called "Lexmark T650", then there will be a match, and the TS will be able to create the printer object automatically within the session. The real important thing is the printer driver name that need really to match.

If you want to minimize the number of drivers installed on the TS, you can use the Printer Mapping to create a compatibility between two drivers. So if the printer driver matches on entry, the session will automatically create a printer object using another printer driver.

You've got details here :
http://www.msterminalservices.org/articles/Windows-Terminal-Services-Printing.html

Now, all this was based on the assumption that the printer was mapped on the printer object from the client.

Michael
0
 
2629326Author Commented:
Thanks for all the input. The printer in question is a Brother MFC-5440CN (64bit). I have all the drivers loaded on the server. When she connects to the server, all of her other printers are mapped and I see them in the printer list. She can see her printer in the dropdown but she's just not able to print to it. I don't see any printer ports opening up for that printer either...
0
 
hatheharikenCommented:
a point to clarify - printers are never 32 bit or 64 bit specific.
only the drivers are.

in cases where it looks confusing (though it really is not), a time tested method is to install the printer as a local printer on the problem pc, then create a remote port and point it to the print server.but there is no need to do this in your case.
simply obtain the 64bit drivers and install it on the client PCs
these links should be of use to you:
http://download.microsoft.com/download/5/D/6/5D6EAF2B-7DDF-476B-93DC-7CF0072878E6/multiplatform_INF.doc
http://technet.microsoft.com/en-us/library/cc732946.aspx
http://www.computing.net/answers/networking/print-driver-issues-32bit-server-/32680.html
http://www.edugeek.net/forums/windows/24994-64bit-client-citrix-but-only-32bit-print-server-driver.html

the DOC file from microsoft solves the entire problem, by helping you write a custom INF installation file for installing x64 assets on a x86 platform - the most foolproof solution to your problem.

do let us know how it works out for you,
cheers!
hathehariken.

0
 
2629326Author Commented:
GREAT!!! Never written an INF before... guess now is as good a time as ever to get started. Cool - I'll get back to you soon...
0
 
hatheharikenCommented:
god to hear that enthusiasm!

if you have any problem deploying the INF, do post here.

cheers!
hathehariken.
0
 
2629326Author Commented:
Okay I didn't quite understand the MS .DOC but I did resolve the problem. Everything I've read to this point made me realize that I could achieve mostly the same results by simply installing the printer locally on the server from the server, not to mention via RD (I used a TS printer port - not sure if that mattered). I then went to additional drivers tab and check off x64bit etc.. I was prompted to installed a particular file off of a x64bit Windows Server CD (lucky for me I had one laying around...). Once the x64bit driver was checked off, I tested it out and WAMO! it worked. Thanks to everybody for trying!    
0
 
hatheharikenCommented:
good good!

the problem got solved - thats the main thing.

cheers!
hathehariken.
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

  • 6
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now