Breached Password Protection Complete scanning. The number of Email notifications sent are less then compromised passwords found.
After a Breached Password Protection Complete scanning the results are showing less email notifications sent then compromised passwords found.
Possible reasons for this
1. A users password has been caught as breached by the complete list in the past and the “User must change password during next logon” setting has been ticked on the user account in Active Directory. The user will not receive an email notification but will still be reported as using a compromised password. This can be checked and verified in the event viewer on the Specops Arbiter server, check for event ID 2016.
2. Another reason could be that the email attribute on a user account in Active Directory is missing an email address. To verify, check for event ID 1109 in the Specops event log on the scanning domain controller.
3. It could also be the case that the email notification setting isn’t ticked in the Specops Password Policy. The result will then be 0 Email notifications sent. If there are multiple Specops Password Policies configured and the setting isn’t ticked in all of them it could also lead to less email notifications sent then compromised passwords found.
