Blog – Watchman Monitoring

Mac Client 7.1.7.712 — CrashPlan and P5 reliability fixes

May 26, 2026

Watchman Monitoring is happy to announce the release of agent 7.1.7.712 for macOS. It will automatically roll out to all Computers next Tuesday, June 2 2026. Bug Fixes CrashPlan: more reliable destination discovery For years, the CrashPlan plugin has discovered configured destinations by parsing the DESTINATIONS section of CrashPlan’s app.log. That format has shifted repeatedly across CrashPlan 8.2, 11.0, 11.5, and 11.6, and routine log rotation can strip the header the parser needs. The visible symptom has been machines reporting “No CrashPlan Destinations reported” while backups were actually running normally. This release adds a filesystem fallback: when app.log yields zero destinations, the plugin scans CrashPlan’s cache directory for GUID-named subdirectories with a cp.properties file — the same authoritative records the plugin already uses for per-destination data. The fallback only activates when the log-based lookup comes up empty, so installs whose app.log still parses cleanly behave exactly as before. If your CrashPlan destinations have been silently dropping out of the report, this should bring them back. P5 plugins: no more spurious tracebacks The check_p5_devices and check_p5_jobs plugins could crash on otherwise-healthy machines when nsdchat returned empty output — common on hosts where P5 is installed but not yet configured, or during ...

Mac Client

Mac Client 7.1.706. – Munki v7 Support

May 8, 2026

Watchman Monitoring is happy to announce the release of agent 7.1.7.706 for macOS. Munki Improvements Munki v7 Support – The Munki plugin now supports Munki v7 and will properly display it in the Dashboard. Bug Fix – Munki plugin no longer crashes when ManagedInstallReport.plist records EndTime as a date. Affected hosted could go silent on Munki reporting. This new version will roll out to everyone on Tuesday May 12 2026. If you’d like to receive this version before then, please let us know and we’re happy to help. What’s Next More bug fixes for various plugins A brand new MDM plugin Better duplicate Computer detection Revamped Webhook integration

Dashboard

Zendesk Integration Update: Migrate to Oauth and fix two way integration

May 8, 2026

We are happy to announce that we have upgraded our Zendesk integration. We have added support for Oauth client based authentication and behind-the-scene changes to how tickets are updated. If you use Watchman Monitoring’s Zendesk integration , here’s what’s changing and what you should do about it. Connect with with OAuth The biggest change is that can connect to Zendesk using OAuth instead of the legacy permanent API token. When you open the Zendesk integration settings, you’ll see a new Authentication Method toggle with two options. The new (recommended) one, OAuth, lets you connect by entering an OAuth Client ID and Secret from your Zendesk account and clicking Connect with OAuth. You’ll be bounced over to Zendesk to authorize, then dropped back into Watchman Monitoring once you approve. The existing API Token flow (admin email plus token) is still available for backward compatibility. Once OAuth is connected, you’ll see an OAuth Connected indicator along with the token’s expiration date. You don’t need to do anything when that date arrives. Watchman Monitoring refreshes the token automatically before it expires. Why does this matter? Zendesk is steadily pushing its platform toward OAuth as the modern, secure authentication standard. As of February 2, ...

News

Windows Client 1.6.2.4 – Volumes and BitLocker Plugin fixes, Cisco MAC addresses, and more

April 28, 2026

Rolling out to all subscribers starting Tuesday, May 5, 2026 (1400 UTC / 9:00 AM Central) Auto-update connectivity fix Earlier this year our load balancer infrastructure dropped support for TLS 1.0 and 1.1 in line with current security standards. The Monitoring Client’s auto-updater (a third-party component compiled against .NET 4.0) defaulted to those older protocols and could no longer download update manifests on systems without certain Windows registry hardening applied. 1.6.2.4 ships an update.exe.config and self-healing logic in the agent so the updater always negotiates TLS 1.2. After this release lands, future updates will go through cleanly even if your endpoints don’t have SchUseStrongCrypto set in the registry. Improved network adapter detection The MAC blocklist used by the agent to identify physical vs. virtual/ephemeral adapters has been expanded to include: Cisco AnyConnect VPN virtual adapters Cisco Network Software virtual adapters If you’ve seen flaky beacon/IP-address reports on machines that frequently connect through Cisco VPN, those should stabilize. Volumes and BitLocker plugin crash fix Both plugins read the system’s drive list from a registry JSON blob. When that JSON ended up malformed on certain endpoints (rare but reproducible after some Windows feature updates), the plugins would crash and produce no output. The plugins ...

Mac Client

Mac Client 7.1.6.101 A Series Chip Support

April 22, 2026

Watchman Monitoring is happy to announce the release of agent 7.1.6.101 for macOS. Apple A Series Support Apple A18 / A18 Pro / A19 / A19 Pro — added processor-speed and unified-memory entries (A18: 4.04 GHz / 7500 MHz, A18 Pro: 4.04 GHz / 8533 MHz, A19: 4.26 GHz / 8533 MHz, A19 Pro: 4.26 GHz / 9600 MHz). Apple M5 chip family — check_cpu now reports M5/M5 Pro/M5 Max as 4.6 GHz, and check_ram reports their unified memory as LPDDR5X-9600 The unified-memory detection branch now recognizes Apple A-prefixed chip names alongside Apple M, so any Apple-silicon device that surfaces with an A-series identifier will report its memory configuration correctly instead of falling through to the generic path. What’s Next We have a ton of macOS agent plugin updates coming in the next week. If you have any requests for plugin fixes or new plugins that you’d like created, please let us know!

ChromeOS Monitoring

New Releases: ChromeOS Monitoring and HaloPSA Integration

March 16, 2026

We have two major features to announce today. Both ChromeOS monitoring and HaloPSA have been running in early access for the past few months, and we’re now making them available to all Watchman Monitoring customers. ChromeOS Monitoring Back in September we sent out a survey asking what Watchman Monitoring users wanted us to build. ChromeOS Monitoring was one of the top requests, and now it’s out! ChromeOS monitoring works through a Google Workspace integration. Once connected, Watchman Monitoring syncs your ChromeOS devices and displays them alongside the rest of your Computers. What you get: Chromebook devices appear in your Computers list, grouped however you organize your other machines Device details pulled from Google Workspace: serial number, model, OS version, enrollment status, last sync time, and more A dedicated sync status indicator so you can see at a glance whether the integration is healthy Email alerts if the sync fails or your Google Workspace credentials need attention An initial set of plugins for monitoring ChromeOS devices. We would love your feedback here on what Plugins you’d like added/changed! How to get started: Navigate to Installers → ChromeOS in your dashboard. You’ll need a Google Workspace service account with read-only access to ...