Knowledge Base

Both affected (perpetual) and subscription licenses use the same model to count licenses — the count is based on the number of enabled Active Directory user accounts that have a Specops Password Policy GPO applied to them in Active Directory. Specops Password Policy regularly updates a record of how many licenses have been consumed. The...

After the migration of SYSVOL replication from FRS to DFSR, there will be path changes in SYSVOL that will prevent the Sentinel component of Password Policy from functioning properly.  As Sentinel is responsible for enforcing Specops password settings, password changes would then be processed only by the native Microsoft password settings in Default Domain Policy...

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...

This may happen when you upgrade from an older version to 7.11 and import the new Continuous Scan license file. To fix: Launch Active Directory Users and Computers and ensure these 2 options are checked: Then navigate under the System>Specops>Password Policy folder and delete the licensing folder: From there, launch Specops Password Policy domain administration...

This is useful if you are applying it to a wide scope of a domain, but rather than exclude an OU, you can choose to exclude by a Security group. If you have a security group in mind you can use that one or create one in Active Directory Users and Computes. You will then...