Run a Configuration Task

The configuration task will run based on the selected task type. To run the task, the following conditions must be met.

If the task type is Apply or Check, the configuration task must have at least one template and one target device or group.
If the task type is Reboot, the configuration task must have at least one target device or group.

Run the configuration task by clicking the [Run] button after selecting the task. If the task is successfully queued, you will see the following message.

Please make sure the target devices are not powered off while the configuration is in progress.

If you encounter problems when running the configuration task, please refer to Troubleshooting tips.

You can find the results in Device Properties then Activity Logs.

In the Activity logs, look for the configuration task name and select to see the details of the task execution.

The results vary based on the task type selected. Please check the action applied depending on the task type selected.

Task Type	Action
Check Template	If the selected task type is Check, the settings in the template will be compared to the settings in the device. The 'Check' result of one setting will either be: Match - This indicates that the value of the template's setting is the same as the device's setting. Does not match - This indicates that the values of the setting in the template and the device are different. Skip - This indicates that the template's setting is not found in the device. For example, the target device does not support Fax, but the template contains Fax-related settings. The Fax settings in the template will be skipped.
Apply Template	If the task type is Apply, the template's settings will be compared and applied to the device. Please note that only the settings whose value does not match the device will be applied. If the setting's value in both templates and devices is the same, it will not be re-applied. The 'Apply' result of one setting will either be: Match - This indicates that the value of the template's setting is the same as the device's setting; therefore, there is no need to apply the same value to the device. Success - This indicates that the setting's value is applied successfully to the device. Fail - Fails to apply the template setting's value to the device. Device errors, connection errors, or incorrect access accounts can cause this failure. Please check the description of the error in the activity logs. Skip - This indicates that the template's setting is not found in the device.
Reboot Device	If the task type is Reboot Device, the target devices will reboot with the possible result: Success - This indicates that the device successfully restarted. Fail - This means that the device reboot is unsuccessful. Please see the activity log for the description of the error. When running a Reboot(restart) task, two results will be shown in the Activity Logs. The first result says "Task Apply" indicating that the reboot request is submitted. Second result is "Task Reboot" which mean, the device is rebooting/ restarting.

Task Type

Action

Check Template

If the selected task type is Check, the settings in the template will be compared to the settings in the device. The 'Check' result of one setting will either be:

Match - This indicates that the value of the template's setting is the same as the device's setting.
Does not match - This indicates that the values of the setting in the template and the device are different.
Skip - This indicates that the template's setting is not found in the device. For example, the target device does not support Fax, but the template contains Fax-related settings. The Fax settings in the template will be skipped.

Apply Template

If the task type is Apply, the template's settings will be compared and applied to the device. Please note that only the settings whose value does not match the device will be applied. If the setting's value in both templates and devices is the same, it will not be re-applied.
The 'Apply' result of one setting will either be:

Match - This indicates that the value of the template's setting is the same as the device's setting; therefore, there is no need to apply the same value to the device.
Success - This indicates that the setting's value is applied successfully to the device.
Fail - Fails to apply the template setting's value to the device. Device errors, connection errors, or incorrect access accounts can cause this failure. Please check the description of the error in the activity logs.
Skip - This indicates that the template's setting is not found in the device.

Reboot Device

If the task type is Reboot Device, the target devices will reboot with the possible result:

Success - This indicates that the device successfully restarted.
Fail - This means that the device reboot is unsuccessful. Please see the activity log for the description of the error.

When running a Reboot(restart) task, two results will be shown in the Activity Logs. The first result says "Task Apply" indicating that the reboot request is submitted. Second result is "Task Reboot" which mean, the device is rebooting/ restarting.

Troubleshooting tips

The Configuration task should return a success result. If it fails, please see some troubleshooting tips below.

Please ensure the device Access Accounts match the device settings.

The SNMP, SDK/J, and Device Administrator access accounts must match the device's settings. Please see Access Profiles and Accounts for more details.
Please ensure that the device has a stable internet connection. This is a factor when deploying embedded tasks to several devices; ensure the device is online.
Check if the DM Agent is working.

One of the ways to know if your device can communicate to the CloudStream DM via DM Agent is by checking the poll time. You can check the Last Communication Time in the Device Properties, then the Main Properties section. The time must be relevant to the set polling interval. If the last communication time passed the polling interval, there is a possibility that your DM agent is not working; thus, no device information was fetched. Please see Device Polling. In such a case, please re-install the DM Agent via the DM Agent Deployment Tool.