Datto RMM 15.1.1 interim release notes

Platform Date From (UTC) To (UTC) Duration
Syrah (APAC) Thursday, September 24, 2026 14:00 16:00 2 hrs
Vidal (US East) Monday, September 28, 2026 09:00 11:00 2 hrs
Concord (US East) Wednesday, September 30, 2026 09:00 11:00 2 hrs
Merlot (EU2) Wednesday, September 30, 2026 19:00 20:00 1 hr
Zinfandel (US West) Thursday, October 1, 2026 09:00 11:00 2 hrs
Pinotage (EU1) Thursday, October 1, 2026 19:00 20:00 1 hr

NOTE  *The schedule is subject to change. Check the Status page for regular updates. Any changes made to the original schedule are denoted in red.

Datto RMM Agent versions upon release deployment:
  • Windows/Linux: 12357
  • macOS: 11994

Enhancement

Web Remote 2.0: WebRTC DNS fallback to public DNS

Web Remote sessions now fall back to public DNS when a target device cannot resolve the WebRTC server through its local DNS configuration. This completes the connection-fallback chain across all transport types, allowing devices with DNS issues to establish a video session that would previously fail.

Fixes

Web Remote 2.0

  • Web Remote sessions now open with the target device's primary monitor selected by default instead of spanning all monitors. This aligns the new video protocol's startup behavior with the existing desktop duplication protocol.
  • Moving the mouse cursor is now smooth and predictable after the target device's display resolution is changed during a Web Remote session. Previously, changing the resolution caused the cursor to jump or become uncontrollable for the remainder of the session.
  • Memory handling and initialization issues in the new video protocol, which could cause crashes or trigger continuous reconnect loops during active sessions, have been resolved.
  • When a target device loses its internet connection during a Web Remote session, the technician now sees a reconnecting screen immediately instead of a static black screen.

Automation & Jobs

  • Copying a quick job created from a site-filtered list spanning multiple pages no longer fails to resolve and retain the full list of targeted devices.
  • An issue where adding or updating ComStore components failed with a Component update failure: Unable to update Comstore component error has been resolved. Components can now be added and updated as expected.
  • Cooper Bot run status now updates to the correct completed state after all downstream actions finish. Previously, the run status remained stuck on Running indefinitely even after the job and any associated ticket creation completed successfully.

Agent & Integrations

  • The maximum byte buffer for Microsoft 365 integration requests has been increased and made configurable, preventing buffer overflow and out-of-memory exceptions when synchronizing larger tenant payloads.
  • The Download Agent Logs action in the UI now correctly includes all historical, archived AEMAgent log files alongside the active log file.