I'm migrating printer deployments on Windows Server 2022 from the older Deployed Printers policy to Group Policy Preferences. The original queues were configured under both Computer Configuration and User Configuration at Policies > Windows Settings > Deployed Printers. After removing the printers from the policy, they continue to appear on client machines, and GPRESULT still shows them being applied.
I have already tried removing the GPO, deleting printer-connection registry entries, configuring GPP to delete the printers, removing and re-adding the queues, and deleting them from Print Management. A GPP cleanup action also reports "Access is denied" in Event Viewer after running gpupdate /force. Point and Print Restrictions are configured so clients can use approved print servers and drivers.
This worked with an older Windows Server 2012 R2 print server, but the issue began after the PrintNightmare-era updates and the move to a Windows Server 2022 print server. Has anyone successfully removed these orphaned legacy printer deployments or completed this migration?
1 Answer
One possible fix is to edit the affected policy from a domain controller running an older Windows Server version that still exposes the full legacy Deployed Printers interface. In one case, opening the policy on a Server 2019 domain controller and deleting the printer entries there allowed the old deployments to be removed. If you have a temporary compatible domain controller available, it may be worth trying. The forest functional level could also matter, so check that before making changes.
Thanks. I’ve already tried opening the policy from multiple domain controllers and working from the print server, but the old printer entries are still being applied.