Print drivers not loading on client machine
I have a print server set-up with multiple printers.
All my Xerox printers when pushed out via group policy work fine on my Windows 7 machines.
All my other printers when pushed out via group policy do not allow me to print.
There is no error. The print job simply does not show up.
It is not until I browse to the printer UNC path on the end user machine, right-click and choose connect does the print driver load and then I can print to the printer.
On the print server, all printers that do not allow me to print to them from the Windows 7 end user machines have the Additional Drivers on the Sharing Tab greyed out.
What do I have to do so all printers can be print from?
All my Xerox printers when pushed out via group policy work fine on my Windows 7 machines.
All my other printers when pushed out via group policy do not allow me to print.
There is no error. The print job simply does not show up.
It is not until I browse to the printer UNC path on the end user machine, right-click and choose connect does the print driver load and then I can print to the printer.
On the print server, all printers that do not allow me to print to them from the Windows 7 end user machines have the Additional Drivers on the Sharing Tab greyed out.
What do I have to do so all printers can be print from?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If they are IP based you can try to access the printer website with a browser from those machines. Is it possible that you have other dynamic IP machines that try to take and lease the printer IPs or are the printer IPs static and DHCP disabled? I just figured that is one test more you can do past the ping test to make sure you are pinging the printers.
ASKER
Aaron -
Excellent questions.
The printers have statically assigned IPs.
I half think it is related to the drivers somehow. They are older HP devices and could be "flaky" on a Windows 2012 R2 print server.
Testing now actually and report back.
Excellent questions.
The printers have statically assigned IPs.
I half think it is related to the drivers somehow. They are older HP devices and could be "flaky" on a Windows 2012 R2 print server.
Testing now actually and report back.
ASKER
Just tested the following using a test machine with a user that has domain admin rights.
When deploying printer again using the type 3 manual install and printing from test machine, the client machine asked to install driver at first use twice and then gave "A StartDocPrinter call was not issued" pop-up. Chose OK, tested print again and it passed thru.
Next test is on the HP machines. These might be trickier given that they are older. Will report back and hopefully finish this!
1.
Uninstall Dell 1320c driver (type 4) that was automatically installed from Windows when setting up print driver on print server. Note this install method never gave the option to install a 64-bit then 32-bit driver.2.
Re-install Dell 1320C driver (type 3) manually from drivers that were downloaded from manufacturer and was able to install both the 64-bit and 32-bit versions.When deploying printer again using the type 3 manual install and printing from test machine, the client machine asked to install driver at first use twice and then gave "A StartDocPrinter call was not issued" pop-up. Chose OK, tested print again and it passed thru.
Next test is on the HP machines. These might be trickier given that they are older. Will report back and hopefully finish this!
ASKER
As I move thru these HP printers, what is preferred for print drivers?
PostScript
PCL5
PCL6
ASKER
Aaron -
It worked. I relied too much on the automatic Windows process and chose the driver that is said matched the model of printer. It seems that when I pull down the driver from the manufacturers website and deploy via group policy with that printer, it works.
I have about a dozen or so printers to do this with but am satisfied with my test on the two printers from Dell and HP.
Thanks again!
It worked. I relied too much on the automatic Windows process and chose the driver that is said matched the model of printer. It seems that when I pull down the driver from the manufacturers website and deploy via group policy with that printer, it works.
I have about a dozen or so printers to do this with but am satisfied with my test on the two printers from Dell and HP.
Thanks again!
That's great, for the record I usually go with Post Script or PCL 6. If performance is an issue usually use the PLC because PS can sometimes slow things down. However I think that PS does give a bit more options for the user. Either one should be fine for what you described. Glad I could be of help!
ASKER
Downloading the print drivers directly from the manufacturers website and then choosing those drivers during installation of the printers on the Windows 2012 R2 print server seemed to work when deployed via Group Policy.
The no-print issue seemed to occur when I used printers that Windows had already loaded and available to use during printer set-up.
Not sure why the Windows process did not work but choosing the driver from the manufactures website did.
The no-print issue seemed to occur when I used printers that Windows had already loaded and available to use during printer set-up.
Not sure why the Windows process did not work but choosing the driver from the manufactures website did.
ASKER
I will delete and re-add then test one of the printers in question and make sure it work with my W7 clients.