
2 - 4
Part 1 – Bootstrapping the RMU
1. Install the RMUCEbt package into the Avalanche MC Console. Do NOT include the Reboot option as part of
the configuration (i.e., the Reboot button in the “Reboot Options” branch must be unbolded).
2. Enable ONLY the RMUCEbt package in the Avalanche MC Console and update the devices. The RMU is
downloaded and automatically installed.
3. Disable the RMUCEbt package in the Avalanche MC Console.
4. For each device, double-click on the device to open the Client Controls dialog box.
5. Check the Delete Orphaned Packages checkbox and click the Update Now button.
6. After the sync completes, uncheck Delete Orphaned Packages and close the dialog box.
Part 2 – Installing Packages
1. Enable the RMUCE package in the Avalanche MC Console.
2. Enable all remaining packages and send them down. It is important that you include the new OS package in
this group (be sure to include the Enabler). If the radio is to be managed remotely, it is important to include
the radio package in this group so that after the reboot the radio can automatically associate. If the radio
package is not sent, the device loses connection to the network and manual configuration of the radio param-
eters is required.
3. Set the Reboot setting for the OS package to Auto.
4. After all packages are downloaded (this may take several minutes) the Remote Management Utility (RMU) is
launched. The RMU processes all the downloaded packages. If the radio package was downloaded, the
Wireless Configuration Application (WCA) is launched to process the new radio settings.
5. After the RMU finishes installing all the packages, the device is automatically coldbooted (assuming the
Reboot setting was set to Auto in Step 3).
6. After the Device completes the coldboot, the RMU is autoinstalled by the OS and the previously downloaded
packages are restored. Assuming at least one package has registry settings that were restored, and that
package was set to reboot (either auto or prompt), the RMU then performs an automatic warmboot.
7. After the warmboot, the device is configured.
8. If the device will no longer be monitored by Wavelink Avalanche, you may remove the Enabler to eliminate
boot up delays, if desired. Even if the Enabler is removed, the installed packages and their configurations
continue to be restored with every reboot by the RMU.
Version Information on Mobile Devices
The VersionInfo.EXE file is included in the Remote Management Utility package downloaded to the mobile device.
It is stored in the \Program Files\RMU folder. When VersionInfo.EXE is opened, a dialog box is presented to the
device user displaying:
• Remote Management Utility (RMU) version
• Wireless Configuration Application (WCA) version
VersionInfo displays the version for each utility only after that utility has been executed at least once.
User Interface
The Enabler can be configured and controlled manually through the user interface on the mobile device. This section details the
functionality that can be controlled by the user or system administrator.
Parameters and Screen Displays
Screen displays shown in this section are designed to present the end-user with information graphically.
Placement of information on the screen displays may be split between one or many tabbed panels.
Standard Avalanche Enabler parameters that are not supported by Honeywell may be missing or dimmed (visible but
unable to be edited) on the tabbed panels or screen displays.
Komentáře k této Příručce