Make configuration.mof changes and restores from backup more robust
Currently, changes to configuration.mof appear to be read in based on the timestamp of the file.
This means that if you restore configuration.mof from a backup, it will not be re-read into the database because the timestamp is older.
Recently I had to force a re-read of a backup of configuration.mof by making a trivial change to a comment in the file so that the timestamp was changed and thus hardware inventory would again run on my clients.
It would seem that perhaps a checksum of the file compared to a file that was read in previously would resolve this issue.