1. Running the Report:

    • The 'Users with Invalid Passwords' report is resource-intensive and can strain the reporting servers if executed multiple times. To mitigate this, it is recommended to:
      • Designate a single administrator to run the report for the entire district.
      • Set the Start Date and End Date to a broad range to ensure comprehensive data capture.
      • Schedule the report to run during off-peak hours to minimize system load.
      • Avoid repeatedly clicking to run the report, as it may appear unresponsive due to processing time.
      • Once initiated, you can navigate away from the report and later retrieve it from the Reports History.
  2. Locating the Report:

    • To locate the report, navigate to the Report History section and verify if the report is available for selection.
    • Ensure the Start Date and End Date are set to a wide range to capture the most recent data.


  3. Additional Recommendations:

    • Prior to running the report again, thoroughly review the existing report to identify and address invalid passwords.
    • The indication "Old hashing algorithm without salt" suggests that the user has not updated their password for an extended period. For active accounts, prompt users to change their passwords. For long-disabled accounts, consider removing them. If retaining disabled accounts, update the passwords and/or enforce a password change.