You can filter the inventory display by device status, type, class, name and category. This helps shorten the list when you're dealing with more than a handful of devices. Once devices are inventoried, device configuration is downloaded into the database. The configuration is then tracked, annotated and compared for changes. We tested this by changing the configuration of a device that already had been inventoried and stored. This created a new version of a particular device configuration. We then were given an option to either commit to the changes and send them to the device or revert to the original configuration. This added step protects against configuration mistakes. Plus, the log noted that someone using our user ID authored the changes.
In the comparison display, two types of changes are shown: those within line numbers and those in the correct position within the configuration. It is very straightforward to find changes and make any necessary fixes to them.
Reporting is clear and concise. Additionally, you can choose between preconfigured reports and custom reports. The canned reports provide enough information about the configuration backups and changes to manage configurations right out of the shrink wrap.
We created custom reports using the wizard. This process was tedious, but we got the hang of it after a while. Still, DeviceAuthority could be improved by simply making the report definition directly editable or by at least adding a Finish button, so that when changes are saved you do not have to walk serially through every report option.
We also created a report showing the changes for the last seven days on a subset of the infrastructure DeviceAuthority was managing. The output is available as text, HTML and PDF. The HTML format has the best visual formatting, and a floating header would make it perfect.