Improve company productivity with a Business Account.Sign Up

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

which Print Drivers to I use for Windows 7 machines connecting to Server 2008 R2?

Hi experts, this is probably a stupid question, but here goes...

I have Windows 7 machines connecting to a 2008 R2 server with printer server setup. I deploy the printers using GPO to the Windows 7 machines.

When I load the print drivers for those printers in Print Management on the server, do I use the 2008 R2 drivers or the Windows 7 drivers?

On Dells webpage for the 2335DN it has both, I'm assuming its the Windows 7 drivers?

This is for the workstations to be able to print to the shared network printer..
Capture.PNG
0
ChiIT
Asked:
ChiIT
  • 23
  • 14
  • 3
  • +1
3 Solutions
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

You load the printer drivers on the printserver BUT you use the 32 and 64 bit drivers for Windows 7. (32/64 bit in case you have mixed installs)

The location is right, click new to add more drivers.
0
 
NiabingiCommented:
you will need to add both 32 bit and 64 bit drivers on the print server for each type of printer/driver you intend to use.
as for what driver to use Win 7 or Server 2008 R2, both will work equally well, i have similar setup and dont have a problem using either one.
0
 
ChiITAuthor Commented:
thank you both...a quick follow up, I have both 32 bit and 64 bit Windows 7 machines on my network, I have both 32 bit and 64 bit drivers loaded, (see attached screen shot), however whenever I print from a 32 bit machine, the 64 bit machines stop printing. When I print from a 64 bit machine, the 32 bit machines stop working...

I thought I had set it up correctly so each version of machine knows which driver to select...any ideas?
Capture2.PNG
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Patrick BogersDatacenter platform engineer LindowsCommented:
You did setup the printer part right so maybe we should look for the GPO.
How is it made?

Good way to try is to block the GPO for one 32 bit machine and one 64 bit machine, go to the machines and delete the printers.

Then to to start-> execute and type in     \\<printerservername>  and in the box that opens double click the printer you want, this would automatically start installing the right drivers.
Now with both machine do some printing tests. What is the result?
0
 
ChiITAuthor Commented:
trying that now...
0
 
ChiITAuthor Commented:
Actually how to I block for an individual machine...?
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
You could simply remove it from the OU and put it in a non assigned temporary OU and block inheritence for that OU.

To block inheritance for an OU, double-click Domains , double-click the domain containing the OU, and then right-click the OU.
Click Block Inheritance
0
 
ChiITAuthor Commented:
when I do that, run gpupdate, the GPO printers disappear, I navigate to the printers, load the drivers, and it loads, but does the same thing....
0
 
ChiITAuthor Commented:
I am wondering if there is some issue with the 32 bit driver..like perhaps the 64 bit driver is loaded for both profiles? is that possible?
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi again,

Ok, do you get spooler issues in event log on the print server?
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

I am thinking in the same direction but my mindset was the other way around, maybe 32bit drivers are installed on 64 bit machines.

But i also have a strong feeling there is something going on in winsxs. That is why i ask for logging details.
0
 
ChiITAuthor Commented:
no issues logged...
0
 
ChiITAuthor Commented:
I get this when I remote login to the server, that's all that is in the print spooler event log

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          1/9/2014 12:55:08 PM
Event ID:      823
Task Category: Changing the default printer
Level:         Information
Keywords:      Print Spooler
User:          CORP\USERNAME
Computer:      SERVER.corp.DOMAINNAME.com
Description:
The default printer was changed to NAMEDPRINTER Printer on SERVER (redirected 1),winspool,TS001. See the event user data for context information.
0
 
ChiITAuthor Commented:
its the 32 bit computers that are not printing..the 64 bit print ok...
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
however whenever I print from a 32 bit machine, the 64 bit machines stop printing. When I print from a 64 bit machine, the 32 bit machines stop working...

Made me think...... ok, clear the 32bit driver, download a new copy and try again.
0
 
ChiITAuthor Commented:
ok so here's the question..how do you clear the 32 bit driver? I can't find anywhere that lists the drivers individually on the server
0
 
ChiITAuthor Commented:
wait I found it...print management, drivers...
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Open Services.msc and stop and start the Print Spooler service
 
Open Print Management(Open command prompt, type in printmanagement.msc or type print management in to the start menu search box)
 
In Custom Filters -> All Drivers right click the printer driver you want to remove and select Remove Driver Package

*edit* cool find!!!
0
 
ChiITAuthor Commented:
so when I try to load the x86 driver from the DELL Driver CD, I click x86, say I have the disk, browse to the directory...it says..

The folder you have specificed doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems....


I know this is the 32bit folder on the disk..and I select x86 when prompted to install new driver...
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi, please look online at DELL support if they carry newer version of the driver.
0
 
ChiITAuthor Commented:
I was able to get it to load, and shows x86 driver...however it's doing the same thing.....
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Please have a look if there isnt any updated drivers available from Dell support site.
0
 
