This article is intended for an experienced Avalanche Package Builder user. It covers best known methods for some of the common questions that are asked.
Silent Installs
There are two methods for creating a package to perform a silent install of cab file/s
Silent Install Method 1: Post-install script (INI file)
Windows CE Devices
[EXECUTE]
CabFiles = Yes
CabCommand = \Windows\wceload.exe
CabParams = /noaskdest /noui "@"
For Windows Mobile Devices
[EXECUTE]
CabFiles = Yes
CabCommand = \Windows\wceload.exe
CabParams = /silent /noui "@"
Silent Install Method 2: Startup command for Auto Run type Package
Sample Startup Command:
\windows\wceload.exe /noaskdest /noui /delete 0 \temp\COFERfClientNew.CAB
*Note that in this example the COFER*.cab is located in the \temp directory on the device.
Additional Notes
1. WCELoad must be installed on the device to achieve silent installation. WCELoad is a separate application, and is typically part of the OS.
2. When using a startup command, you can only install 1 cab file per package since we can only have 1 Startup Command per package.
3. When using the INI file to install and execute cab files, you can have as many cab files as you would like. They will all process and install using the same switches that are in the INI file.
4. You do not have to use WCELoad or its switches for a non-silent install. This means there will be prompts on the device that the user must acknowledge in order to proceed with the installation.
*Additional INI Commands that may be useful, but are not required:
[EXECUTE]
CabMonitorInstall = [Yes | No] disables the installation monitoring. Use [No] for CAB files that reboot the device during installation.
Reboot = [Auto | Yes]
RebootType = [Warm | Cold]
[EXECUTE]
CabMonitorInstall = [Yes | No] disables the installation monitoring. Use [No] for CAB files that reboot the device during installation.
Reboot = [Auto | Yes]
RebootType = [Warm | Cold]
[OMA] XML Provisioning in the INI File
This example demonstrates removing TelnetCE from the device by pushing a uninst.xml, and then running it using the OMA Heading in the INI File:
SAMPLE uninst.xml:
<wap-provisioningdoc>
<characteristic type="UnInstall">
<characteristic type="Wavelink TelnetCE 7363">
<parm name="uninstall" value="1"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
The following screenshots demonstrate how to do this in Package Builder:
Package Information Tab
Package Files Tab
Post Install Script (INI) Tab
Sequencing Packages
Post-install script (INI file) of first package (PackageA) to be installed
Mobile Device Details in Avalanche after PackageA gets installed to the device
Selection Criteria of second package to be installed
Post-install (INI) for PackageB
Additional Notes
1. This process can be used for as many packages as needed, and is useful for sequencing the order that avalanche packages are installed.
2. Be sure to use the ServerReconnect = Yes property in the INI since the device needs to reconnect so that it can report the custom property back to the server.
3. If you do NOT designate “Custom” in the property, then it will default as a general property and report under the ‘General’ tab under device details in Avalanche.