We had the same issue, until we found this:
https://community.spiceworks.com/topic/277019-printer-deployment-via-group-policy-not-working
Windows failed to apply the Deployed Printer Connections settings.
I am experiencing an issue with Deployment of Printers from GPO. This just started last week after I replaced existing 2012r2 DC and 2012R2 Print Server with New 2019 DC and Print Server If a user had already gotten their printers from GPO they are present and work. If a user needs printers to load from GPO they will not. When we run gpupdate /force we get this "Windows failed to apply the Deployed Printer Connections settings. Deployed Printer Connections settings might have its own log file. Please click on the "More information" link."
All other GPOs are processing and working properly.
I have 4 other DCs (3 - 2012r2 and 1 -2019) and 3 other Print Servers (2 - 2012R2 and 1 - 2019) Workstations are all Win10 assorted flavors (1908 through 21H2)
Since I list all printers in the Directory. I can still install the printers manually from the Printer Servers through "Add Printer" and they install without issue even for none admin users.
Microsoft has really made a mess with this recent security update. Did they ever test this with GPO deployment of printers before dumping it out there?
Anyone else seeing this behavior? Has anyone fixed this behavior?
18 answers
Sort by: Most helpful
-
dn 11 Reputation points
2021-12-03T12:49:01.927+00:00 -
Gary Longstaff 6 Reputation points
2022-04-14T11:32:32.227+00:00 Okay so Microsoft as usual 'passed the buck' to others. We have all had to look at creating a Reg policy for Point and Print
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint
value name="RestrictDriverInstallationToAdministrators"
type=REG_DWORD
value=0After the most recent updates MS forced the restriction and this still impacts older printer drivers even after the reg hack. After plenty of head scratching and investigations: 1.You must have Type 3 drivers 2. If you have older packages NOT classed as packaged it appears MS still doesn't allow them without issues: using kix script-even if you have disabled the Point and Print registry, the user is still prompted with the 'Trust this printer and install option', to which you need to supply and admin account . Once installed all fine the next time around. IF using GPO Targeting the printer configured in GPO doesn't appear in the printer options list when trying to print. Found the following in the event log of the client machine [even though the driver does exist on the server]
1The column where the Package column have 'false' against them will likely be issues:
I had been scratching my head for days testing and wondering why the Brother HL-5450DN worked but not the Brother HL-L8250CDN as there just didn't appear to be a reason for it, well there is thanks to MS. :( So, to sum up: 1. You will require new drivers from the manufacturer’s website. 2. look at ways to possibly build a 'package' to be deployed by systems like SCCM.Just another shambles!
-
Limitless Technology 37,786 Reputation points2021-09-28T15:00:27.29+00:00 Hello @DanHoffa ,
Thank you for your question.
Based on the description of your problem, I recommend that you take a look at the topic below, which has a problem similar to yours and may help you fix the problem:
------------------------------------------------------------------------------------------------------------------------
If the answer is helpful, please vote positively and accept as an answer.
-
Alex Alexander 1 Reputation point
2021-09-28T15:38:51.193+00:00 Yes, the same issue. Exact same.
When you use RSOP.msc all it says is "status failed" "Deployed Printer Connections failed due to the error listed below."
They've done something within the last 3 weeks.
-
Maciej Rubin 1 Reputation point
2021-09-28T21:14:23.233+00:00 exactly the same problem in my environment.