Windows 7 Thread, Printer Deployed via GPO Not applying on all machines in Technical; Hi guys,
We have a print server with all our printers installed. For each IT room we have allocated a ...
23rd April 2013, 04:03 PM #1
Printer Deployed via GPO Not applying on all machines
We have a print server with all our printers installed. For each IT room we have allocated a printer via GPO.
We did this by creating a blank GPO on the DC, right clicking the printer on the print server, deploy with Group Policy, browse for the blank GPO we created and select Per Machine.
We then linked the GPO to each room's OU and most PC's have picked it up. However in each room we have about 5 PC's that don't show the printer. No matter who logs onto that PC, no-one gets the printer without manually adding it from the directory. Sometimes its not in the directory and wont let you add it as it already thinks its allocted but doesnt show in the printers list.
A gpresult /h reports the printer policy applied to the machine fine, yet it doesnt show.
Any ideas? Can a printer be allocated differently per machine which has a better success rate?
Last edited by Darylrese; 23rd April 2013 at 04:09 PM.
IDG Tech News
23rd April 2013, 11:31 PM #2
You could create a couple of batch files using PrintUI as below. Use the GPOs you've created to have this script run at machine startup. This should do the trick.
rundll32 printui.dll PrintUIEntry /ga /n "\\printserver\Single_Sided_B&W"
rundll32 printui.dll PrintUIEntry /ga /n "\\printserver\Double_Sided_B&W"
rundll32 printui.dll PrintUIEntry /ga /n "\\printserver\Single_Sided_Colour"
rundll32 printui.dll PrintUIEntry /ga /n "\\printserver\Double_Sided_Colour"
net stop spooler
net start spooler
Thanks to bainer from:
Darylrese (24th April 2013)
24th April 2013, 09:40 AM #3
Do I just create a .bat file for the above and run it as a startup script?
24th April 2013, 10:04 AM #4
Check these machines don't have a corrupt driver installed on them. I've had a similar problem that the printer constantly tries to install but fails as it thinks the driver is already installed on the client and then fails as the driver doesn't work. If you remove the driver on the client and then re-try (and check it works) it may clear the problem. I've had this primarily with Kyocera KX drivers but have updated these to Universal ones.
24th April 2013, 11:13 AM #5
Script seems to have worked on my machine to allocate a printer, thank-you!
Hopefully it will resolve the issue with machines missing the printers too!
By IT_Man_Dan in forum Windows
Last Post: 15th November 2012, 12:21 PM
By Chuckster in forum Windows
Last Post: 1st July 2009, 09:58 PM
By craigg in forum O/S Deployment
Last Post: 11th March 2009, 11:16 AM
By leco in forum How do you do....it?
Last Post: 8th August 2008, 12:04 PM
By rlculver in forum Network and Classroom Management
Last Post: 22nd April 2007, 10:53 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)