Nothing jumped out at me here regarding this, so I figured I'd throw a thread together.
Me and my partners in crime spent the last four hours trying to dissect Microsoft's patch level system for the fix to this SMB exploit, and came to the following list of KBs and stuff, updated as of today (15MAY2017).
Win7: KB4012212
Win10 pre-1511: KB4019474
Win10 1511: KB4019473
Win10 1607: KB4019472
Win10 1703: Secured in-place.
All of the above have superseded previous updates. If you're like me with WSUS running through SCCM, you should see those. If you're like my cohorts running WSUS standalone, you might see the previously superseded patches and for some reason missed the 09MAY downloads, for unknown reasons (still troubleshooting that one).
I'd love to give a punch in the face to whomever in MS came up with this new system.
Me and my partners in crime spent the last four hours trying to dissect Microsoft's patch level system for the fix to this SMB exploit, and came to the following list of KBs and stuff, updated as of today (15MAY2017).
Win7: KB4012212
Win10 pre-1511: KB4019474
Win10 1511: KB4019473
Win10 1607: KB4019472
Win10 1703: Secured in-place.
All of the above have superseded previous updates. If you're like me with WSUS running through SCCM, you should see those. If you're like my cohorts running WSUS standalone, you might see the previously superseded patches and for some reason missed the 09MAY downloads, for unknown reasons (still troubleshooting that one).
I'd love to give a punch in the face to whomever in MS came up with this new system.
Facebook
Twitter