# Why Configuration Status Stays Yet to Apply Last Updated On: 12 Oct 2026 9 minutes read ## Problem A configuration has been deployed and the status always remains in "Yet to Apply". ## Cause This could be due to one or more of the following reasons: - [Awaiting "Install After Time"](#awaiting-install-after-time) - [Deploy during Startup/User Logon](#deploy-during-startupuser-logon) - [Preferred Day for Deployment](#preferred-day-for-deployment) - [Deployment Window has not reached](#deployment-window-has-not-reached) - [Allowing Users to Skip Deployment](#allowing-users-to-skip-deployment) - [Configuration is applied to remote office and Distribution Server is not reachable](#configuration-is-applied-to-a-remote-office-and-the-distribution-server-is-not-reachable) - [Active Directory is not reachable](#active-directory-is-not-reachable) - [Computers are moved out of specified target during deployment](#computers-are-moved-out-of-the-specified-target-during-deployment) - [Target computer or agent is offline or unable to reach the server](#target-computer-or-agent-is-offline-or-unable-to-reach-the-server) - [Another configuration deployment is already in progress for the same target](#another-configuration-deployment-is-already-in-progress-for-the-same-target) ## Resolution ### Awaiting "Install After Time" If you want the configuration to be deployed only after a specified time, then the configuration will remain in "Yet to Apply" status till the specified time is reached. Status will be modified when the specified time has reached and the deployment has been initiated. ### Deploy during Startup/User Logon If you want the configuration to be deployed only after the system startup/logon, then the status of the configuration will remain in "Yet to Apply". This configuration will be deployed only after system startup/logon. ### Preferred Day for Deployment If you have specified any preferred day/days for the deployment to happen, then the configuration will remain in "Yet to Apply" status till the specificed day. ### Deployment Window has not reached Deployment Window specified in the "Deployment Policy/Settings" determines the time for the deployment to happen. The configuration will remain in "Yet to Apply" status, till the deployment window has reached. ### Allowing users to skip deployment You have allowed the users to skip deployment. The configuration will remain in "Yet to Apply" status, till the time the user skips deployment. ### Configuration is applied to a remote office and the Distribution Server is not reachable The target computers are located in a remote office and the communication to the remote office is routed via Distribution Server. If the Distribution Server is not reachable, then the configuration will remain in "Yet to Apply" status. You can manually verify the connectivity of the Distribution server from one of the target computers located in the same remote office. Ensure that Distribution Server replicates the configuration details from the Endpoint Central server. You can verify this, by navigating to the Remote Office tab, under SoM page on the Endpoint Central web console. If, by any chance the replication fails, you can see an error message with a read KB article. You will have to contact support with the [Endpoint Central server and distribution server logs](https://www.manageengine.com/products/desktop-central/help/general/how-to-send-logs-to-support-team.html). ### Active Directory is not reachable If the configuration is deployed for a target, which belongs to an Active Directory Group/Organization Unit, and the Domain Controller is not reachable from the client machine, then the configuration will remain in "Yet to Apply" status. You need to ensure that the Active Directory is reachable from the client computer. ### Computers are moved out of the specified target during deployment A configuration is deployed to a Custom Group/Active Directory Group/Organization Unit. Computers which were a part of the target has been moved from the Custom Group/Active Directory Group/Organization Unit before deployment is initiated, then the status of the configuration for those computers will remain in "Yet to Apply". ### Target computer or agent is offline or unable to reach the server If the target computer is offline, or its agent cannot reach the Notification Server, the configuration stays in "Yet to Apply". Verify connectivity by running telnet from the agent machine to the server on ports 8027, 8020 and 8383. An outdated or incompatible agent version can also break agent-server communication (for example, a (401) Unauthorized error in the Agent Troubleshooting Tool). In that case, uninstall the agent and reinstall the latest agent from **Agent > Computers > Download Agent**. ### Another configuration deployment is already in progress for the same target Configurations apply sequentially to a target computer. If another configuration is still deploying to the same computer, this configuration is queued behind it. The **Remarks** column shows a message that the deployment of another configuration is in progress and that this configuration will be deployed after it completes. Wait for the earlier deployment to finish, or suspend the earlier task, reboot the target machine and redeploy. **Note** - If the **Remarks** column is blank, the agent may not have contacted the server yet, or the agent version may be out of date. Check agent communication and the agent version before escalating with the configuration summary and agent logs. - If none of the listed causes apply, deploy the configuration first, wait for the normal apply window (about 10-15 minutes), and only then force an immediate apply. On Windows, run **C:\Program Files (x86)\ManageEngine\UEMS_Agent\bin\cfgupdate.exe** on the agent. On Mac, open Terminal, go to **/Library/DesktopCentral_Agent/bin** and run **sudo ./cfgupdate**. To force a refresh across many machines, deploy a [Custom Script (Command Line)](https://www.manageengine.com/products/desktop-central/help/configuration-management/executing_custom_scripts-computer.html) configuration that runs cfgupdate.exe. - For a target that belongs to an Active Directory Group or Organizational Unit that is not reachable, use a Remote Office as the parent target with a Custom Group as the sub-target, so the configuration does not depend on Domain Controller connectivity.