@erefneb commented on GitHub:
More info... When you run Installomator.sh microsoftedge And then right away run /Library/Application\ Support/Microsoft/MAU2.0/Microsoft\ AutoUpdate.app/Contents/M…
@scriptingosx commented on GitHub:
@PezzaD84 or you could add INSTALL=force to make Installomator not use the updater...
@scriptingosx commented on GitHub:
I would recommend adding INSTALL=force to the business pro installomator run to bypass the update tool
@PezzaD84 commented on GitHub:
I have found an issue with this as well. If a microsoft app is installed then installomator tries to use autoupdate to update the app but it just hangs. I have…
@scriptingosx commented on GitHub:
add INSTALL=force as an extra argument to the script in the policy
@PezzaD84 commented on GitHub:
Where do you specify that in a jamf policy?
@PezzaD84 commented on GitHub:
Awesome thanks for the help!
@brentley commented on GitHub:
The current version URL shows us a version later than what the download page serves up:
curl https://armmf.adobe.com/arm-manifests/mac/AcrobatDC/reader/curre…
@scriptingosx commented on GitHub:
There were several fixes regarding adobe labels in V10.0. Can you say if this fixes it?
@brentley commented on GitHub:
This appears to be corrected with Adobe's release today.
@kMikaZu commented on GitHub:
Here it's not the download but a 1636 error. Looks like this is an installer issue because the same thing happens when running a downloaded installer.
@kMikaZu commented on GitHub:
Well, I found the culprit for the setup I was maintaining. Switched to JAMF Patch Management and turned out the Adobe Acrobat installer triggers the antivirus Trend…
@kclose3 commented on GitHub:
One change of note is that Acrobat Reader is now simply "Adobe Acrobat Reader" rather than "Adobe Acrobat Reader DC" as is specified in the Installomator script.…
@kclose3 commented on GitHub:
On top of everything else, it appears Installomator is pulling an old version of Acrobat Reader. I manually deleted Acrobat from my test computer and ran the…
