Revision to Incorrect logon attempts sent to AD

This commit is contained in:
John Tobin 2017-07-27 14:03:04 -07:00
parent 1e9c74b57f
commit 4a3d52fb68

View File

@ -23,9 +23,35 @@ The following known issues have been fixed by servicing releases made available
This issue can potentially lead to unexpected account lockouts. See also Microsoft® Knowledge Base articles [KB4015219](https://support.microsoft.com/help/4015219/windows-10-update-kb4015219) and [KB4015221](https://support.microsoft.com/help/4015221/windows-10-update-kb4015221) This issue can potentially lead to unexpected account lockouts. See also Microsoft® Knowledge Base articles [KB4015219](https://support.microsoft.com/help/4015219/windows-10-update-kb4015219) and [KB4015221](https://support.microsoft.com/help/4015221/windows-10-update-kb4015221)
- [KB4033236 Two incorrect logon attempts sent to Active Directory after Credential Guard installed on Windows 10](https://support.microsoft.com/help/4033236/two-incorrect-logon-attempts-sent-to-active-directory-after-credential?preview) - [KB4033236 Two incorrect logon attempts sent to Active Directory after Credential Guard installed on Windows 10](https://support.microsoft.com/help/4033236/two-incorrect-logon-attempts-sent-to-active-directory-after-credential?preview)
See also Microsoft Knowledge Base article [KB4015217](https://internal.support.services.microsoft.com/help/4015217/windows-10-update-kb4015217) This issue can potentially lead to unexpected account lockouts. The issue was fixed in servicing updates for each of the following operating systems:
- Windows 10 Version 1607 and Windows Server 2016:
[KB4015217 (OS Build 14393.1066 and 14393.1083)](https://support.microsoft.com/en-us/help/4015217)
- Windows 10 Version 1511: [KB4015219 (OS Build 10586.873)](https://support.microsoft.com/en-us/help/4015219)
- Windows 10 Version 1507: [KB4015221 (OS Build 10240.17354)](https://support.microsoft.com/en-us/help/4015221)
The following issue affects Cisco AnyConnect Secure Mobility Client: The following issue affects Cisco AnyConnect Secure Mobility Client: