Patch Management for Adobe Air
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on
06-15-2018
11:30 AM
- last edited on
03-04-2025
01:57 AM
by
kh-richa_mig
Hello from Texas,
I apologize if this question has been answered somewhere else. I am in need of some guidance/help concerning packing and patching management of AirAdobe Air.
I am new to packaging in general, and Adobe Air seems to be one of the only packages where it appears that there is a .dmg within a .dmg (Inception style).
My question is what would be the best way to package Adobe Air for Patch management?
Any help and even guides are much appreciated.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-15-2018 11:49 AM
If you haven't discovered it yet, run, do not walk, to Google and start reading about AutoPKG. (and sidekick AutoPkgr) It may become your best friend.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-15-2018 01:13 PM
They have a script for updating Adobe Air you can set to run on a schedule or as needed.
https://www.jamf.com/jamf-nation/third-party-products/files/846/adobe-air-installer-updater
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 04-09-2019 03:37 PM
The current script only updates major version numbers like from 31.x to 32.x, but does not update minor version like from 32.0.0.89 to 32.0.0.116. Does anyone have a solution for this?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-27-2020 10:27 AM
@mojo21221 I am facing below script failure issue any idea what need to be changed, I tried couple of URL change for download the AIR but still the same issue.
Script result: Latest Version is: 32.0
Current installed version is: 30.0
Latest version of the URL is: https://airdownload.adobe.com/air/mac/download/32.0/AdobeAIR.dmg
Updating to 32.0.0.125
done
grep: AIR: No such file or directory
2020-08-27 07:57:05.150 defaults[17153:534400]
The domain/default pair of (/Applications/Utilities/Adobe, AIR) does not exist
Error running script: return code was 1.
Running Recon...
Retrieving inventory preferences from https://zebra.jamfcloud.com/...
Locating accounts...
Locating package receipts...
Searching path: /System/Applications
Locating software updates...
Locating plugins...
Locating printers...
Searching path: /Applications
Locating hardware information (Mac OS X 10.15.6)...
Gathering application usage information...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-27-2020 10:58 AM
I would begin the transition on Adobe AIR. As of the end of the year, Adobe is getting out of the development of that and turning it over to others: https://blog.adobe.com/en/2019/05/30/the-future-of-adobe-air.html#gs.e0w0v4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-27-2020 11:07 AM
Thanks for response @blackholemac . Do we need to change the URL or anything else which I may not be aware off. I downloaded and used the script from jamf thirparty software.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-21-2020 01:22 PM
Our environment started recently throwing errors as well. The script is returning empty string for latestver variable. I assume its because of changes to their adobe air site.
#!/bin/sh
## CHANGED FROM
latestver=`/usr/bin/curl -s -A "$userAgent" https://get.adobe.com/air/ | /usr/bin/grep "<strong>Version" | /usr/bin/sed -e 's/<[^>][^>]*>//g' -e '/^ *$/d' | /usr/bin/awk '{print $2}'`
## CHANGED TO
latestver=`/usr/bin/curl -s -A "$userAgent" https://get.adobe.com/air/ | /usr/bin/grep ">Version" | /usr/bin/sed -e 's/<[^>][^>]*>//g' -e '/^ *$/d' | /usr/bin/awk '{print $2}'`
Seems like the script was grabbing the version number by using grep to find <strong>Version. Site looks a bit different and has a different tag. Making this change got rid of the errors since the old version just returned empty.
