2019.5 Service Update
September 10, 2019
Release Notes
We're pleased to announce our 2019.5 Service Update, soon to be followed by new versions of File Protection Desktop and File Protection Server. These releases contain the following:
Changes
In order to provide a more complete reporting snapshot of your users, we've added a Status column to the special report Users report. In cases in which a user has multiple statuses, only one will display. The order of status precedence is:
- Disabled
- Password locked
- Not Activated
- Active
If, for example, a user's password is locked and their account is disabled, the Status column will display Disabled.
For general information, please refer to Reports.
A new security feature called Full Disk Access was introduced with macOS Mojave. In order for File Protection Desktop for Mac backups to work properly in macOS Mojave or later, you must enable Full Disk Access. To learn how, please refer to How do I enable Full Disk Access for File Protection on macOS?
Issue Resolutions
In addition to a variety of minor enhancements and stability improvements, the following issues are resolved in this release:
Recycling a metered plan File Protection server did not free up the storage allocated to the device. The issue has been resolved.
Upgrade of File Protection Server resulted in a reset of the "run as" selection to LocalSystem instead of the previously selected user. The issue has been resolved.
Please note that upgrading from a previous version to version 8.1 will cause the account running the service to revert to LocalSystem. This will not, however, occur again upon subsequent upgrades.
In File Protection Desktop for Windows, the Status Report - Datto File Protection.xml file was missing a value for "backup-last-complete" upon upgrade from older (pre-Datto) versions. This value will now be retained on upgrade.
In File Protection Desktop for Windows and File Protection Server, an uncommon set of circumstances caused a popup warning message to display an entertainingly preposterous but completely inaccurate amount of required disk space. The issue has been resolved.
As always, we've included in this release a number of interface improvements and corrections.