Recommended Workflow for Deploying a Template to a Fleet

Once a template has been validated and confirmed to be the master template, the following workflow is recommended for deploying it to the fleet. This workflow applies to both MG and ALEOS devices.

1. In the Configuration > Templates window, select the template that you wish to deploy.

2. Select the group in the left hand tree that you wish to apply the template to.

3. Select the Deploy button.

4. In the Summary window, the Perform a version compatibility check should be left as enabled. Enable Automatically upgrade gateway(s) to compatible versions . This option will only show if the devices are running a lower version than the template(s) being applied, or if the device has never checked in before. Specify Yes when prompted to schedule the upgrades . The scheduling panel will display allowing you to set when and how often the AMM will attempt to upgrade.

5. If the draft template has not been published, you have the option to publish it before it is deployed .

6. If there are multiple templates selected, and one template contains removing or renaming actions, then you must enable this option if it is to be deployed . This is so that you acknowledege that there could be conflicts caused by the rename/remove action.

7. Enable the Reboot automatically after changes are applied. .

8. (Optional) Enable the Link the template to the affected gateway(s)/group(s) . 7. Enable the Reboot automatically after changes are applied if you want the AMM to reboot after the templates have been applied. This does not apply to MG devices.

8. (Optional) Enable the Link the template to the affected gateway(s)/group(s) . Caution should be used when enabling this feature, as deploying the template with linked groups/gateways will cause the changes to be immediately pushed out to all linked groups/gateways.

9. (Optional) If deploying a template that will specify unique values per gateway, then select to upload the CSV file.

10. Verify that the Affected Gateways are as expected.

11. Check the Unaffected Gateways to investigate why those will not have the template applied.

12. Select the Submit button.

13. If more than 10 gateways are affected, then a popup with a summary of how many gateways the template(s) is being deployed to, will be shown. Press Submit to confirm deployment or Cancel to cancel the deployment.

Note: Unless the changes are minor, we recommend performing the mass deployment in progressively larger groups, while pausing to perform real-world testing in between each group deployment.

As the operating environment will change continually for a mobile fleet, this will ensure that you catch any issues with minimal impact to your fleet. The number and size of your groups will be determined by the size of your overall fleet.