The Adobe® AIR® runtime enables developers to package the same code into native apps for iPhone, iPad, Kindle Fire, Nook Tablet, and other Android™ devices. On Windows, applications like ‘TweetDeck’ and Adobe’s own Creative Suite uses Adobe AIR for its Adobe Community Help and Adobe Widget Browser. The Adobe® Dreamweaver® Widget Browser is an Adobe AIR® application that lets you preview and configure widgets using a visual interface.
You can download the Adobe AIR runtime installer for Windows here. However, if you would create a Windows Bundle to run this installer, you would need the correct silent switches in order to prevent end users having to manually agree the license agreement:
and to finish the install:
Therefore silent or unattended switches are needed to run this installer ‘silently’, which means without involving the end user in the installation process. Bundle Commander has extensive support for ‘legacy setups’, also called non-MSI (Windows Installer) based setups.
After starting Bundle Commander and connecting it to your ‘ZENworks Configuration Management’ zone, you need to select the ‘AdobeAIRinstaller.exe’. Choose ‘Create Bundle(s)’ from the Ribbon bar, or right click to use the context menu or just double click the installer file. Choose ‘Create Bundle’ and click ‘Ok’:
Bundle Commander extracts the correct ‘Product Name’ and ‘Product Version Number’ from the installer. These two are combined and used to suggest a consistent name for ‘Bundle Name’ and ‘Display Name’. The correct silent switches are provisioned in the ‘command line parameters’ section. If you like to make modifications, you’re able to because these fields are all editable.
If you would like to use ZCM’s content repository, you can the check ‘Upload the selected file …’ checkbox. If you deploy ‘Adobe AIR’ in a locked down environment, where users don’t have local administrator rights, you can opt to set the Executable Security Level accordingly. If you want to assign Users and or Devices to this Windows Bundle, you can use the ‘User Assignments’ and or ‘Device Assignments’ section. Also, the icon of the installer is extracted and added to the Windows Bundle automatically:
Instead of using Adobe’s legacy setup, there’s a second more customizable way of deploying Adobe AIR. The ‘AdobeAIRInstaller.exe’ is basically a compressed file, packaged as a bootstrapper. In this file you can find an uncompressed ‘setup.msi’ which is the actual Adobe AIR setup. The MSI can be extracted by e.g. using WinRAR. This is explained in depth in this MSIwisdom article.
If you select this ‘setup.msi’ in Bundle Commander, select ‘Create Bundle’ and click ‘Ok’:
the ‘Adobe AIR Configuration Wizard’ will be shown. This is one of the many built-in wizards of Bundle Commander:
This wizard allows you to configure three options:
- Preventing installation of AIR applications
If you don’t check this checkbox, installation of AIR applications is allowed.
- Preventing installation of untrusted AIR applications
If you check this option, installation of untrusted AIR applications is not allowed.
- Preventing automatic updates to Adobe AIR
If you check this option, automatic updates of the runtime is not allowed (when required by an AIR application). When an update for Adobe AIR becomes available, it will not be made available via a background update mechanism nor will the end user be notified.
These three settings have already been set by default for ‘best practice’ use considering you want to deploy this application in an enterprise environment. Which means that if you leave the option ‘Preventing automatic updates to Adobe AIR’ checked, your end user will not be shown screens like this when an update for Adobe AIR becomes available:
Of course you have to create a new Windows Bundle yourself, when a new version becomes available. But you probably want to do that anyway, since regular users normally don’t have sufficient rights to install applications nor updates to begin with.
When you click ‘Ok’, you can review the Windows Bundles details. Bundle Commander automatically detects whether a selected MSI is compressed or not compressed. Since the Adobe AIR MSI is compressed, the ‘Include all files in and below the directory of this file’ checkbox is automatically checked. This prevents you from creating Windows Bundles based on uncompressed MSI’s which would fail with a 1603 Fatal Error, because the actual files are missing:
After creating the Windows Bundle, In ZENworks Configuration Center it would look like this:
Instead of naming the Install action ‘Install MSI’, which is the default when you create a Windows Bundle in ‘ZENworks Configuration Center’, the selected MSI filename is included in the name of the ‘Install Action’.
The parameters for ‘msiexec’ are set accordingly: