Jump to content

Recommended Posts

Posted

I am having some issues with deploying printers from our server 2016 to our Windows 10 stations.

 

The school is really simple...

One shared network printer in a corridor.

There is then one network printer in the main office for the receptionist.

 

... could't it be an easier setup?! Windows 10 seems to have other ideas.

 

I have set up a basic policy to deploy the shared printer to all client computers:

2.PNG

The policy is deploying without an issue, however, the receptionist's printer is showing on all of the client computers when users log in. And sometimes, it is even the default.

There is obviously some sort of network discovery going on.

 

Does anyone know how I can stop this? Also, not sure how PDF printer is getting set as default?

The network printer is HP Color LaserJet CP4005, the offending receptionist printer is named NP16A8862.

1.PNG

Posted
Check the printer port, is it installing as WSD?? If so, try turning this off and see if it works. Helps here but i use vb script to map which you welcome to have
Posted
Check the printer port, is it installing as WSD?? If so, try turning this off and see if it works. Helps here but i use vb script to map which you welcome to have

 

Would I need to turn this off on the printer if it is on?

Posted
I think you need to use group policy preferences to specify the default printer. I'm not certain that Gpo lets you set default?
Posted
Would I need to turn this off on the printer if it is on?

 

Sorry for late reply, yup on the network config page on the printer web portal. Not at a computer to send a screenshot

Posted

Have you got the latest ADMX templates for Win10 on your AD server? We deploy printers via User Configuration > Preferences > Control Panel Settings > Printers, which allows you to set defaults etc.

 

Can you check all other GPOs to ensure the mystery printer isn't being deployed by another GPO?

 

You shouldn't need to deploy it in Computer Configuration as well as User Configuration, so it's worth removing either one of those, depending on your AD configuration. Presumably you haven't got your PCs and users in the same OU in AD, or are you deploying that GPO to several OUs- some of which contain PCs and some contain users?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...