Adobe has transitioned "ongoing platform support and feature development of ADOBE AIR to HARMAN":
Adobe will provide basic security support – limited to security fixes only for desktop platforms (Windows 7 and above, and Mac OS X) – for Adobe AIR v32 until the end of 2020. After that time, Adobe support for AIR will be discontinued and ongoing support will be managed by HARMAN and communicated by them directly. However, beginning with the release of AIR v33 by HARMAN, developers should contact HARMAN directly for AIR support on both mobile and desktop platforms – including bug fixes, platform compatibility, and new and improved functionality.
Similar statement has been provided for Adobe Flash Player:
Adobe Flash Player reached its end of life on December 31, 2020. At this point companies should be removing the historically highly targeted application from their environments if you have not already done so. If you need to continue running Flash for any specific reason it should be specific exceptions in controlled circumstances. Also, Adobe has worked with Harman to transition extended support for enterprise customers. You should reach out to Harman for additional services or coverage past the end of life date. For details see the Flash Player Enterprise End-of-Life page: https://www.adobe.com/products/flashplayer/enterprise-end-of-life.html
Currently Patch Management Solution does not offer HARMAN as a vendor; hence, a customer cannot patch through Patch Management Solution the endpoints that need an update after Adobe AIR 31.
ITMS 8.5, 8.6
At this point Patch Management Solution doesn't have Harman as one of the provided vendors.
In the meantime, you could use Software Delivery to deliver the files to a managed computer. This is the best guidance that we can provide without going to customization realm:
Workaround. Create a Software Package by Importing the desired files as a new Software Package; then create a Managed Software Policy to deploy the Software Package, and finally create a Target of vulnerable systems.
Steps to complete the Workaround: