Forum Discussion

simp513's avatar
simp513
Copper Contributor
Nov 06, 2026

Server 2016 Domain member server Policy in effect prevents connecting to print queue

I have server 2016 member server (terminal server). Cannot add shared printers, get "A policy is in effect on your computer which prevents you from connecting to this print queue" I have check added changed the Point and print ect policies, no change...This is a new issue in the last few months but not sure exactly when it started.

5 Replies

  • maskwill's avatar
    maskwill
    Iron Contributor

    This is most likely related to Microsoft's PrintNightmare security changes, which tightened Point and Print restrictions.

     

    On Windows Server 2016, I'd check the following:

     

    1. Open Group Policy Editor (`gpedit.msc`).

    2. Navigate to Computer Configuration → Administrative Templates → Printers.

    3. Check Point and Print Restrictions and verify its configuration.

    4. Check Package Point and Print – Approved servers.

    5. Review Event Viewer → Applications and Services Logs → Microsoft → Windows → PrintService → Admin.

     

    Also verify that the latest printer drivers are installed on both the print server and terminal server.

     

    One important question: Are you connecting to printers hosted on another Windows print server, and does the same connection work from a Windows 10/11 workstation?

     

    That will help isolate whether this is a Server 2016 policy issue or a driver compatibility problem.

     

    Avoid disabling Point and Print security protections globally.

  • That update from you changes the picture — if you're signed in as a domain admin on the member server itself, the driver-installation restriction from the first reply isn't the thing blocking you, since that one is aimed at non-admin installs. The message you're seeing is the generic one Windows shows when the Point and Print policy itself refuses the connection, so the next thing to pin down is which policy is actually in effect on that server. Local edits in the Group Policy editor lose to domain Group Policy at the next refresh, so run gpresult /h gp.html from an elevated prompt and look at the Computer Configuration printer policies that are actually applied, rather than what the local editor shows — it's the step that decides everything else here, because a domain policy can quietly undo a local change.

     

    What you're looking for in that report is the pair of policies Microsoft's Group Policy printer documentation describes: Point and Print Restrictions, and Package Point and print - Approved servers. If Point and Print Restrictions is enabled with a list of servers, the client will only pull drivers from servers on that list, and if Package Point and print - Approved servers is enabled the same applies to packaged drivers. The other one to check is Only use Package Point and print — when that's on, only packaged drivers are allowed, so if the driver the print server is offering isn't a packaged driver, the connection is refused no matter who is signed in. You can see that on the print server in Print Management, in the driver list, where each driver shows whether it's packaged.

     

    If the server isn't on an approved list, adding it there in the domain policy, not locally, is the fix. And as a quick test of whether the driver download is the sticking point, install the same driver on the member server first through Print Management and then add the shared printer — if the driver is already in the local driver store, the connection doesn't need to download it from the server, and it should go through. If it still fails after that, the gpresult output will show which policy is still in the way, and that's the bit worth posting back.

  • simp513's avatar
    simp513
    Copper Contributor

    None of these help. I Am logged in as the domain admin and directly on a member server

  • That message can reflect an effective printer policy or a driver-installation restriction; changing several Point and Print settings does not establish which one is blocking this terminal server.

     

    I would not leave RestrictDriverInstallationToAdministrators at 0 as the routine fix. Microsoft explicitly warns that this makes devices vulnerable and that other mitigations are not equivalent to keeping it at 1. The same article says changing that registry value requires no restart.

     

    On the affected server, run gpresult /h gp.html from an elevated prompt and inspect the applied computer and user printer policies. Check Point and Print Restrictions and Package Point and Print – Approved servers against the actual print-server name used by the connection.

     

    Then test installation with administrator credentials while retaining the driver-installation restriction. If that fails too, collect the exact error, driver name/version, print-server name, and effective policy report. Those results distinguish a policy rejection from an elevation-only problem.

  • Hello simp513​ ,

    Since August 2021, Microsoft has defaulted to restricting only administrators from installing printer drivers. The key to resolving this issue lies in the RestrictDriverInstallationToAdministrators registry value, which may not be in the same location as the traditional Point and Print restrictions you modified.

    Please check or modify the following registry key on this Windows Server 2016 terminal server:

     

    Path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint

    Value name: RestrictDriverInstallationToAdministrators

    Type: REG_DWORD

    Value data: Set to 0

     

    Key point: Setting it to 0 allows non-admin users to install print drivers from the print server; if it is 1 or the value doesn't exist (default state), it will block installation. After making the change, it's recommended to restart the Print Spooler service or restart the server to ensure it takes effect.