Solved

'Add device ' wizard in Windows 10

Posted on 2016-07-27
5
20 Views
Last Modified: 2016-10-07
Hi -

We're running Windows 10 and Server 2012 R2.  Previously (using Windows 8.1), our users were able to add networked printers (without admin credentials) by going to the Control Panel --> View devices and printers --> Add a printer --> and then selecting the desired printer.  With Windows 10, it's now prompting them for admin credentials.  I've tried just about every GPO option to disable this.  The funny thing is that when adding a printer as a non-admin user using the UNC path, it works fine; just about any other method of adding printers works as well.

Our users only know the control panel method and it will be tough teaching them a new way,  Is there any way to allow non-admins to install network printers through 'add a device' under 'devices and printers' in the control panel?
0
Comment
Question by:Emeka Ibekweh
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 95

Expert Comment

by:John Hurst
ID: 41731086
Generally I have found (Windows 7 and up) that installing Printers need Admin Credentials.

In gpedit.msc -> Computer Configuration -> Administrative Templates, Printers, there are settings you could try:

Add Printer Wizard, disallow installation of printers.
0
 
LVL 12

Assisted Solution

by:Benjamin Voglar
Benjamin Voglar earned 250 total points
ID: 41731092
We have Windows Server 2012R2 print server and users do not need any Admin Rights.

For users who have printer at home, we enablet this GPO:

Enable Users to install printers
0
 

Author Comment

by:Emeka Ibekweh
ID: 41731096
I too have my GPO configured that way.

Our issue is internal; staff cannot add a printer (via Control Panel/Devices and Printers/Add a Printer) without being prompted for admin credentials.
0
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 250 total points
ID: 41731271
Nothing has changed between win8 (or 7 actually) and 40 in this regard. If the driver is signed and trusted and supports point and print, admin creds are not required.

What is more likely the case is that the driver does *not* support point and print, and was staged or pre-deployed with the win8 image (via script or similar.) installing such a driver requires admin privileges. But if the driver were already included in the image or was staged via script, then the user can simply add the printer.

But if the driver is *not* already present, adding the printer initiates the driver install as well... and presto... credentials are required.

Definitely see this more when people rely on "out of box" drivers. 8.1 and 2012 R2 have the same core, same out of box drivers. No issues. But people deploying 8.1 with a 2008 R2 print server would have the same problem. Not because of 8.1, but because 8.1 didn't have the same out of box drivers. Even using a native 2008 R2 driver could trigger the prompt.
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
free print management solution 5 47
How to backup a Windows 2012  virtual server using VEEAM backup 1 65
dpm 2012 r2 3 27
Windows Server 2012 Start Menu 6 51
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question