Now we can call any script on the root of the path where `appName` is found.
Same result:
```
2021-11-10 15:58:02 adobecreativeclouddesktop setting variable from argument DEBUG=0
2021-11-10 15:58:02 adobecreativeclouddesktop setting variable from argument INSTALL=force
2021-11-10 15:58:02 adobecreativeclouddesktop ################## Start Installomator v. 0.8.0
2021-11-10 15:58:02 adobecreativeclouddesktop ################## adobecreativeclouddesktop
2021-11-10 15:58:03 adobecreativeclouddesktop BLOCKING_PROCESS_ACTION=tell_user
2021-11-10 15:58:03 adobecreativeclouddesktop NOTIFY=success
2021-11-10 15:58:03 adobecreativeclouddesktop LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-10 15:58:03 adobecreativeclouddesktop no blocking processes defined, using Creative Cloud as default
2021-11-10 15:58:03 adobecreativeclouddesktop Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.WNV7B1pH
2021-11-10 15:58:03 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 15:58:03 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 15:58:03 adobecreativeclouddesktop appversion:
2021-11-10 15:58:03 adobecreativeclouddesktop Latest version of Creative Cloud is 5.6.0.788
2021-11-10 15:58:03 adobecreativeclouddesktop Downloading https://ccmdl.adobe.com/AdobeProducts/KCCC/CCD/5_6_0/macarm64/ACCCx5_6_0_788.dmg to Creative Cloud.dmg
2021-11-10 15:58:17 adobecreativeclouddesktop no more blocking processes, continue with update
2021-11-10 15:58:17 adobecreativeclouddesktop Installing Creative Cloud
2021-11-10 15:58:17 adobecreativeclouddesktop Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.WNV7B1pH/Creative Cloud.dmg
2021-11-10 15:58:18 adobecreativeclouddesktop Mounted: /Volumes/Creative Cloud
2021-11-10 15:58:18 adobecreativeclouddesktop Verifying: /Volumes/Creative Cloud/Install.app
2021-11-10 15:58:18 adobecreativeclouddesktop Team ID matching: JQ525L2MZD (expected: JQ525L2MZD )
2021-11-10 15:58:18 adobecreativeclouddesktop Downloaded version of Creative Cloud is 2.6.0.46 (replacing version ).
2021-11-10 15:58:18 adobecreativeclouddesktop CLIInstaller exists, running installer command /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 15:58:23 adobecreativeclouddesktop Succesfully ran /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 15:58:23 adobecreativeclouddesktop Debugging enabled, update tool output was:
objc[20055]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565018) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10f2f0790). One of the two will be used. Which one is undefined.
objc[20055]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565068) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10f2f07e0). One of the two will be used. Which one is undefined.
objc[20055]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565018) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x110302790). One of the two will be used. Which one is undefined.
objc[20055]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102565068) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x1103027e0). One of the two will be used. Which one is undefined.
Starting installer...
Installation successful.
2021-11-10 15:58:23 adobecreativeclouddesktop Finishing…
2021-11-10 15:58:33 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 15:58:33 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 15:58:33 adobecreativeclouddesktop Installed Creative Cloud
2021-11-10 15:58:33 adobecreativeclouddesktop notifying
2021-11-10 15:58:33 adobecreativeclouddesktop Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.WNV7B1pH
2021-11-10 15:58:33 adobecreativeclouddesktop Unmounting /Volumes/Creative Cloud
"disk5" ejected.
2021-11-10 15:58:33 adobecreativeclouddesktop App not closed, so no reopen.
2021-11-10 15:58:33 adobecreativeclouddesktop ################## End Installomator, exit code 0
```
Changes to the label, so path to CLIInstaller does not contain the name of the app, as that is already in the variable `appPath`.
Still needing to decide on debug logging or what kind of message we want there.
But this is succesfull:
```
% sudo /Users/st/Documents/GitHub/Installomator/utils/assemble.sh -r adobecreativeclouddesktop DEBUG=0 INSTALL=force
Password:
2021-11-10 11:30:51 adobecreativeclouddesktop setting variable from argument DEBUG=0
2021-11-10 11:30:51 adobecreativeclouddesktop setting variable from argument INSTALL=force
2021-11-10 11:30:51 adobecreativeclouddesktop ################## Start Installomator v. 0.8.0
2021-11-10 11:30:51 adobecreativeclouddesktop ################## adobecreativeclouddesktop
2021-11-10 11:30:51 adobecreativeclouddesktop BLOCKING_PROCESS_ACTION=tell_user
2021-11-10 11:30:51 adobecreativeclouddesktop NOTIFY=success
2021-11-10 11:30:52 adobecreativeclouddesktop LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-10 11:30:52 adobecreativeclouddesktop no blocking processes defined, using Creative Cloud as default
2021-11-10 11:30:52 adobecreativeclouddesktop Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.wMH45Qfi
2021-11-10 11:30:52 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 11:30:52 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 11:30:52 adobecreativeclouddesktop appversion:
2021-11-10 11:30:52 adobecreativeclouddesktop Latest version of Creative Cloud is 5.6.0.788
2021-11-10 11:30:52 adobecreativeclouddesktop Downloading https://ccmdl.adobe.com/AdobeProducts/KCCC/CCD/5_6_0/macarm64/ACCCx5_6_0_788.dmg to Creative Cloud.dmg
2021-11-10 11:31:41 adobecreativeclouddesktop no more blocking processes, continue with update
2021-11-10 11:31:41 adobecreativeclouddesktop Installing Creative Cloud
2021-11-10 11:31:41 adobecreativeclouddesktop Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.wMH45Qfi/Creative Cloud.dmg
2021-11-10 11:31:42 adobecreativeclouddesktop Mounted: /Volumes/Creative Cloud 2
2021-11-10 11:31:42 adobecreativeclouddesktop Verifying: /Volumes/Creative Cloud 2/Install.app
2021-11-10 11:31:42 adobecreativeclouddesktop Team ID matching: JQ525L2MZD (expected: JQ525L2MZD )
2021-11-10 11:31:42 adobecreativeclouddesktop Downloaded version of Creative Cloud is 2.6.0.46 (replacing version ).
2021-11-10 11:31:42 adobecreativeclouddesktop CLIInstaller exists, running installer command /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 11:31:46 adobecreativeclouddesktop Succesfully ran /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 11:31:46 adobecreativeclouddesktop Debugging enabled, update tool output was:
objc[71312]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f018) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10dc38790). One of the two will be used. Which one is undefined.
objc[71312]: Class ProxyManager is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f068) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10dc387e0). One of the two will be used. Which one is undefined.
objc[71312]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f018) and /Volumes/Creative Cloud 2/resources/AdobePIM.dylib (0x10e4e6790). One of the two will be used. Which one is undefined.
objc[71312]: Class ProxyManager is implemented in both /Volumes/Creative Cloud 2/Install.app/Contents/MacOS/Install (0x100c2f068) and /Volumes/Creative Cloud 2/resources/AdobePIM.dylib (0x10e4e67e0). One of the two will be used. Which one is undefined.
Starting installer...
Installation successful.
2021-11-10 11:31:46 adobecreativeclouddesktop Finishing…
2021-11-10 11:31:56 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 11:31:56 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 11:31:56 adobecreativeclouddesktop Installed Creative Cloud
2021-11-10 11:31:56 adobecreativeclouddesktop notifying
2021-11-10 11:31:56 adobecreativeclouddesktop Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.wMH45Qfi
2021-11-10 11:31:56 adobecreativeclouddesktop Unmounting /Volumes/Creative Cloud 2
"disk6" ejected.
2021-11-10 11:31:57 adobecreativeclouddesktop App not closed, so no reopen.
2021-11-10 11:31:57 adobecreativeclouddesktop ################## End Installomator, exit code 0
```
I was looking into installing Adobe CC fully (Isaac has done the hard part), and we can add `CLIInstaller` and `CLIArguments` to get it fully installed.
This implementation is slightly changed from Isaacs.
```
% sudo /Users/st/Documents/GitHub/Installomator/utils/assemble.sh -r adobecreativeclouddesktop DEBUG=0 INSTALL=force
2021-11-10 08:56:00 adobecreativeclouddesktop setting variable from argument DEBUG=0
2021-11-10 08:56:00 adobecreativeclouddesktop setting variable from argument INSTALL=force
2021-11-10 08:56:00 adobecreativeclouddesktop ################## Start Installomator v. 0.8.0
2021-11-10 08:56:00 adobecreativeclouddesktop ################## adobecreativeclouddesktop
2021-11-10 08:56:00 adobecreativeclouddesktop BLOCKING_PROCESS_ACTION=tell_user
2021-11-10 08:56:00 adobecreativeclouddesktop NOTIFY=success
2021-11-10 08:56:00 adobecreativeclouddesktop LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-10 08:56:00 adobecreativeclouddesktop no blocking processes defined, using Creative Cloud as default
2021-11-10 08:56:00 adobecreativeclouddesktop Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.0LNrXCQX
2021-11-10 08:56:01 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 08:56:01 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 08:56:01 adobecreativeclouddesktop appversion:
2021-11-10 08:56:01 adobecreativeclouddesktop Latest version of Creative Cloud is 5.6.0.788
2021-11-10 08:56:01 adobecreativeclouddesktop Downloading https://ccmdl.adobe.com/AdobeProducts/KCCC/CCD/5_6_0/macarm64/ACCCx5_6_0_788.dmg to Creative Cloud.dmg
2021-11-10 08:56:30 adobecreativeclouddesktop no more blocking processes, continue with update
2021-11-10 08:56:30 adobecreativeclouddesktop Installing Creative Cloud
2021-11-10 08:56:30 adobecreativeclouddesktop Mounting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.0LNrXCQX/Creative Cloud.dmg
2021-11-10 08:56:30 adobecreativeclouddesktop Mounted: /Volumes/Creative Cloud
2021-11-10 08:56:30 adobecreativeclouddesktop Verifying: /Volumes/Creative Cloud/Install.app
2021-11-10 08:56:30 adobecreativeclouddesktop Team ID matching: JQ525L2MZD (expected: JQ525L2MZD )
2021-11-10 08:56:30 adobecreativeclouddesktop Downloaded version of Creative Cloud is 2.6.0.46 (replacing version ).
2021-11-10 08:56:30 adobecreativeclouddesktop CLIInstaller exists, running installer command /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install --mode=silent
2021-11-10 08:56:34 adobecreativeclouddesktop Debugging enabled, update tool output was: objc[51900]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a018) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10fa75790). One of the two will be used. Which one is undefined.
objc[51900]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a068) and /Library/Application Support/Adobe/Adobe Desktop Common/Core/AdobePIM.dylib (0x10fa757e0). One of the two will be used. Which one is undefined.
objc[51900]: Class HTTPHeader is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a018) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x110a87790). One of the two will be used. Which one is undefined.
objc[51900]: Class ProxyManager is implemented in both /Volumes/Creative Cloud/Install.app/Contents/MacOS/Install (0x102d2a068) and /Volumes/Creative Cloud/resources/AdobePIM.dylib (0x110a877e0). One of the two will be used. Which one is undefined.
Starting installer...
Installation successful.
2021-11-10 08:56:34 adobecreativeclouddesktop Finishing…
2021-11-10 08:56:44 adobecreativeclouddesktop App(s) found: /Library/Application Support/Adobe/Adobe Desktop Common/HDBox/Install.app
2021-11-10 08:56:44 adobecreativeclouddesktop could not determine location of Install.app
2021-11-10 08:56:44 adobecreativeclouddesktop Installed Creative Cloud
2021-11-10 08:56:44 adobecreativeclouddesktop notifying
2021-11-10 08:56:44 adobecreativeclouddesktop Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.0LNrXCQX
2021-11-10 08:56:44 adobecreativeclouddesktop Unmounting /Volumes/Creative Cloud
"disk4" ejected.
2021-11-10 08:56:45 adobecreativeclouddesktop App not closed, so no reopen.
2021-11-10 08:56:45 adobecreativeclouddesktop ################## End Installomator, exit code 0
```
If `INSTALL=force` is used, then previously we would need installed version and appNewVersion to be equal for the updateTool to be skipped. Not anymore.
Separate lines for running `msupdate --list` before running the update tool, but currently it runs if just msupdate exist, and not only if we run the updateTool.
By using variable `archiveName` we can let Installomator find the right archive in the github list of possibilities. I think this is a more cleaner approach.
Added a bit to explanation of archiveName variable.
```
sudo /Users/st/Documents/GitHub/Installomator/utils/assemble.sh -r macports DEBUG=0 INSTALL=force
Password:
2021-11-02 09:55:12 macports setting variable from argument DEBUG=0
2021-11-02 09:55:12 macports setting variable from argument INSTALL=force
2021-11-02 09:55:12 macports ################## Start Installomator v. 0.8.0
2021-11-02 09:55:12 macports ################## macports
2021-11-02 09:55:13 macports BLOCKING_PROCESS_ACTION=tell_user
2021-11-02 09:55:13 macports NOTIFY=success
2021-11-02 09:55:14 macports LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2021-11-02 09:55:14 macports no blocking processes defined, using MacPorts as default
2021-11-02 09:55:14 macports Changing directory to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.4KnOGDkl
2021-11-02 09:55:14 macports Custom App Version detection is used, found 2.7.1
2021-11-02 09:55:14 macports appversion: 2.7.1
2021-11-02 09:55:14 macports Latest version of MacPorts is 2.7.1
2021-11-02 09:55:14 macports There is no newer version available.
2021-11-02 09:55:14 macports Using force to install anyway. Not using updateTool.
2021-11-02 09:55:14 macports Downloading https://github.com/macports/macports-base/releases/download/v2.7.1/MacPorts-2.7.1-12-Monterey.pkg to Monterey.pkg
2021-11-02 09:55:15 macports no more blocking processes, continue with update
2021-11-02 09:55:15 macports Installing MacPorts
2021-11-02 09:55:16 macports Verifying: Monterey.pkg
2021-11-02 09:55:16 macports Team ID: QTA3A3B7F3 (expected: QTA3A3B7F3 )
2021-11-02 09:55:16 macports Installing Monterey.pkg to /
installer: Package name is MacPorts
installer: Upgrading at base path /
installer: The upgrade was successful.
2021-11-02 09:56:03 macports Finishing…
2021-11-02 09:56:13 macports Custom App Version detection is used, found 2.7.1
2021-11-02 09:56:13 macports Installed MacPorts, version 2.7.1
2021-11-02 09:56:13 macports notifying
2021-11-02 09:56:14 macports Deleting /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.4KnOGDkl
2021-11-02 09:56:14 macports App not closed, so no reopen.
2021-11-02 09:56:14 macports ################## End Installomator, exit code 0
```
In this branch I demand that INSTALL=force if an App Store app should be replaced. Best example is Slack that will loose all settings if it is replaced. But we can still do it and the log will show what we are doing.
First /Applications, then /Applications/Utilities, and then Spotlight. Maybe we should be prepared that DEPnotify should be installed in Utilities, so `customDestination="/Applications/Utilities/"`could ba a thing.
The URL for `webexteams` appears to have changed yet another time.
Good thing: The downloaded `pkg` contains the versions for Intel and Apple Silicon at the same time. So no additional URL required :-)
[TechSmith Capture](https://www.techsmith.com/jing-tool.html) is a simple, free way to capture basic screenshots and screen recordings and share them with others.
Thanks for find the URL with release-notes, but the original version returned had too much content. Current version is only 1.3.4, not "1.3.4.4648". But in the little square on the right side above the download link is the version, so I took that.
If using INSTALL=force, the script will not be using updateTool, but will reinstall instead.
microsoftteams label was still having appNewVersion that does not work, so that has been commented out.
This is my first time contributing to Installomator, so my apologies in advance if I'm missing something, or doing something wrong.
I believe this is the best option to find the latest appNewVersion number for TextExpander specifically, but I'm also happy to be proven otherwise.
There are direct links for Intel and Apple Silicon packages of PyCharm Pro available. Replaced the existing URLs with the simplified ones.
Also corrected a doubled 'appNewVersion' line.
The XML from the vagrant downloads page is one giant html document with no spaces. If there's a better & more efficient way of parsing this, please lmk or update according so it can serve as a template for other similarly formatted websites.
The `prompt_user` option uses osascript to attempt to quit an app three times,
which can sometimes fail. Added an option `prompt_user_then_kill` to attempt
to quit twice, but kill the process if earlier quit attempts failed.
- removed leading `0` from the version because it has lost all meaning (thanks to @grahampugh for the inspiration)
- Installomator now detects when an app is already installed, and will display notifications correctly the user based on if the app was updated or installed for the first time.
- New variables for labels that should be installed using CLI: `CLIInstaller` and `CLIArguments`. When the installer app is named differently than the installed app, then the variable `installerTool` should be used to name the app that should be located in the DMG or zip. See the label __adobecreativeclouddesktop__ to see its use.
-`buildLabel.sh` has been improved to build GitHub software labels much easier. In essense if the URL contains github.com, then it will try to find if it's the latest version or if variable `archiveName` is needed for finding the software. Also improved messaging throughout the script, as well as handling a situation where a pkg does not include a “Distribution” file, but a “PackageInfo”.
- MDM script extended with `caffeinate` so Mac will not go to sleep during the time it takes installomator to run. Especially during setup, this can be useful.
- Microsoft labels with `updateTool` variable, is updated to run `msupdate --list` before running the updateTool directly. Problems have been reported that the update would fail if the `--list` parameter for the command was not run first. This should help with the Jamf agent stalling during installation.
- Added bunch of new labels, and improved others.
## v0.7
- default for `BLOCKING_PROCESS_ACTION`is now `BLOCKING_PROCESS_ACTION=tell_user` and not `prompt_user`. It will demand the user to quit the app to get it updated, and not present any option to skip it. In considering various use cases in different MDM solutions this is the best option going forward. Users usually choose to update, and is most often not bothered much with this information. If it's absoultely a bad time, then they can move the dialog box to the side, and click it when ready.
- script is now assembled from fragments. This helps avoid merging conflicts on git and allows the core team to work on the script logic while also accepting new labels. See the "Assemble Script ReadMe" for details.
- We now detect App Store installed apps, and we do not replace them automatically. An example is Slack that will loose all settings if it is suddenly changed from App Store version to the "web" version (they differ in the handling of settings files). If `INSTALL=force` then we will replace the App Store app. We log all this.
- Change in finding installed apps. We now look in /Applications and /Applications/Utilities first. If not found there, we use spotligt to find it. (We discovered a problem when a user has Parallels Windows installed with Microsoft Edge in it. Then Installomator wanted to update the app all the time, becaus spotlight found that Windows version of the app that Parallels created.)
- Added bunch of new labels, and improved others.
- Renamed `buildCaseStatement.sh` to `buildLabel.sh` and improved it a lot. It is a great start when figuring out how to create a new label for an app, or a piece of software. Look at the tutorials in our wiki.
- Mosyle changed their app name from Business to Self-Service
## v0.6 - 2021-07-14
- several new and updated labels, for a total of 302
- versionKey variable can be used to choose which Info.plist key to get the version from
- an appCustomVersion() {} function can now be used in a label
- with INSTALL=force, the script will not be using updateTool, but will reinstall instead
- added quit and quit_kill options to NOTIFY
- updated buildCaseStatement.sh
- updated buildInstallomatorPkg.sh to use notarytool (requires Xcode 13)
- several minor fixes
## v0.5 - 2021-04-13
- Major update and now with help from @Theile and @Isaac
- Added additional `NOTIFY=all`. Usuful if used in Self Service, as the user will be notified before download, before install as well as when it is done.
- Added variable `LOGO` for icons i dialogs, use `LOGO=appstore` (or `jamf` or `mosyleb` or `mosylem` or `addigy`). It's also possible to set it to a direct path to a specific icon. Default is `appstore`.
- Added variable `INSTALL` that can be set to `INSTALL=force` if software needs to be installed even though latest version is already installed (it will be a reinstall).
- Version control now included. The variable `appNewVersion` in a label can be used to tell what the latest version from the web is. If this is not given, version checking is done after download.
- For a label that only installs a pkg without an app in it, a variable `packageID` can be used for version checking.
- Labels now sorted alphabetically, except for the Microsoft ones (that are at the end of the list). A bunch of new labels added, and lots of them have either been changed or improved (with `appNewVersion` og `packageID`).
- If an app is asked to be closed down, it will now be opened again after the update.
- If your MDM cannot call a script with parameters, the label can be set in the top of the script.
- If your MDM is not Jamf Pro, and you need the script to be installed locally on your managed machines, then take a look at [Theiles fork](https://github.com/Theile/Installomator/). This fork can be called from the MDM using a small script.
- Script `buildCaseStatement.sh` to help with creating labels have been improved.
- Fixed a bug in a variable name that prevented updateTool to be used
- added `type` variable for value `"updateronly"` if the label should only run an updater tool.
## v0.4 - 2020-10-19
- you can now set script variables as an argument in the form `VARIABLE=value`. More detail on this in the README file, 'Configuration from Arguments.' (#26, #50, #72, and #73)
- change `downloadFromGit` to match file types better (#58)
- implemented a workaround for changed behavior of `xpath` in Big Sur (#80)
- added an option `prompt_user_then_kill` to `BLOCKING_PROCESS_ACTION` which will kill the process after the third unsuccessful attempt to quit (#78, thanks Patrick Atoon @raptor399)
- added several new labels for total of 116
## v0.3 - 2020-07-23
- added several new labels for total of 98
- removed the powershell labels, since the installer is not notarized
@@ -7,6 +65,7 @@
- improved logging in some statements
- several more minor improvements
## v0.2 - 2020-06-09
- many fixes for broken URLs and other bugs
@@ -16,4 +75,5 @@
improved logging
- several new applications: count increased from 62 in 0.1 to 87 in 0.2
__Please note, that if you are contributing to this project with new labels or other suggestions in PRs, please put your changes in the fragmented files, not the full `Installomator.sh` script. The full script is now a build of the fragments, and will be overwritten.__
We try to keep the script as short as possible, and with more than 300 labels, we can save 300 lines in the script, if we do not have credit lines on each of these. So we are thankful for your contribution, but we will be removing these lines in the coming releases.
## Labels
If you need a new label, please take a look at the tutorials in the Wiki, if those can be helpful for starting out on the creation of the label.
We really encourage you to try out finding the version of the app online, so that `appNewVersion` can be filled in the label. It helps a lot when the software needs update, and greatly improve user experience.
When creating a new label, please file a pull request (PR). And feel free to ask questions or make your comments about what else is needed, if we should take a look at the label, or help out in finding the version or isolating URLs or anything else.
Please include the log of installing this label in the description.
Please have one label per PR, so we can separate these. Also if you change/fix a label.
Thank you very much!
## Issues
Do not create an issue just when you have a questions, but do file an issue or pull request (PR) for bugs or wrong behavior. Include the full log and include the version of Installomator you're running.
When in doubt, use the MacAdmins.org Slack as described in [README.md](https://github.com/Installomator/Installomator/)
This script is in the "we find it useful, it is working for us" stage.
This script is in the “we find it useful, it is working for us” stage.
Your production and deployment environment will be different, please test thoroughly before rolling it out to your production.
@@ -12,11 +12,13 @@ I have put a lot of work into making it stable and safe, but I cannot - of cours
## Support and Contributing
Discussion, support and advice around Installomator happens in the `#installomator` channel in the [MacAdmins Slack](https:/macadmins.org). Go there for support questions.
__Please note, that if you are contributing to this project with new labels or other suggestions in PRs, please put your changes in the fragmented files, not the full `Installomator.sh` script. The full script is now a build of the fragments, and will be overwritten. See the REAMDME.md file in the `utils` directory for detailed instructions.__
Do not create an issue just when you have a questions, but do file an issue or pull request for bugs or wrong behavior. When in doubt, ask in the above Slack channel.
Discussion, support and advice around Installomator happens in the `#installomator` channel in the [MacAdmins.org Slack](https://macadmins.org). Go there for support questions.
If you have added a new label, then please file a pull request. (and Thank you!)
Do not create an issue just when you have a questions, but do file an issue or pull request (PR) for bugs or wrong behavior. When in doubt, ask in the above Slack channel.
Please see [CONTRIBUTING.md](https://github.com/Installomator/Installomator/blob/dev/CONTRIBUTING.md) for how to contribute.
## More reading
@@ -24,6 +26,7 @@ There are a few interesting post on Installomator on my weblog:
There is a debug mode and one other setting that can be controlled with variables in the code. This simplifies the actual use of the script from within a management system.
### Extensible
As of this writing, Installomator knows how to download and install more than 50 different applications. You can add more by adding a block to the _long_`case` statement starting on line 160. Some of them are more elaborate, but most of them just need this information:
As of this writing, Installomator knows how to download and install more than 238 different applications. You can add more by adding a block to the _long_`case` statement starting on line 758. Some of them are more elaborate, but most of them (just) need this information (not really "just" in this case, as we have to differentiate between arm64 and i386 versions for both `downloadURL` and `appNewVersion`):
appNewVersion=$(curl -s https://omahaproxy.appspot.com/history | awk -F',' '/mac,stable/{print $3; exit}') # Credit: William Smith (@meck)
fi
expectedTeamID="EQHXZ8M8AV"
;;
```
When you know how to extract these pieces of information from the application and/or download, then you can add an application to Installomator.
The script `buildCaseStatement.sh` can help with the label creation.
Please note: Labels should be named in small caps, numbers 0-9, “-”, and “_”. No other characters allowed.
### Not specific to a management system
I wrote this script mainly for use with Jamf Pro, because that is what we use. For testing, you can run the script interactively from the command line. However, I have tried to keep anything that is specific to Jamf optional, or so flexible that it will work anywhere. Even if it does not work with your management system 'out of the box,' the adaptations should be straightforward.
Not all MDMs can include the full script, for those MDMs it might be more useful to install it on the client machines, and run it from there. See [Using another MDM than Jamf and you might want a local installation](https://github.com/Theile/Installomator/) By Søren Theilgaard.
### No dependencies
The script started out as a pure `sh` script, and when I needed arrays I 'switched' to `zsh`, because that is what [we can rely on being in macOS for the foreseeable future](https://scriptingosx.com/zsh). There are quite a few places where using python would have been easier and safer, but with the python 2 run-time being deprecated, that would have added a requirement for a Python 3 run-time to be installed. XML and JSON parsing would have been better with a tool like [scout](https://github.com/ABridoux/scout) or [jq](https://stedolan.github.io/jq/), but those would again require additional installations on the client before the script can run.
@@ -141,15 +159,19 @@ The argument can be `version` or `longversion` which will print the script's ver
```
> ./Installomator.sh version
0.1
2021-03-28 10:03:42 version ################## Start Installomator v. 0.5.0
2021-03-28 10:03:42 version ################## version
2021-03-28 10:03:42 version 0.5.0
> ./Installomator.sh longversion
Installomater: version 0.1 (20200506)
2021-03-28 10:04:16 longversion ################## Start Installomator v. 0.5.0
2021-03-28 10:04:16 longversion Installomater: version 0.5.0 (2021-03-28)
```
Other than the version arguments, the argument can be any of the labels listed in the Labels.txt file. Each of the labels will download and install the latest version of the application, or suite of applications. Since the script will have to run the `installer` command or copy the application to the `/Applications` folder, it will have to be run as root.
```
> sudo ./Installomator.sh desktoppr
> sudo ./Installomator.sh desktoppr DEBUG=0
```
(Since Jamf Pro always provides the mount point, computer name, and user name as the first three arguments for policy scripts, the script will use argument `$4` when there are more than three arguments.)
@@ -174,8 +196,9 @@ Then you can use the Installomator script in a policy and choose the application
When it runs with a known label, the script will perform the following:
-when the application is running, prompt the user to quit or cancel
-Check the version installed with the version online. Only continue if it's different
- download the latest version from the vendor
- when the application is running, prompt the user to quit or cancel
- dmg or zip archives:
- extract the application and copy it to /Applications
- change the owner of the application to the current user
@@ -201,22 +224,58 @@ Debug mode is useful to test the download and verification process without havin
The `BLOCKING_PROCESS_ACTION` variable controls the behavior of the script when it finds a blocking process running.
There are four options:
There are eight options:
-`ignore`: continue even when blocking processes are found
-`silent_fail`: exit script without prompt or installation
-`prompt_user`: show a user dialog for each blocking process found abort after three attempts to quit
-`kill`: kill process without prompting or giving the user a chance to save
-`ignore`: continue even when blocking processes are found.
-`silent_fail`: exit script without prompt or installation.
-`prompt_user`: (default) show a user dialog for each blocking process found abort after three attempts to quit (only if user accepts to quit the apps, otherwise the update is cancelled).
-`prompt_user_then_kill`: show a user dialog for each blocking process found, attempt to quit two times, kill the process finally.
-`prompt_user_loop`: Like prompt-user, but clicking "Not Now", will just wait an hour, and then it will ask again.
WARNING! It might block the MDM agent on the machine, as the scripts gets stuct in waiting until the hour has passed, possibly blocking for other management actions in this time.
-`tell_user`: User will be showed a notification about the important update, but user is only allowed to quit and continue, and then we ask the app to quit.
-`tell_user_then_kill`: Show dialog 2 times, and if the quitting fails, the blocking processes will be killed.
-`kill`: kill process without prompting or giving the user a chance to save.
The default is `prompt_user`.
If any process was closed, Installomator will try to open the app again, after the update process is done.
### Notification
The `NOTIFY` variable controls the notifications shown to the user. As of now, there are two options:`success` (default) and `silent`.
The `NOTIFY` variable controls the notifications shown to the user. As of now, there are three options:
-`success`: notify the user after a successful install
-`success`: (default) notify the user after a successful install
-`silent`: no notifications
-`all`: all notifications (great for Self Service installation)
### Logo
The `LOGO` variable is used for the icon shown in dialog boxes. There are these options:
-`appstore`: Icon is Apple App Store (default)
-`jamf`: JAMF Pro
-`mosyleb`: Mosyle Business
-`mosylem`: Mosyle Manager (Education)
-`addigy`: Addigy
Path can also be set in the command call, and if file exists, it will be used, like `LOGO="/System/Applications/App\ Store.app/Contents/Resources/AppIcon.icns"` (spaces are escaped).
### App Store apps handling
Default is `IGNORE_APP_STORE_APPS=no`
__options:__
-`no`: If installed app is from App Store (which include VPP installed apps) it will not be touched, no matter it's version (default)
-`yes`: Replace App Store (and VPP) version of app and handle future updates using Installomator, even if latest version. Shouldn’t give any problems for the user in most cases. Known bad example: Slack will loose all settings.
### Install behavior (force installation)
Since we now make a version checking, and only installs the software if the version is different, an `INSTALL` variable can be used to force the installation:
- ``: When not set, software is only installed if it is newer/different in version (default)
-`force`: Install even if it’s the same version
### Re-opening of closed app
The `REOPEN` can be used to prevent the reopening of a closed app
-`yes`: (default) app will be reopened if it was closed
-`no`: app not reopened
### Adding applications/label blocks
@@ -242,13 +301,25 @@ The display name of the installed application without the `.app` extensions.
The type of installation. Possible values:
-`dmg`: application in disk image file (drag'n drop installation)
-`pkg`: flat pkg download
-`zip`: application in zip archive (`zip` or `tbz` extension)
-`zip`: application in zip archive (`zip` extension)
-`tbz`: application in tbz archive (`tbz` extension)
-`pkgInDmg`: a pkg file inside a disk image
-`pkgInZip`: a pkg file inside a zip
-`appInDmgInZip`: an app in a dmg file that has been zip'ed
-`downloadURL`:
The URL from which to download the archive.
The URL can be generated by a series of commands, for example when you need to parse an xml file for the latest URL. (See `bbedit`, `desktoppr`, or `omnigraffle` for examples.)
Sometimes version differs between Intel and Apple Silicon versions. (See `brave`, `obsidian`, `omnidisksweeper`, or `notion`).
-`appNewVersion` (optional, but recommended):
Version of the downloaded software.
If given, it will be compared to installed version, to see if download is different.
It does not check for newer or not, only different.
Not always easy to figure out how to make this. Sometimes this is listed on the downloads page, sometimes in other places. And how can we isolate it in a genral manner? (See `abstract`, `bbedit`, `brave`, `desktoppr`, `googlechrome`, or `omnidisksweeper`).
-`packageID` (optional, but recommended for pkgs without an app)
This variable is for pkg bundle IDs. Very usefull if a pkg only install command line tools, or the like that does not install an app. (See label `desktoppr`, `golang`, `installomator_st`, `odrive`, or `teamviewerhost`).
-`expectedTeamID`:
The 10-character Developer Team ID with which the application or pkg is signed and notarized.
@@ -273,6 +344,7 @@ Depending on the application or pkg there are a few more variables you can or ne
-`appName`: (optional)
File name of the app bundle in the dmg to verify and copy (include the `.app`).
When not given, the `appName` is set to `$name.app`.
This is also the name of the app that will get reopned, if we closed any `blockingProcesses` (see further down)
-`targetDir`: (optional)
dmg or zip:
@@ -300,11 +372,45 @@ Depending on the application or pkg there are a few more variables you can or ne
`$updateTool $updateArguments`
Will be run instead of of downloading and installing a complete new version.
Use this when the `updateTool` does differential and optimized downloads.
e.g. `msupdate` (see microsoft installations)
e.g. `msupdate` (see various Microsoft installations).
-`updateToolRunAsCurrentUser`:
When this variable is set (any value), `$updateTool` will be run as the current user. Default is unset and
-`CLIInstaller`:
-`CLIArguments`:
If the downloaded dmg is actually an installer that we can call using CLI, we can use these two variables for what to call.
We need to define `name` for the installed app (to be version checked), as well as `installerTool` for the installer app (if named differently that `name`. Installomator will add the path to the folder/disk image with the binary, and it will be called like this:
`$CLIInstaller $CLIArguments`
For most installations `CLIInstaller` should contain the `installerTool` for the CLI call (if it’s the same).
We can support a whole range of other software titles by implementing this.
See label adobecreativeclouddesktop.
-`installerTool`:
Introduced as part of `CLIInstaller`. If the installer in the DMG or ZIP is named differently than the installed app, then this variable can be used to name the installer that should be located after mounting/expanding the downloaded archive.
See label adobecreativeclouddesktop
### Configuration from Arguments
You can provide a configuration variable, such as `DEBUG` or `NOTIFY` as an argument in the form `VAR=value`. For example:
Providing variables this way will override any variables set in the script.
You can even provide _all_ the variables necessary for download and installation. Of course, without a label the argument parsing will fail, so I created a special label `valuesfromarguments` which only checks if the four required values are present:
The order of the variables and label is not relevant. But, when you provide more than one label, all but the _last_ label will be ignored.
Providing all the variables this way might be useful for certain downloads that have a customized URL for each vendor/customer (like customized TeamView or Watchman Monitoring) or are local downloads.
## Frequently Asked Questions
### What if the latest version of the app is already installed?
# remove the temporary working directory when done
printlog "Deleting $tmpDir"
rm -Rf "$tmpDir"
fi
if[ -n "$dmgmount"];then
# unmount disk image
printlog "Unmounting $dmgmount"
hdiutil detach "$dmgmount"
fi
# If we closed any processes, reopen the app again
reopenClosedProcess
printlog "################## End Installomator, exit code $1 \n\n"
exit"$1"
}
runAsUser(){
if[[$currentUser !="loginwindow"]];then
uid=$(id -u "$currentUser")
launchctl asuser $uid sudo -u $currentUser"$@"
fi
}
reloadAsUser(){
if[[$currentUser !="loginwindow"]];then
uid=$(id -u "$currentUser")
su - $currentUser -c "${@}"
fi
}
displaydialog(){# $1: message $2: title
message=${1:-"Message"}
title=${2:-"Installomator"}
runAsUser osascript -e "button returned of (display dialog \"$message\" with title \"$title\" buttons {\"Not Now\", \"Quit and Update\"} default button \"Quit and Update\" with icon POSIX file \"$LOGO\")"
}
displaydialogContinue(){# $1: message $2: title
message=${1:-"Message"}
title=${2:-"Installomator"}
runAsUser osascript -e "button returned of (display dialog \"$message\" with title \"$title\" buttons {\"Quit and Update\"} default button \"Quit and Update\" with icon POSIX file \"$LOGO\")"
printlog "Changing BLOCKING_PROCESS_ACTION to kill"
BLOCKING_PROCESS_ACTION=kill
else
# give the user a bit of time to quit apps
printlog "waiting 30 seconds for processes to quit"
sleep 30
fi
;;
kill)
printlog "killing process $x"
pkill $x
sleep 5
;;
prompt_user|prompt_user_then_kill)
button=$(displaydialog "Quit “$x” to continue updating? (Leave this dialogue if you want to activate this update later).""The application “$x” needs to be updated.")
printlog "Changing BLOCKING_PROCESS_ACTION to kill"
BLOCKING_PROCESS_ACTION=kill
else
printlog "telling app $x to quit"
runAsUser osascript -e "tell app \"$x\" to quit"
# give the user a bit of time to quit apps
printlog "waiting 30 seconds for processes to quit"
sleep 30
fi
fi
;;
prompt_user_loop)
button=$(displaydialog "Quit “$x” to continue updating? (Click “Not Now” to be asked in 1 hour, or leave this open until you are ready).""The application “$x” needs to be updated.")
if[[$button="Not Now"]];then
if[[$i < 2]];then
printlog "user wants to wait an hour"
sleep 3600# 3600 seconds is an hour
else
printlog "change of BLOCKING_PROCESS_ACTION to tell_user"
BLOCKING_PROCESS_ACTION=tell_user
fi
else
printlog "telling app $x to quit"
runAsUser osascript -e "tell app \"$x\" to quit"
# give the user a bit of time to quit apps
printlog "waiting 30 seconds for processes to quit"
sleep 30
fi
;;
tell_user|tell_user_then_kill)
button=$(displaydialogContinue "Quit “$x” to continue updating? (This is an important update). Wait for notification of update before launching app again.""The application “$x” needs to be updated.")
printlog "telling app $x to quit"
runAsUser osascript -e "tell app \"$x\" to quit"
# give the user a bit of time to quit apps
printlog "waiting 30 seconds for processes to quit"
downloadURL=$(redirect=$(curl -sfL https://www.blender.org/download/ | sed 's/.*href="//'| sed 's/".*//'| grep .dmg)&& curl -sfL "$redirect"| sed 's/.*href="//'| sed 's/".*//'| grep -m1 .dmg)
appNewVersion=$(echo"${downloadURL}"| sed -E 's/.*\/[a-zA-Z]*-([0-9.]*)-.*/\1/g')
#Maybe change to GitHub for this title. Looks like 5.28.0 release is the first to also release a binary, so maybe see what the next release will be to decide if we should switch.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Armin Briegel