# Managing Configurations and Collections Clicking on the **Configurations** tab will list the details of the configurations and collections that are defined using Endpoint Central. You can view the details of the configurations by clicking the corresponding configuration name. Apart from viewing the configuration details, you can perform the following actions: - [Modify the Configuration/Collection](https://www.manageengine.com/products/desktop-central/help/managing_configurations_collections.html#Modifying-the-Configuration/Collection) - [Suspend a Configuration/Collection](https://www.manageengine.com/products/desktop-central/help/managing_configurations_collections.html#Suspending-the-Configuration/Collection) - [Resume a suspended Configuration/Collection](https://www.manageengine.com/products/desktop-central/help/managing_configurations_collections.html#Resuming-the-Suspended-Configuration/Collection) ## Viewing Status of Configuration/Collection To view the status of the defined configuration/collection, follow the steps given below: 1. Clicking on the **Configurations** tab will list the details of the configurations and collections that are defined using the product. 2. The status column provides the current status of the configuration/collection. The table given below lists the various states of the configuration/collection and its description: | Status | Description | |---|---| | ![](https://www.manageengine.com/products/desktop-central/help/images/status_draft.jpg) Draft | Represents the configurations/collections that are saved as draft. | | ![](https://www.manageengine.com/products/desktop-central/help/images/status_ready_to_deploy.jpg) Ready To Execute | Represents the configurations/collections that are ready for execution. This will be the initial state of the deployed configurations/collections. Configurations will be **"Ready to Execute"** status in the following scenarios:

- While the patch/software is scheduled to be deployed during system startup.
- If it is specified in Deployment Settings, patches/software will be deployed only during the **Install Between** time.
- If it is specified in Deployment Settings, patches/software will be deployed during the **Install Between** time after the next **system startup**.
- If it is specified in Scheduler Settings, patches/software will be deployed only during the **Install After** time. | | ![](https://www.manageengine.com/products/desktop-central/help/images/status_inprog.jpg) In Progress | Represents that the configuration is applied on one or more targets. Will continue to remain in this state until the configurations are applied to all the defined targets. | | ![](https://www.manageengine.com/products/desktop-central/help/images/status_suspend.jpg) Suspended | Represents that the configuration/collection has been suspended. | | ![](https://www.manageengine.com/products/desktop-central/help/images/status_executed.jpg) Executed | Represents that the configuration/collection has been applied to all the defined targets. | | ![](https://www.manageengine.com/products/desktop-central/help/images/delete.jpg) Failed | Represents that the attempt to deploy the configuration has failed. | | ![](https://www.manageengine.com/products/desktop-central/help/images/delete.jpg) Draft Download Failed | Represents that one or more patches / service packs defined in the configuration could not be downloaded from the Microsoft Website. | | ![](https://www.manageengine.com/products/desktop-central/help/images/config_status_retry_in_progress.png) Retry in Progress | Represents that the product is currently retrying to deploy the configuration. | 3. To view the status of the configurations on individual targets, click the configuration name. ## Modifying the Configuration/Collection To modify a configuration/collection, follow the steps given below: 1. Clicking on the **Configurations** tab will list the details of the configurations and collections that are defined using the product. 2. All the configurations and collections that are defined are listed here. Click the ![](https://www.manageengine.com/products/desktop-central/help/images/modify.jpg) icon from the Actions column of the corresponding configuration/collection. 3. Change the values as required. 4. Click **Deploy**. ## Suspending the Configuration/Collection To suspend a configuration/collection, follow the steps given below: 1. Clicking on the **Configurations** tab will list the details of the configurations and collections that are defined using the product. 2. All the configurations and collections that are defined are listed here. Click the ![](https://www.manageengine.com/products/desktop-central/help/images/status_suspend.jpg) icon from the Actions column of the corresponding configuration/collection that has to be suspended. | ![](https://www.manageengine.com/products/desktop-central/help/images/note.jpg) | **Note:** **Configurations that have been applied to targets prior to suspension will not be reverted. Suspending a configuration will only stop further deployments.For example, suppose we are deploying a configuration to 10 endpoints in your remote office. If you click Suspend immediately after deploying the configuration to one endpoint, the configurations will not be deployed to the remaining 9 endpoints. To resume the deployment, you need to click Resume for the configuration to be deployed in all the other 9 endpoints.** | |---|---| ## Resuming the Suspended Configuration/Collection To resume a suspended configuration/collection, follow the steps given below: 1. Clicking on the **Configurations** tab will list the details of the configurations and collections that are defined using the product. 2. All the configurations and collections that are defined are listed here. Click the ![](https://www.manageengine.com/products/desktop-central/help/images/resume.jpg) icon from the Actions column of the corresponding configuration/collection that has to be resumed. ## /Moving the Configuration to trash/Collection By clicking on Moving the Configuration to trash, the configuration will be moved to trash. For example: Suppose you are deploying a configuration to 10 endpoints in your remote office. If you click Move the configuration to trash after the configuration is deployed to one of the endpoints, then it will not be deployed in any of the 9 endpoints and the configuration will be permanently deleted and the deployment for that configuration cannot be resumed.