In Execution Settings, you can choose to apply the configuration during
You can also configure to deploy the configuration again in case it fails and enable the notification option to receive updates regarding the current status of the configuration.
You can configure the execution settings while defining the individual configurations or from the configuration's details view. To configure execution settings you will have to specifty the following:
Desktop Central enables you to apply the configuration during every Refresh Cycle. This option is only available for the following configurations:
Desktop Central enables you to apply the Custom Script configuration during every Refresh Cycle. This will essentially execute the deployed custom script every 90 minutes (Refresh Cycle).
Sometimes, it is necessary to maintain the shortcuts of certain important applications in the desktop view. When you enable the option to execute this configuration during every refresh cycle,the shortcuts of the selected applications will be created. If a user deletes a shortcut, the shortcut will be created again in the subsequent Refresh Cycle.
Note:1) When creating a software package, you must configure a pre-deployment activity to check whether the software has already been installed on a particular computer. This will indispensably eliminate the process of installing the software repeatedly. Learn more about Pre-deployment Activity.
2)The Deployment schedule configured in the Deployment Policy is not applicable for deploying software, if the one or more of the following options are enabled:
1) Apply the configuration during every Refresh Cycle
2) Apply the configuration during every logon/start-up
Some software applications have to be available at all times in an orgranization to eliminate any productivity loss contributed by their deletion. This configuration essentially equips the administrator to automatically deploy the software if it has been uninstalled from a particular computer.
Desktop Central enables you to apply a configuration every time a user logs into their computer or when their system boots up.
The configuration will be applied every time the user logs into their computer. The configuration will be applied only to the selected target user in the computer. Enable this option to execute a particular configuration whenever a user logs into their computer.
The configuration will be applied every time when the target computer boots up. Enable this option to execute a particular configuration every time the target computer is booted.
Desktop Central enables you to automate the redeployment process. This option enables you to do the following:
Based on the specified input, configurations will be re-deployed on the computers till the deployment is successful or the retry limit has reached.
You can break up the number of times you want deployment of the configuration to be retried into the number of times you want it retried during logon or startup and the number of times you want it retried during the refresh cycle. Neither option can be set to zero. For example, if you want an option to be retried 8 times and you set the number of times it should be retried during the refresh cycle to 7, the number of times is should be retried during login or startup will automatically be set as one.
Specify the email address, if you wanted to receive email notifications. These notifications will begin when the status is moved to "Ready to Execute". You can also set a frequency for the notifications to be sent. Notification will be sent only if there is any change in the status, from the previous notification. The example below will brief you in detail:
You have deployed a configuration to a target of 10 computers. The notification settings has been configured to "Notify via email every 2 hours for 3 days". The configuration has been moved to Ready to execute status at 10.00 hours. on day 1. The first notification will be sent at 12.00 hours. Assume none of the computers were reachable during the time interval. The notification mail will be sent stating that the configuration is yet to be deployed, and the reason as Agents not reachable.
The second notification should be sent at 14.00 hours, however still none of the computers are reachable, and there is no specific change in the status from the previous notification, then the second notification will not be sent.
Assume 5 computers were reachable at 15.00 hours, then the subsequent notification will be sent as per schedule at 16.00 hours with the status of the configuration.