Forum Discussion
Server 2016 Domain member server Policy in effect prevents connecting to print queue
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.