thub.users.profile.tabs.comments.personalized


Thanks for the response. I have been dealing with things other than this recently and have forgotten some of the details of things that I have read and tried.

Does this allow for Printer Deployment per User via GPO to process and load printer for the individual users?

Also if I am not mistaken doing this basically negates the Print Nightmare fix and opens you right back up to the same vulnerabilities.

I have not found anything posted anywhere that actually fixes the issue short of giving a user admin permissions or roll back updates. Here is one of the better discussions that I have found regarding the whole Print Nightmare security fix that created this whole mess to start with.
https://docs.microsoft.com/en-us/answers/questions/517533/pint-server-and-print-nightmare-update.html

I have tried just about everything discussed to try and remedy this issue but none of them have work for me so far.

What I have seen is that if the user had the printer installed by GPO prior to the update there are no issues with printing. It is only new deployments that do not load from GPO. Now if the User is and Administrator all printers load without issue.

Microsoft needs to come out with some clarification on how to get Domain Users to process the Deployed Printers GPO since they seem to have made it and Admin only function with this latest update.

I wish I could change to deployment by machine. Unfortunately I have 50+ printers (BW Lasers, Color Lasers, Wide format printers, label printers, and MFPs) across 4 locations and users are constantly moving around. I have some spoiled users that like having their printers no matter where they are in the company and if they don't you would think the world is coming to an end.

The stranger part is that this has caused Print Servers that have not had the updates to not deploy via GPO. Most recent print server I installed was 2019 and fully updated with 9/21 rollup. This is when My problem started and it was only that server at first. With in a few hours all my print servers stopped deploying printers from GPO. My other 3 print servers have not had the 9/21 update. 2 of them (1 - 2012R2 and 1 - 2019) have had the 8/21 update and 1 of them (1- 2012R2) has only had 7/21 update.

That single server having the 9/21 update broke all the rest in a few hours.

Microsoft needs to stop passing the buck and admit the screwed everyone that uses print servers and come up with a real fix for the issue.

I don't believe it has to do with the Workstations. I have workstations that haven't been updated in a year that printer deployment via GPO now does work. It doesn't seem to matter if it is 1908 that hasn't been updated in a year or if it is 21h2 that is fully updated.

The stranger part is that this has caused Print Servers that have not had the updates to not deploy via GPO. Most recent print server I installed was 2019 and fully updated with 9/21 rollup. This is when My problem started and it was only that server at first. With in a few hours all my print servers stopped deploying printers from GPO. My other 3 print servers have not had the 9/21 update. 2 of them (1 - 2012R2 and 1 - 2019) have had the 8/21 update and 1 of them (1- 2012R2) has only had 7/21 update.

That single server having the 9/21 update broke all the rest in a few hours.

Microsoft needs to stop passing the buck and admit the screwed everyone that uses print servers and come up with a real fix for the issue.

I haver applied the registry change to 2 of my print servers and printers still will not load from GPO for Domain Users. Does the registry change need to be applied on every print server in the Domain before it will allow Domain Users to get there printers deployed via GPO?

Printers are Deployed via GPO to users not machines in Domain.

Thank you for the response.

Article does nothing for me. Already been through the gambit of fixes already. The problem really appears to rest in the permissions realm. All my admins get every printer from GPO even now. Normal users do not. They did before the security change. Registry entries have not worked. Rolling back updates is only good till the next rollup installs.

This is Microsoft screwed up. They broke Deployment of Printers via GPO for normal Domain Users.

What are we suppose to do now?

I am experiencing a similar issue but it has to do with Deployment of Printers from GPO. If a user had already gotten their prints from GPO they are present and work. If users need 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.

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 every test this with GPO deployment of printers before dumping it out there?

Anyone else seeing this behavior? Has anyone fixed this behavior?