Problems with deploying printers at specific site

[swpmre]

Dear all,

I'm tearing my hair out here, so I've given up and I'm posting here for the first time in years!

 

This is for an Adult Education Service. We have a number of remote sites across the city, and have just opened a new one.

 

At this new site I cannot deploy some networked printers - others work ok. But it is two classrooms (two separate OUs with specific printer group policies for each classroom).

 

We deploy using Windows Server. The configuration is the same as for all our other sites, but the printers just do not appear on the computers for any users (including admin) at this site. These are Brother HL-L2360D and we are using the latest drivers.

 

The printers did initially appear, but after a few days they disappeared.

 

The PCs are Windows 10. Everything is fully patched.

 

I cannot find any errors in the logs.

 

If I run GPRESULT /SCOPE COMPUTER /r I see that the PC is receiving all the correct and relevant GPOs.

 

I have tried deleting the printers and the queues and redeploying it all, and the problem still doesn't get solved.

 

I really can't see what is happening that is different to our other sites, or classrooms.

 

Any ideas gratefully received.

martin

[Rob_D]

Can you manually add the printers to the computer?

 

We've had issues with the GPO not being able to install drivers for some printers. Logging on as admin allowed us manually install the driver and then they worked. Now we deploy the drivers for those printers as part of our build, which seems to have sorted the problem.

[badders]

Have the PC's got security update KB3170455 installed? It's a print spooler update that can cause issues like you seem to be having. We removed the update and printers re-appeared after a restart.

[swpmre]

Definitely not, we had the KB3170455 fun last year and I've checked its not deployed.

[swpmre]

Bingo. Well not quite. But enough to get me to isolate the problem - turns out that the PCs were x86 and not x64 and the queue was deploying the wrong driver for that room. So obvious! Thanks for getting me back on the right track. Edited January 19, 2018 by swpmre