Mac Client – – Certificate and More Volumes in Preference Pane

In addition to update, this release includes:


  • APFS and ZFS volumes are listed for easy configuration of Presence and Capacity monitoring


  • Installation packages are signed with updated installer certificates, expiring 2025

About Existing Installers

Watchman Monitoring regularly updates installers, and recommends that older installers are replaced.

This is typically not a requirement, as agents will auto-update even if an old installation package is used. Installers published before June 2020 are slated to expire June 10th, and will need to be replaced.

What to do I need to do?

Please visit your Installers page and re-download your installers.

If you are using Group-Specific installers, they can be downloaded from each Group’s page as needed.

Updated Betas

Splashtop Business will generate an integration button for non-business versions of Splashtop. The link created will not work. A fix to exclude links for non-business versions of Splashtop is in development.

The beta of Retrospect Client for Mac is available. All subscribers who have requested access will have the beta automatically deployed to their monitored computers.

You can request the beta here.

Keep an eye on our Community Forum for news of incremental changes, and we will keep emailing major release notes.

About the Timing of macOS Installer Notarization

At this time, users are able to download and attempt to open the installer before the process is complete, and may see the following warning dialog:

macOS Catalina notarization warning Example Dialog
If the user attempts to install again a few minutes later, installation will complete, since that same package is known by Apple to be notarized.

We are aware of the issue. We are working to add additional checks to prevent download of enrollment code installers until Apple has completed notarization.

Of note, scripted macOS installation does require notarization and will not display the dialog or warnings mentioned above.

Additionally, deployment of our installation package via MDM will work as expected.