Event details

With Microsoft 365, we reject the tyranny of “or” and embrace the genius of “and.” That’s why a variety of mobile platforms are supported in Microsoft 365 environments. But what about managing and se...
Char_Cheesman
Updated Dec 27, 2024
Web series
rrenstrom's avatar
rrenstrom
Brass Contributor
Jun 18, 2024
Any improvements coming in non-LOB package detection rules, beyond the current app bundle version check? This is needed to cover situations for packages that install in non-standard locations or don't have an app bundle. Currently these types of packages install over and over every check-in, since it can't determine if a package is already installed. It would be awesome to offer more detections, such as checking package receipts/version, a particular file path, or a user generated install check script to determine if a package is already installed.
rrenstrom's avatar
rrenstrom
Brass Contributor
Jun 18, 2024

Arnab Biswas thank you for answering this during today's live episode.

One way Microsoft could quickly and immediately address this would be to slighly alter the Pre-install script exit code check.

Currently according to https://learn.microsoft.com/en-us/mem/intune/apps/macos-unmanaged-pkg documentation, "Pre-install script: Provide a script that runs before the app is installed. Only when the preinstall script returns zero (indicating success), the app proceeds to install. If the preinstall script returns a non-zero code (indicating failure), the app doesn't install and reports its installation status as "failed". The preinstall script runs again for failed installations at the next device check-in (sync)."

Microsoft could enhance this to provide a way for the admin to indicate a package is already installed by offering a custom exit code the pre-install script can return (eg exit code 2 for "package already installed"), so the reports show the installation status as "success".