Mapping network printer fails with "A policy is in effect on your computer which prevents you from connecting to this printer queue. Please contact your system administrator."

Mik Op 136 Reputation points
2021-09-23T07:51:40.463+00:00

Seems like a bug in recent windows server update or something..

Adding network shared printer fails on Windows Server 2012 R2. Driver downloads and installs ok, but finishing the task fails with "A policy is in effect on your computer which prevents you from connecting to this printer queue. Please contact your system administrator.". Tried all possible GPO settings about point & print restrictions etc. Even under administrator account with UAC disabled. Affects multiple Windows Servers 2012-2016.

Only option to connect the printer is to manually add registry

[HKEY_CURRENT_USER\Printers\Connections\,,sharingcomputername,sharename]

"GuidPrinter"="{68499076-F37A-4089-BCE7-3B4C48416ADA}"

"Server"="\\sharingcomputername"

"Provider"="win32spl.dll"

"LocalConnection"=dword:00000001

Anyone has a better sollution?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,170 questions
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
641 questions
Accepted answer
  1. Mik Op 136 Reputation points
    2021-09-24T16:37:13.393+00:00

    Adding printers connections to registry is not a solution - even though printers got mapped, printing fails with "The system cannot find the file specified" message.
    Setting RestrictDriverInstallationToAdministrators to 0 or playing with Point and Print Restrictions does not help.
    The only option is to uninstall KB5005613 (Windows Server 2012 R2).

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-09-28T16:05:01.737+00:00

    In my testing I added a new printer that uses the same port as the existing one and this new printer does not suffer the same issue. So we're going to leave the existing one and append an "A" to the end of the new printer. So existing employees who are printing without any issue can do so, while those who cannot will install the "A" printer. At this point we are up to two different printers having this issue...different models, all <cough> HP, different drivers, different print servers, etc.

    Another work around could be to install this ONE printer as a local TCP/IP printer.

    1 person found this answer helpful.
    0 comments
  2. Limitless Technology 39,366 Reputation points
    2021-09-23T10:32:25.55+00:00

    Hello @Mik Op ,

    This is due to recent updates to protect from the PrintNightmare exploit. Only users with Admin rights would be able to see the printer because the would have access to the drivers. One workaround is to install manually the printer drivers locally, and this will allow any users on the computer to map the device. Otherwise Microsoft released an article regarding the printer and printer driver management post patching:

    https://support.microsoft.com/en-us/topic/kb5005652-manage-new-point-and-print-default-driver-installation-behavior-cve-2021-34481-873642bf-2634-49c5-a23b-6d8e9a302872

    Hope it helps,

    ---------------------------------------------------------------------------------------------------------------------------

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

  3. Mik Op 136 Reputation points
    2021-09-23T10:56:33.683+00:00

    Hi, I don't think that's the case because 1) I have tried with admin rights 2) driver is already installed.

    0 comments