September 22, 2024 - Version 9861
NOTE Datto EDR leverages a staggered release process. You'll receive an in-product notification when these updates are available to your instance.
Version information
| Endpoint Security Agent | Ransomware Agent | Rollback Agent | API |
|---|---|---|---|
|
3.11.5 |
1.3.0 |
1.2.2 |
5.0.0 |
New features
Viewing the policies assigned to each device
With the addition of device groups comes an easy way to see the specific policies assigned to each device. From the device details page for any device, you can now see what policies are running.
Device groups for security policies
To achieve more granular policy management, you can now assign policies to specific device groups within the organization or location.
Enhancements
- To reduce confusion about device statuses, the concept of monitored and unmonitored devices was removed with the introduction of Datto EDR-specific policy types. Now, devices will appear as Active instead of monitored.
- You can now assign policies to multiple organizations at the same time. From the Organizations page, select the desired organizations, then assign the applicable policies.
- Clicking the Alert count value for the organization, for the location, or on the device details page will now open a list of alerts filtered according to the respective alert count.
- New checks during the agent upgrade process are designed to detect issues that would prevent or disrupt agent updates.
- Agents integrated with Datto RMM now monitor and address multiple issues that could prevent an EDR agent installation from completing successfully.
Bug fixes
- An issue where host details were not visible in isolation response actions has been fixed.
- Some VSA 10-integrated users continued to see synced locations in Datto EDR that were deleted in VSA 10. The sync process has been updated to gracefully delete locations in EDR if the VSA 10 location is deleted.
NOTE To prevent disruptions, the location will remain in EDR if any devices are associated with the location.
Artifacts
agent.linux-amd64.1ecfa36421f0a7909fedac1a42a1df7dfb1e05d9a461716d7786d0e986b6424d.bin.gz agent.linux-arm64.9e75bbbe8702a351b85d9f6419589ed1d9b897af0ae17d23b0e376e57c85fb56.bin.gz agent.linux-x86.8c4d908b6efa9fd4e0a7360e68c4eec50e6181d261091043d9a6000867af9bb6.bin.gz agent.macos-amd64.863a7a2f13d9813f7180503fdeb35eb79ec14c0d259408b16d14fc69a32dc113.bin.gz agent.macos-arm64.9c8134346b951dd5d7c81f6aa10501fde7637831632d6b1591f787a807fcb87b.bin.gz agent.windows-amd64.c1b507203732fbefad4bfc2a809b8c0fa0eba69ca8a6cad3a54b922c2f31541f.exe.gz agent.windows-x86.0e911215b789576ea7f511a38760cfb55d33d728cf3f7fc876c33dd5251a53d8.exe.gz integrator.windows64.fbb706073459de90303e42f356be48765c2615bb2178eb2ba3d78780bd1956ad.exe.gz
