Exchange Reporter: New version with support for Exchange 2019

After a long time, I have once again revised the Exchange Reporter and corrected various errors. Most modules now also work with Exchange 2019.

The following fixes and new functions are now included in version 3.4:

• New functions
  • Support for Server 2016 (AD) and Exchange 2019
• Bug fixes
  • Link in the PSPKI documentation corrected
  • DBReport: Display of free disk space in the database (thanks to Anton)
  • MBXReport: Error message for mailboxes that have never been logged into corrected (thanks to Florian)
  • UpdateReport: Fixed an error when searching for updates when Exchange Reporter is running on an Exchange Server
  • UpdateReport: Connection to the Exchange Reporter Update Check now requires at least TLS1.0
  • DGReport: Error message when determining distribution lists fixed
  • CAReport: Module is now canceled if the PSPKI module is not found
  • SSLLabsReport: At least TLS1.0 is now required for the connection to the SSLLabs API

If you are not yet familiar with the Exchange Reporter, you can find an example screenshot here:

A description of Exchange Reporter, the functions and the current download can be found here:

• Exchange Reporter Page

There is also an option on the page to report problems with the Exchange Reporter. I am now trying to work on updates more regularly again.

Note: When updating an existing Exchange Reporter installation, the settings.ini can be adopted. However, I had noticed that the SSLLabsReport module (Qualys SSLLabs Server Test) was not previously included in the settings.ini. I have corrected this in the current version. If you want to use the module, you can also add it manually to the existing settings.ini.

I have also updated the manual to the latest version. If you encounter errors or problems with Exchange Reporter, it is worth taking a look at the manual. Some Reporter modules require certain PowerShell modules to be installed first. These PowerShell modules and the download URLs can be found in the manual.

The question also arose as to whether Exchange Reporter could be managed on GitHub. If there are people who are actively involved in the further development, this would definitely be an option. If you are interested, please send an email using the contact form.