Non admin user can't install driver from shared printer

Norell 26 Reputation points

I am running into a problem where non admin user cannot install the shared printer. If I use admin user there is no problem at all.

I have tried the following
-Turn Off password in the host computer in the advance sharing settings.
-Turn on file and printer sharing in the host computer in the advance sharing settings.
-Reinstall printer driver in the client computer printer using admin user.

I got stuck with the credentials below even though my user and password are correct.




Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
613 questions
{count} votes

5 answers

Sort by: Most helpful
  1. Alan Morris 1,041 Reputation points

    @Norell ,

    What's up with the IP rather than a machine name?

    Is this a workgroup configuration?

    If you do not need to know who is printing, enable the guest account so all jobs go into the print system as guest.

    As long as the machine is not running a Home version of Windows, use the MMC Local user and groups snapin to enable the guest account.


    0 comments No comments

  2. Limitless Technology 38,861 Reputation points

    Hi @Norell

    By default, non-admin domain users do not have permission to install the printer drivers on domain computers. To install a driver, the user should have local admin privileges (must be a member of the local Administrators group).

    You can use Group Policy to allow users permission to install printers

    Create a new (or edit an existing) GPO object (policy) and link it to the OU (AD container), which contains the computers on which is necessary to allow users to install printer drivers (use the gpmc.msc snap-in to manage domain GPOs). You can implement the same settings on a standalone (non-domain) computer using the Local Group Policy Editor (gpedit.msc).

    Expand the following branch in the Group Policy editor: Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options. Find the policy Devices: Prevent users from installing printer drivers.

    Set the policy value to Disable. This policy allows non-administrators to install printer drivers when connecting a shared network printer (the printer’s driver downloaded from the print-server host). Then you can set the policy value to Disable, any unprivileged user can install a printer driver as a part of a shared printer connection to a computer. However, this policy does not allow downloading and installing an untrusted (not-signed) printer driver.

    The next step is to allow the user to install the printer drivers via GPO. In this case, we are interested in the policy Allow non-administrators to install drivers for these device setup classes in the GPO section Computer Configuration > Policies > Administrative Templates > System > Driver Installation.

    Enable the policy and specify the device classes that users should be allowed to install. Click the Show button and in the appeared window add two lines with device class GUID corresponding to printers:

    Class = Printer {4658ee7e-f050-11d1-b6bd-00c04fa372a7};
    Class = PNPPrinters {4d36e979-e325-11ce-bfc1-08002be10318}.
    You can find a full list of the device class GUIDs in Windows here.

    When you enable this policy, members of the local Users group can install a new device driver for any device that matches the specified device classes.

    Note. You can enable this policy through the registry using the command:

    reg add "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DriverInstall\Restrictions" /v AllowUserDeviceClasses /t REG_DWORD/d 1 /f
    You can find the list of allowed to install device GUIDs under the registry key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DriverInstall\Restrictions\AllowUserDeviceClasses.

    Now save the policy.

    I hope this answers your question.


    --If the reply is helpful, please Upvote and Accept as answer--

  3. Alan Morris 1,041 Reputation points

    @Syed Fahad Ali

    This all depends if you prevent the client from connecting to any shared printers outside of your control. If you secure the print server environment and allow only connections to the shares you provide, then this will mitigate the issue.

    Moving to the Type 4 driver model ensures no binaries are copied from the server to the client and does not require the above configurations.

    The client experience may feel degraded but they will be able to get squiggly lines on a piece of paper.


    0 comments No comments

  4. Syed Fahad Ali 6 Reputation points

    Thank you for your response.

    So its clear that if the printers are under control then this will mitigate the vulnerability if we are giving the rights of printer installation to end user/s.

    0 comments No comments

  5. Syed Fahad Ali 6 Reputation points

    Both group policies have been applied but still user cant install the printer driver. Please advise.

    0 comments No comments