Add AD bad logon attempts known issue

This commit is contained in:
John Tobin
2017-07-18 17:12:41 -07:00
parent 442aa65aac
commit d821b489f3

View File

@ -17,12 +17,16 @@ author: brianlic-msft
Credential Guard has certain application requirements. Credential Guard blocks specific authentication capabilities. Therefore applications that require such capabilities will not function when Credential Guard is enabled. For further information, see [Application requirements](https://docs.microsoft.com/en-us/windows/access-protection/credential-guard/credential-guard-requirements#application-requirements).
The following known issue has been fixed by servicing releases made available in the Cumulative Security Updates for April 2017:
The following known issues have been fixed by servicing releases made available in the Cumulative Security Updates for April 2017:
- [KB4015217 Credential Guard generates double bad password count on Active Directory domain-joined Windows 10 machines](https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217)
This issue can potentially lead to unexpected account lockouts. See also Microsoft® Knowledge Base articles [KB4015219](https://support.microsoft.com/en-us/help/4015219/windows-10-update-kb4015219) and
[KB4015221](https://support.microsoft.com/en-us/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/en-us/help/4015219/windows-10-update-kb4015219) and [KB4015221](https://support.microsoft.com/en-us/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/en-us/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/en-us/help/4015217/windows-10-update-kb4015217)
The following issue affects Cisco AnyConnect Secure Mobility Client: