Wednesday, February 06, 2013 9:51 PM
I have deployed network printers using Print Management. If I log onto a users PC as an admin I can see the printers, however if I log back in as a user I can not. So I know that the PC is getting the printers, I just can't figure out how to get the user to see them. Users are not local Admins on their PC's. The PC's in question are Windows 7. The server is Win Server 2008 R2.
My GPO has Add Printer Wizard - Network Scan Page (Managed Network) as Enabled. I also have Point and Print Restrictions set to Enabled, with Users Can Only Point and Print to These Servers: "our print server". Do Not Show Warning Or Elevation Prompt is set for installing drivers for a new connection, and updating drivers for an existing connection.
I feel that I have missed something on the local PC, if the regular user can't see the printers but a logged in admin can.
Thursday, February 07, 2013 1:32 AMAnswerer
Keep in mind that the Admin can never see printer connections for other users in the Devices and Printers folder. A user can only see their printer connections since the connection in created in the users context.
It almost sounds like the users are not in the same security group as the admins.
Are the printers listed in the gpresult report for the user? Also verify that the policy the printers are in has been applied for the user. If the user does not get the policy, they will never get the connection
Alan Morris Windows Printing Team
Thursday, February 07, 2013 3:00 PM
When I do a gpresult as the user, I see that the GPO for that printer has been applied. How can I tell of the user should be able to see the printer?
What is unusual is that I have one network printer that everyone can see. I have set the GPO of the printer that they can't see, to be the same as the one they can. This has not worked.
Today I am going to delete the GPO and recreate it. Hopefully that might work.
Is their a local security setting for printers that I might be missing on the PC's?
Thanks for the help!
Thursday, February 07, 2013 8:26 PMThanks for the help. I figured it out. The printers were not shared correctly. All is good now!
- Marked As Answer by DebLarkins Thursday, February 07, 2013 8:26 PM