Distributing settings using MDMs

If you have mobile device management (MDM) software, such as Ivanti Avalanche, use it to distribute Velocity deployment files to the Velocity Client. The methods may vary depending on the MDM you are using and the operating systems on your devices.

If you have Ivanti Avalanche, you can deploy a project directly from the Velocity Console to the Avalanche Central File Store. Then from Avalanche, deploy a file payload or a Velocity configuration file to devices.

If your Android devices are running a version of Android older than version 10, in most cases the MDM can distribute the deployment files directly to the com.wavelink.velocity directory in the first external storage partition. However, if the devices are running Android 10, they must be an Android Enterprise managed device in order to distribute the deployment files to it.

Android 10 considerations

If you have devices running Android 10, the Velocity app can only be configured using an MDM when the device is an Android Enterprise managed device, the deployment files are hosted on a web server, and you create a managed configuration and a manifest file.

If you use Ivanti Avalanche, create the manifest file easily from the Avalanche Console. The Avalanche Console also provides the URL and trust information for the manifest file. See the section below for more information.

To configure Velocity on Android 10 using an MDM

1.Create the deployment files (.wldep, .wlxgp, or .wlvpk) from the Velocity Console.

2.Create a manifest file that lists the deployment files each client should retrieve. The manifest file should be a text file with the extension .wlcfg and use the following format:

{

"files": [

{"name":"profile1.wldep"},

{"name":"profile2.wldep"},

{"name":"global.wlxgp"}

]

}

3.Host the deployment files and manifest file on a web server.

4.In the managed configuration settings for the Velocity client, in the Fetch Configurations field, provide a URL for the manifest and, if needed, authentication information for SHA1 or SHA256 certificate. For example:

{"manifest":"https://10.10.10.10:9999/velocity/manifest.wlcfg","trust":"sha1:a69cfdb0580da4eeae9a477524c30b9f5db61c77","authorization":"Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkqIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5cl"}

Deploying projects to devices using Avalanche

To distribute projects to devices using Avalanche, first deploy the projects to the Central File Store. Then, for devices with older versions of Android, you can use a File payload to distribute projects. To distribute projects to devices using Android 10 or newer, make sure the devices are enrolled in Android Enterprise and then create a managed configuration file and a manifest.

You must have Velocity 2.1.8 or newer and Avalanche 6.3 in order to deploy projects ( .wldep or .wlxgp ) directly to Avalanche. (Speakeasy files are not included when you deploy to Avalanche.) First, set up Velocity with Avalanche credentials and the path to the Central File Store. Then, when you do a deployment, the Velocity Console copies the deployment file to the Avalanche Central File Store. Each deployment from the same project overwrites the existing file and is associated with the file payload. Deploying from Velocity does not trigger an Avalanche deployment.

For devices that are running Android 10 or newer: the devices must be Android Enterprise devices, the deployment files must be hosted on a web server, and you must also create a managed configuration and a manifest. Avalanche sends the configuration file to the device, and the Velocity Client reads the file to know where the Central File Store is, how to authenticate, and which manifest file to use. Then the manifest file tells the client which deployment files to retrieve.