Forum Discussion
GeekNaHalf patching caused quite the commotion for me this morning. I ended up rolling back KB5005573 and restarted the print servers. It would appear that this has been long in the process according to this link: https://support.microsoft.com/en-us/topic/managing-deployment-of-printer-rpc-binding-changes-for-cve-2021-1678-kb4599464-12a69652-30b9-3d61-d9f7-7201623a8b25
Unfortunately with everyone and anyone making noise about the issue... I did not feel I had enough time to research the root cause. That article would have been nice to be made aware of prior to patching this last weekend.
I am currently in the testing phase on that article to see if it works or not. I suspect it will work, but I'm not sure why Microsoft doesn't just address the problem rather than disable a feature that everyone seems to use.
- GeekNaHalfSep 22, 2021Copper ContributorGlad it helped. I am also going to try and uninstall all printers and drivers from the DC, and then reinstall with only v4 drivers, re-apply the patch and see if users can still print. Hopefully that will correct the problems for W10 users at least. W7 clients are screwed regardless I think.
If anyone hears of better solution(s), pls post.
RS