ChiITAuthor Commented:
I'm downloading now..I'm not convinced its a new driver issue...but then again, I have no idea what it could be.

there is an option to set driver isolation, currently set to system default..should that be something different maybe?
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

It describes how drivers act against the spooler and each other, i would definatelly put it to isolated mode.
0
 
ChiITAuthor Commented:
update..

ok so it's definitely the 32 bit workstations that are not working.

Summary is:
Both 32 bit and 64 bit drivers are loaded on the server
Printers are deployed via GPO
The 64 bit workstations print perfect
the 32 bit workstations get a message that says "failed to print"
I have deleted and reinstalled the 32 bit driver, and it does say x86 by it
There is nothing in the event log that I can note of any significance.

I will do a driver update tonight.

It seems like somehow the 32 bit workstations are not recognizing the 32 bit driver from the server but that is a guess... I have loaded a manual printer on aa 32 bit workstation, and it prints..but I'd like to keep these gpo based instead of having to manage printers on each PC.


Any other ideas?
0
 
NiabingiCommented:
your print server properties should look like this, see attachent
remove the 32 bit driver from the server and reinstall it.
do you have any problems with installing the current 32 drivers on the workstations
drivers.PNG
0
 
ChiITAuthor Commented:
Hello, thank you for responding.

Attached is what mine looks like, it looks correct.

I have no issue loading the 32 bit driver locally on a 32 bit PC and manually creating a printer that prints with no problem.

When you say remove the 32 bit driver from the server and reinstall, do you mean in PRINT MANAGEMENT DRIVERS, RIGHT CLICK DELETE?

I've done that with the same result, however, when I reloaded I did run into an issue, its a Dell 2335DN, I downloaded the current drivers, and when I add a new driver, select x86, and navigate to the 32 bit driver directory that I just downloaded, it says

"The folder you have specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems" (see attached)

Attached is the downloaded directory also. perhaps I'm using the wrong 32 bit driver...
printdrivers.jpg
driverdirectory.jpg
x86-error.jpg
0
 
NiabingiCommented:
ok attached is what the print server properties box looks like, you have to select a printer for it to be available at teh top of the toolbar.
from that window click drives tab and you can add and remove driver from there.
click add and browse to the location of the 32 bit drive, you should not get that error doing it that way.
server-prop.PNG
0
 
ChiITAuthor Commented:
ok, I was going it from within Printer Management, drivers...

I will try deleting from there and see if that works...thank you for the help, it might be later today before I get a chance to test it..
0
 
ChiITAuthor Commented:
Hello, I removed from the drives tab and reinstalled, and at first it did not work, same result. I ended up logging off as the user I was using, and logged on as another user on the same computer (who also happens to be an admin account), and the printing worked. So I started to suspect it had something to do with the account on the computer/AD. I logged back on to the original user, and the printing worked. Or, perhaps when I logged back on, it did a group policy update?

I need to test it on another computer but won't have a chance until tomorrow. I'll update you tomorrow, thank you for the help so far..
0
 
wyliecoyoteukCommented:
The 32 and 64 bit drivers must be exactly the same version, otherwise the clients may try to download both.
0
 
ChiITAuthor Commented:
Thank you, I read that somewhere and now that you say that the client will try to download both, it makes me think that may be it..

Same version as is for example both need to be 10.2.13 (I made that number up) or same version as in both Dell 2335dn print drivers?
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

This i overlooked, it should be 3.5.10.0 on both, i assumed you downloaded the most current version together.
0
 
ChiITAuthor Commented:
I updated the drivers on Friday night, before the two were drivers for the same printer, but different versions, now they are the same..could that be causing the issue?

see attached
printdriversBEFORE.jpg
driverNOW.jpg
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
On the NOW it stated Windows NT x86 which i wonder if you have installed the WindowsNT/2000 drivers. Where we expect to see Windows x64 like in the picture.

Are you sure the Windows NT x86 are for windows7?
0
 
ChiITAuthor Commented:
here is the driver I downloaded.

http://www.dell.com/support/drivers/us/en/04/DriverDetails/Product/dell-2335dn?driverId=PKHWK&osCode=W732&fileId=3290118292&languageCode=EN&categoryId=DD

I extracted it and used the driver that was in this directory:

\Dell_2335dn_MFP_Driver.zip\Printer\PCL\WINXP_2000_VISTA_32

see attached. the only thing I don't understand completely is that the version doesn't match the version for either driver that is on the webpage.....
delldriverpage.jpg
delldriverdirectory.jpg
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
That is strange... maybe this link contains the right drivers.
0
 
ChiITAuthor Commented:
I'll give that a try and get back to you
0
 
ChiITAuthor Commented:
It loaded and show the same 3.5.10.0 with NT...not sure ..
0
 
ChiITAuthor Commented:
I tested today all of the 32 bit workstations and all seem to work now, I'm guessing it was the version of driver since that is the last thing I did based on your recommendations.

Thank you both for the help!
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Super!!!
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.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 23
  • 14
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now