Event Id | 699 |
Source | Microsoft-Windows-ADFS |
Description | The LSAuthenticationObject method LogonClient was called, but the Federation Service trust policy does not define any account stores. User Action If the Federation Service is intended to authenticate users, configure at least one account store. Otherwise, consider replacing clientlogon.aspx with a static page that indicates that logon is not supported. |
Event Information | According to Microsoft : Cause : This event is logged when the LSAuthenticationObject method LogonClient was called, but the Federation Service trust policy does not define any account stores. Resolution : Configure at least one account store If the Federation Service is intended to authenticate users, use the following procedure to configure at least one account store. Otherwise, consider replacing clientlogon.aspx with a static page that indicates that logon is not supported. Depending on how you configured AD FS authentication, you can find the appropriate clientlogon.aspx page in either the %systemdrive%\Windows\ADFS\sts\ls, %systemdrive%\Windows\ADFS\sts\ls\auth\integrated, or %systemdrive%\Windows\ADFS\sts\ls\auth\sslclient directory. To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority. To add an account store to the Federation Service:
Verify that you can access the Active Directory Federation Services (AD FS)-enabled application from a client browser and that the resource can be accessed with the appropriate authorization. |
Reference Links | Event ID 699 from Source Microsoft-Windows-ADFS |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.