# Defining Execution Settings In Execution Settings, you can choose to apply the configuration during: - Every Refresh Cycle (90 minutes), and/or - When the system starts up (computer configuration) or the user logs in (user configuration). You can also configure the system to deploy the configuration again if it fails and enable notifications to receive updates regarding the current status of the configuration. ## Configuring Execution Settings You can configure execution settings while defining individual configurations or from the configuration's details view. To configure execution settings, specify the following: - [Apply the configuration during every Refresh Cycle](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#everyrefresh) - [Apply the configuration during every logon/start-up](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#everylogon) - [Retry Configuration on Failed Targets](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#retry) - [Enable Notifications](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#notifications) ### Apply the configuration during every Refresh Cycle Vulnerability Manager Plus enables you to apply the configuration during every Refresh Cycle. This option is only available for the following configurations: - [Custom Scripts](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#customscript) - [Shortcuts](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#shortcut) - [Patch Deployment](https://www.manageengine.com/vulnerability-management/help/configuration-management/configuring_execution_settings.html#patch) #### Custom Scripts You can apply the Custom Script configuration during every Refresh Cycle. This will execute the deployed custom script every 90 minutes (Refresh Cycle). #### Shortcut Sometimes, it is necessary to maintain shortcuts for certain important applications in the desktop view. When you enable the option to execute this configuration during every refresh cycle, shortcuts for the selected applications will be created. If a user deletes a shortcut, it will be created again in the subsequent Refresh Cycle. #### Patch Deployment When a computer on your network goes offline and then reconnects to the network, there may be certain patches missing on the computer. Automated patch deployment provides a solution for easily patching systems with missing patches. When the agent contacts the server, it undergoes an automatic scan during the next refresh cycle to detect and update any missing patches on the server. The agent deploys these patches within the deployment window during the subsequent refresh cycle. ### Apply the configuration during every logon/start-up You can apply a configuration every time a user logs into their computer or when their system boots up. #### For User configuration: The configuration will be applied every time the user logs into their computer. The configuration will be applied only to the selected target user on the computer. Enable this option to execute a particular configuration whenever a user logs into their computer. #### For Computer configuration: The configuration will be applied every time the target computer boots up. Enable this option to execute a particular configuration every time the target computer is booted. ### Retry Configuration on Failed Targets You can automate the re-deployment process. This option enables you to do the following: - Specify whether you want the agent to try applying this configuration on computers where deployment of the configuration failed. - Choose the number of times you want the agent to try deploying a configuration. You can also specify how many times, out of the number you specified, you want the configuration to be deployed when: - Users log on - Computers complete the 90-minute refresh cycle Based on the specified input, configurations will be re-deployed on the computers until deployment is successful or the retry limit is 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 set the number of times it should be retried during the refresh cycle to 7, the number of times it should be retried during login or startup will automatically be set to 1. ### Enable Notifications Specify the email address if you want to receive email notifications. These notifications begin when the status moves to "Ready to Execute." You can also set a frequency for notifications to be sent. A notification will be sent only if there is a change in status from the previous notification. For example, you have deployed a configuration to 10 target computers. The notification settings are configured to "Notify via email every 2 hours for 3 days." The configuration moves to Ready to Execute status at 10:00 on day 1. The first notification will be sent at 12:00. Assume none of the computers were reachable during this interval. The notification email will state that the configuration is yet to be deployed and the reason is that agents are not reachable. The second notification should be sent at 14:00. However, if none of the computers are still reachable and there is no change in status from the previous notification, the second notification will not be sent. Assume 5 computers become reachable at 15:00. The subsequent notification will be sent as scheduled at 16:00 with the status of the configuration.