What’s new – Event Monitoring v0.7

This release was one of the early quality passes on Event Monitoring: some code was cleaned up, a few health checks were added, and a couple of rough edges in configuration handling became clearer. If you were already using the scripts, v0.7 was mainly about making the reporting flow more predictable.

Please notice this article contains partial historical information and may not reflect everything that the module can do now. For source code, downloads, and the broader current picture, refer to the dedicated PSWinReporting page.

What changed in v0.7

There were several additions and cleanups in this version, including:

• fixed display issues related to Write-Color inconsistencies
• small code optimizations
• better error handling for event listing on older systems
• a new Supported column
• moving Test-Prerequisite from the config file into the library

That last change is the most important one for anyone updating an existing configuration.

Config change you actually need to make

Because Test-Prerequisite was moved into the library, this:

Has to be replaced with this:

In practice, you just remove the old If check from the config file. If you leave it there, nothing catastrophic should happen, but you will see a duplicate prerequisite check at the beginning.

Known issues at the time

At that point there were still a few unfinished pieces:

• IncludeLogonEvents was not working correctly
• IncludeDomainControllersReboots returned more information than needed
• AsCSV was not working
• KeepReports was not working yet and reports stayed saved by default

Why this post is still useful

Older release notes like this are mostly helpful when you are trying to understand how the module evolved, why an older config file behaves differently, or why a screenshot from a previous version does not match the current project documentation.