Replies

anonymous wrote:

Is there a fix for this? I connect via RDC to one of my servers and now I can’t.

Have to update the server.

mcbsys wrote:

I don’t know where the original @geekdiver post is so don’t know the context. I suspect unpatched servers and/or clients. This is a planned tightening of security over three months. As promised, the May update changed the default to Mitigated. You can use group policy or registry to change it back to Vulnerable until you get your systems patched. Susan gave a heads-up on this in March: https://www.askwoody.com/2018/patch-lady-tracking-some-post-release-issues/: “Initially in March, they are rolling out the new protocol. 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.” I hate it when Microsoft releases bugs that affect millions. In this case, I think Microsoft deserves credit for FIXING a security bug with a careful, documented, multi-month rollout of a mitigation.

Definitely, agree they deserve some kudos for fixing the security hole but with how messy patches have been this first quarter of the year it does add to issues.