Configuration Status Yet to Apply - Knowledge Base

Problem

A configuration has been deployed and the status always remains in "Yet to Apply". This could be due to one or more of the following reasons: 

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 Desktop Central server. You can verify this, by navigating to the Remote Office tab, under SoM page on the Desktop 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  desktop central server and distribution server logs

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". 

 

Applies to: Desktop Configuration, Desktop Configuration Status, Yet to Apply status, Configuration Collection

Keywords: Desktop Configuration Status, Unchanged Status for Configuration, User Configuration settings, Computer Configuration settings, Windows Desktop Configuration