According to the KB that shouldn’t happen. One small caveat though: I can confirm this problem also affects May rollup patched Windows 10 machines RDP-ing into April rollup patched servers. I agree with you that Microsoft has provided ample warning of this and in my personal opinion there indeed isn’t a lot wrong with the way they have been securing this protocol in the “careful, documented, multi-month rollout of a mitigation” way as you have described it. In this case, I think Microsoft deserves credit for FIXING a security bug with a careful, documented, multi-month rollout of a mitigation. I hate it when Microsoft releases bugs that affect millions. ![]() ![]() Later in April they will make it so that an error message will occur when you attempt to remote from a patched machine to an unpatched machine, and then later in May (tentative at this time) the default will be to enforce that remoting from a patched machine to an unpatched machine will not work.” “Initially in March, they are rolling out the new protocol. Susan gave a heads-up on this in March: : You can use group policy or registry to change it back to Vulnerable until you get your systems patched. As promised, the May update changed the default to Mitigated. This is a planned tightening of security over three months. ![]() I suspect unpatched servers and/or clients. I don’t know where the original post is so don’t know the context.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |