Skip to content

Releases: munkireport/munkireport-php

Munkireport 3.2.2

08 Jul 21:13
Compare
Choose a tag to compare

3.2.2 (July 08, 2018)

FIXES

Munkireport 3.2.1

05 Jul 15:38
Compare
Choose a tag to compare

3.2.1 (July 05, 2018)

FIXES

Munkireport 3.2.0

01 Jul 06:30
Compare
Choose a tag to compare

3.2.0 (July 01, 2018)

FIXES

NEW FEATURES

NEW MODULES

Munkireport 3.1.1

23 Mar 16:34
Compare
Choose a tag to compare

3.1.1 (March 23, 2018)

FIXES

  • filevault escrow migration

NEW FEATURES

Munkireport 3.1.0

21 Mar 21:57
Compare
Choose a tag to compare

3.1.0 (March 21, 2018)

FIXES

  • Totalsize of disk in client detail
  • Updated MySQL default config example
  • munkiinfo module
  • Adjusted security report loading data (#983) @tuxudo
  • Fix DeployStudio migration (#982) @tuxudo
  • Fixed DeployStudio processing on MR3 (#985) @tuxudo
  • Add option to use current username for ssh link (#976) @poundbangbash
  • Check for no Bluetooth in BT module (#992) @tuxudo
  • Fixed postflight error in homebrew modules (#991) @tuxudo
  • Migration adjustment for nullable values. (#973) @poundbangbash
  • Fixed vendor column (#998) @tuxudo
  • Docker (#1003) @sphen13
  • Remove index.php .htacces and web.config from src root
  • Fix certificate migration
  • Add fv key encryption migration
  • Add filter to getLocalAdmins
  • Extensions module - Added variable declaration (#1017) @poundbangbash

NEW FEATURES

  • Add optional recursive group searching to AD auth
  • Added widget for 32-bit apps (#1021) @tuxudo
  • Added support for different ship to in GSX (#1028)

Munkireport 3.0.2

15 Feb 20:21
Compare
Choose a tag to compare

3.0.2 (February 15, 2018)

More bugfixes, mostly migration related.

FIXES

  • Fixed migrations for SQLite (#971)
  • Added indexes for the tag, usb, fonts, network_shares, homebrew and servermetrics modules
  • Improved Dockerfile

Munkireport 3.0.1

14 Feb 12:58
Compare
Choose a tag to compare

3.0.1 (February 14, 2018)

This is a small bugfix release that fixes some issues with the 3.0.0 release.

FIXES

NEW FEATURES

Munkireport 3.0.0

07 Feb 13:25
Compare
Choose a tag to compare

3.0.0 (February 07, 2018)

The third major version of munkireport attempts to solve a couple of longstanding issues concerning security, dependency management and database management. We're moving slowly to using eloquent as replacement for the KISS database abstraction. A ton of work has been done by @mosen to make this all work.

Most notable changes are:

  • Minimum PHP version is 7.0
  • Document root is now in a directory called /public. The best practice is to serve your munkireport instance from this directory or make a symlink to this directory.
  • If you install munkireport via the commandline, you need to install all dependencies first via composer
  • There is a new database configuration format $conf['connection']. See config_default.php on how to use it.
  • Database migrations (also the initial ones) are not running automatically. You need to run migrations via the commandline tool php database/migrate.php

See also the Upgrade v3 guide and Quick demo v3

FIXES

  • Certificate Module fix for multiple certs with same name (#893) @sphen13
  • Misc UI fixes (#885) @tuxudo
  • Fix vendors for 10.13 (#902) @tuxudo
  • Fix localization in client tab (#903) @tuxudo
  • Use CFPreferences to read BaseUrl and Passphrase. (#919) @MagerValp
  • Misc migration fixes
  • AuthLDAP fixed (#944)
  • Recaptcha uses proxy settings
  • Database info fixed
  • Installer postflight script (#949) @MagerValp

NEW FEATURES

Munkireport 2.15.2

28 Sep 14:28
Compare
Choose a tag to compare

2.15.2 (Sept 28, 2017)

FIXES since 2.15.1

  • Fixed Apple icon url

FIXES since 2.15.0

  • Removed default method from Schema.php which caused errors in PHP < 7.0.0

FIXES

NEW FEATURES

  • Add Munki 3 ManagedInstalls Keys
  • Kernel Extensions Module (KEXT) - @tuxudo
  • More default filters for inventory module - @poundbangbash
  • APFS support in disk_report module
  • Invisible CAPTCHA (you need to generate new keys if you were using the previous version)
  • Schema class to help with migrations

REQUIREMENTS

This version requires php version 5.6 minimum

UPGRADING

By default, only three modules are enabled. To enable more modules, please read https://github.com/munkireport/munkireport-php/blob/master/docs/setup.md#select-which-modules-to-install-on-the-client

If you upgrade 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 if you're logged in as an admin user (see note at the top of this page)

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

  • When new modules are released or if you add a module to the module list in config.php, a new client pkg installer will need to be created and installed on clients to report on the new data.
  • Due to preference caching issues with cfprefsd it is advised that you either restart the client or issue a "killall cfprefsd" after the new modules are installed on the client. Clients may not report back for the new modules until that is done.

Munkireport 2.15.1

18 Sep 16:42
Compare
Choose a tag to compare

2.15.1 (Sept 18, 2017)

FIXES since 2.15.0

  • Removed default method from Schema.php which caused errors in PHP < 7.0.0

FIXES

NEW FEATURES

  • Add Munki 3 ManagedInstalls Keys
  • Kernel Extensions Module (KEXT) - @tuxudo
  • More default filters for inventory module - @poundbangbash
  • APFS support in disk_report module
  • Invisible CAPTCHA (you need to generate new keys if you were using the previous version)
  • Schema class to help with migrations

REQUIREMENTS

This version requires php version 5.6 minimum

UPGRADING

By default, only three modules are enabled. To enable more modules, please read https://github.com/munkireport/munkireport-php/blob/master/docs/setup.md#select-which-modules-to-install-on-the-client

If you upgrade 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 if you're logged in as an admin user (see note at the top of this page)

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 pkg installer.