What's New in This Version
•QR code provisioning for Android Enterprise. Use QR code provisioning to send Wi-Fi and enrollment information from an enrolled fully managed Android Enterprise device to new devices. For more information, see QR Code Provisioning from the Enabler.
•NFC provisioning for Android Enterprise. Use NFC provisioning to send Wi-Fi and enrollment information from an enrolled fully managed Android Enterprise device to new devices. For more information, see NFC Provisioning.
•Fully managed mode for Android Enterprise. Fully managed device mode offers extensive control over device policies, settings, and applications of Android Enterprise devices. For more information, see Fully Managed Mode.
•Dedicated device mode for Android Enterprise. Dedicated device mode locks devices to a single app or set of apps. Dedicated device mode (also known as kiosk mode) is a subset of fully managed mode. To put a device into dedicated device mode, enroll it as a fully managed device then use a restrictions payload to enable kiosk mode. For more information, see Restrictions Payload.
•Android Enterprise payloads. New Android Enterprise payloads include the file payload, restrictions payload, system update payload, and Wi-Fi payload. For more information, see Smart Device Payloads.
•Scan to enroll for Android Enterprise. Create QR codes from enrollment rules to easily enroll Android Enterprise devices. For more information, see Scan to Enroll.
•Subscription licenses. Subscription licenses support Avalanche version 6.3 and newer. For more information, see Licensing.
•Smart device logs in the console. Request device logs from Android Enterprise devices and view them in the Avalanche console. For more information, see Managing Smart Device Logs.
•Ivanti UserVoice for Avalanche. Use the Ivanti UserVoice feedback system to suggest and vote for new Avalanche features. Access Ivanti UserVoice from the link in the Tools menu or by visiting Ivanti UserVoice for Avalanche.
•New UI in the console. To improve performance, new options have been added to the management tabs, and smart device profiles and payloads have an updated design.
•Distributing Velocity configurations. Use Avalanche to distribute Velocity configuration files to your Android devices. For more information, see Distributing Velocity Configurations.
•OEM configuration support. Use OEM configurations to gain access to device management settings that are not available through typical software management, such as manufacturer specific device settings and functions. For more information, see OEM Configurations.
•Work profile mode for Android Enterprise. Android Enterprise offers secure management of Android devices through a selection of different management modes. Use Avalanche to create work profiles on devices, set password restrictions, set app permissions, and configure and deploy enterprise approved apps to devices. For more information, see Getting started with Android Enterprise .
•Firebase Cloud Messaging support. Firebase Cloud Messaging (FCM) enables Avalanche’s smart device server to establish communication with your Android devices. For more information, see Configuring FCM for Android.
•APN payload for Android. Specify the carrier access point that Android devices use to connect to a cellular network. For more information, see APN Payload.
•Prerequisite software settings for manifest URL software payloads. Specify apps that must be installed before installing a manifest URL software payload. For more information, see Software Payload.
•Panasonic OS updates. You can now create OS update payloads for Panasonic devices. For more information, see OS Update Payload.
•Improved encryption. When installing or upgrading to Avalanche 6.2.2, confidential information in the Avalanche database is encrypted with a new key that will be stored outside the database. This means the encryption key must be backed up separately from the databases. For more information, see Backing Up the Database Encryption Key
•SDS scalability. Install and manage multiple smart device servers.
•Smart device server profiles. Use profiles to configure smart device servers. For information about the settings in a smart device server profile, see Creating and Configuring a Smart Device Server Profile.
•Central File Store. Use the Central File Store to manage files that are distributed to devices. For information about setting up and using the Central File Store, see Using the Central File Store.
•Reference enrollment rules. A reference enrollment rule is not tied to a specific device server, so when a device uses the enrollment rule, it is placed in a folder relative to the device server that it connects to. For more information about types of enrollment rules, see Creating Enrollment Rules for Smart Devices.
•Time zone and NTP server payload for Android. Set the time zone for devices, or configure them to use an NTP server. For more information, see Time Settings Payload.
•Integrated Remote Control with Splashtop. When you have Splashtop set up, clicking the Splashtop Launcher button in the Device Details page starts a remote control session. For more information, see Remote Control for Android Devices.
•Support for Zebra Mobility Extensions (Mx). If you use Zebra Mx, Avalanche can distribute the Mx files so the configurations are applied. Name the file avamxmf.xml, create a file payload, and use the file path /sdcard/Ivanti/MXMF.
Avalanche 6.1 SP3
•Custom properties. You can create custom properties for Android devices both from the Device Details page as well as through Custom Properties Payload for use in filtering and selection criteria. You can also create a file for device-side properties.
•Android bulk enrollment. You can create a configuration file for Android devices with your server's enrollment credentials and then upload it to your devices. When the Avalanche Enabler app is launched on the device, it automatically enrolls and adds the device to your inventory.
•Support Bluetooth properties. When a device with paired Bluetooth devices is synced with Avalanche, any such Bluetooth pairings appear as properties from the Device Details screen.
•Configurable file location. When creating a file payload, you can set the location of where to put files on managed devices.
•Blackout support. By adding a file to Android devices, you can prevent Avalanche from syncing new profile settings and payloads on the device. This is especially helpful when devices are in use, as such syncs could impact employee productivity.
•LDAPS authentication. SSL encryption (LDAPS) is an available option when selecting LDAP authentication from System Settings.
•Force device reboot, invoke applications, and resync. When creating a smart device profile, you can force devices to reboot when they receive the associated payloads, or to invoke (launch) an application installed as part of a software payload. Once payloads associated with the profile are applied to the device, the behaviors are enforced. You can also select the option to force devices to resync upon a successful sync, to ensure all profile settings are received.
Avalanche 6.1 SP2
•OS update payload. Send a compressed file to enrolled Zebra Android devices for download and installation. From this payload, you can specify where update files are hosted and when they should be downloaded or installed. For more information, see OS Update Payload.
Avalanche 6.1 SP1
•EAP-TLS support added. Another method of wireless LAN authentication is now available, utilizing certificates on both the device and server to establish a secure connection. This feature requires the Wavelink Certificate Management Server. For more information, see Configuring Network Profiles.
•Silently install certificates on WinCE devices. Whereas before, device users were prompted to accept a certificate when it was first installed, this alert has now been removed and all devices using WinCE will silently install certificates with no user interaction.
•PKCS#12 certificates are supported for Remote Control. PKCS#12 certificates no longer need to be exported to the keystore.jks format for use with Remote Control. The .p12 format is fully supported for immediate use. For more information, see Obtaining SSL Certificates.
•Wi-Fi Payload changes. When a Wi-Fi payload is unapplied from a device, the settings are not deleted from the device and must be removed manually or through a selective wipe. For more information, see Wi-Fi Payload.
•Request Immediate Check In is not selected by default. When deploying payloads to assigned devices, the task scheduler no longer forces devices to check in by default. This option must be manually selected. For more information, see Deploying Changes.
•Increased File payload sizes. Files attached to this payload can now be as large as 5MB. For more information, see File Payload.
•Software payload changes. When multiple software payloads are deployed with a different version of the same application, the newer software payload will overwrite the existing one, but it will not alter any existing app configurations on the device.
•Certificate management. Integrate Avalanche with Microsoft SCEP and automatically track, request, and renew certificates stored on managed AIDC mobile devices. After adding certificate management server details to the System Settings screen and your Network and Mobile Device profiles, Avalanche automatically distributes any hosted certificates and distributes certificate requests directly to your certificate management server.
•Android Device File payload. Send files directly to managed Android devices. This new payload allows you to upload a single file and mass deploy it to devices with external SD cards. For ruggedized Motorola Android devices, if an external SD card cannot be found, the file is stored locally on the device. For more information, see File Payload.
•Android Wi-Fi priority. Avalanche-deployed Wi-FI payloads have a higher priority over manually-configured and auto-scanned Wi-Fi settings on the device. Devices with a Wi-Fi payload will attempt this connection first before attempting any other networks. For more information, see Wi-Fi Payload.
•Dynamic folder assignment. Set the default Mobile Device Profile to dynamically assign devices to different regions and folders each time a mobile device syncs. If the device properties change between syncs, the AIDC device is moved to the new folder automatically and inherits all new payloads. For more information, see Using Selection Criteria.
•LDAP Avalanche sign-in. Sign in to the Avalanche Web Console using your LDAP credentials. Provide the credentials for LDAP Integration Services on the System Settings page to enable this. For more information, see Configuring General System Settings.
•Silent Android Enabler installation and updates. Updating and installing the Android enabler on MC Android devices through the Software Payload occurs silently without notification or user interaction.
•Motorola MC device scanner options. Configure scanner decoding and barcode settings for MC40 devices using Wavelink Terminal Emulation. For more information, see TE Client Settings Payload.
•External SD card encryption. Encrypt and decrypt external SD cards on Samsung SAFE devices to protect the integrity of company data. For more information, see Restrictions Payload.
•Wavelink Productivity Pack Configuration payload. Deliver custom keyboard bundles to devices using Wavelink Terminal Emulation. For more information, see Productivity Pack Configuration.
•Silent app install on Samsung SAFE devices. Push an app to the device and have it install without device user interaction. For more information, see Software Payload.
•Samsung SAFE Exchange payload. Send information to Android devices about the Exchange server so users can access their email accounts. For more information, see Exchange / ActiveSync Payload.
•Samsung SAFE network restrictions payload. Restrict network access for an Android device’s default browser. This includes whitelisting, blacklisting, or redirecting traffic. For more information, see Network Restrictions Payload (Samsung SAFE).
•Updated restrictions payload for Android devices. New restriction options for Samsung SAFE devices. This includes restricting the Play Store, uninstalling apps, or more granular control over specific apps. For example, you could restrict one app from using NFC but allow NFC for other apps. For more information, see Restrictions Payload.
•Wavelink Studio configuration payloads. Configure host profiles, SSL certificates, and other settings for Studio Clients installed on iOS devices. For more information, see Studio Host Profile Configuration Payload, Studio Client Settings Payload, or Studio SSL Certificate Payload.