DeviceAuthority's scheduled backup of device configuration is another very strong feature. We created a schedule that selected devices we had added to our lab's infrastructure group. Available fields include specific device, host name, make, model, class and OS as targets for configuration backup. Backups worked as advertised.
Look Ma, I Can Still Shoot Myself in the Foot!
DeviceAuthority can't protect from the random hit-and-run--or in our case head-on--collision, so we don't recommend it for operational or helpdesk employees. Configuration syntax checking isn't available, so poorly advised changes or even incorrect formats can be uploaded.
Although access control functionality is offered, DeviceAuthority is basically a flat model with an administrative account and all other accounts. The administrative user is the only one who can add accounts. This means that, short of adding and deleting other users, all users have the same rights to devices in DeviceAuthority's inventory. Such security obviously is not good enough for either an enterprisewide or a service provider solution.
Stand-in or proxy access for the configuration management system is, unfortunately, not included in DeviceAuthority. This means that remote access, even by telnet, is not possible.