Munkireport 2.0.10

2.0.10 (June 30, 2014)

This release has some changes to the way preflight scripts are handled:

• scripts with a non-zero exit status will not terminate a munki run. If you rely on this behaviour, you should move your script to preflight_abort.d
• all scripts (including preflight) are aborted after 10 seconds. Munkireport will emit a warning when a timeout is reached.

FIXES

• Better widget sorting (thanks to @nbalonso)
• jQuery 2.1.0
• Bootstrap 3.1.1
• Date display fixed in install history and client detail
• AD module (thanks to @nbalonso)
• MySQL create table now uses default innodb and utf-8
• FV users in security listing (thanks to @diwanicki)
• Preflight scripts handling improved

NEW FEATURES

• ARD info fields
• CPU info (thanks to @joshua-d-miller)
• Add your custom css and js files to MR
• External (and internal) displays tracking (thanks to @nbalonso)
• Display vendor strings added (thanks to @diwanicki)
• Bluetooth device tracking (thanks to @gmarnin)
• Site name on login page (thanks to @gmarnin)
• Client uptime reporting
• Added postflight.d and preflight_abort.d
• verbosity is now controlled by munki (with munki 1.0.0.1883 or 2.0.0.2086 and up)

UPGRADING

There are some changes in the database setup, if you are upgrading from a previous version, you should:

• Make a backup of your database
• Add the following line to config.php:

$conf['allow_migrations'] = TRUE;

This will automatically migrate your database to the correct version.

For more info about upgrading, visit https://github.com/munkireport/munkireport-php/wiki/How-to-upgrade

• If you come from a previous release and you want to add new report items, you have to push your clients a new pkginfo file.