# Desktop Configuration - Configuration Status does not change from In Progress - Endpoint Central Knowledge Base

## Configuration Status is always "In Progress"

### Problem

The status of a configuration is always **"In Progress"**.

### Cause

When a configuration moves to the *In Progress* status, it means that the configuration is applied in at least one of the target computers or users. The status will change to *Executed* only when the configuration is applied in **all** the target computers or users.

When the status of the configuration remains at *In Progress*, it means that the configuration is not applied to at least one of the target computers or users. This may happen in the following cases:

**Configuration is linked to a workgroup**

If you have linked a user configuration to a workgroup, the status will always remain as *In Progress*. This is because the details of users in that workgroup cannot be accessed remotely. Therefore, the Endpoint Central server will not receive information whether the configuration is applied to all the users or not.

**Version of the agent not up-to-date**

If automatic agent upgradation is not successful in all computers, the status of the configuration will remain *In Progress*.

Check the version of the agent of the computer where the configuration is not applied, from the **Computers** tab under **Scope of Management** in the Agent page. Compare it with the latest version of the agent, which you can view on the **Summary** page in the **Agent** tab of the Web console of the product. Both versions should be the same.

If the versions are different, you must upgrade the agent to the latest version.

**Agent has not picked up the configuration yet**

The agents' last contact time should be after the configuration created time.

- For computer configurations, verify the agent’s last contact time and the configuration created time by clicking the status link of the corresponding configuration.
- For User Configurations, verify the agent’s last contact time from the SoM page under the Agent tab.

**If the target has any dummy computer objects**

If you have linked the configuration to an OU or a domain, check whether the OU/domain has any dummy computer objects. These computers will never receive the configuration, causing the status to remain in *"In Progress"* state.

**Absence of Endpoint Central Agent in client machines**

The Endpoint Central agent may not have been installed in all the computers within the defined scope. To verify this, view the **Agent Installation Summary** by clicking **Admin → Scope of Management**.

**Deploying the configuration to a remote office when the user belongs to a local office**

If you deploy a configuration to a remote office when the user belongs to another remote office, the configuration status will remain *In Progress*.

---

## Resolution

Detect and remediate the issues as follows:

**Linking a configuration to a workgroup**

This cannot be resolved. If you need accurate configuration status, it is recommended to create a custom group with the required users. You can then associate a configuration with this custom group.

This way, Endpoint Central can identify the exact users in the defined target. When the configuration gets applied to all these users, the status is automatically updated.

**Agent version is not up-to-date**

If the agent version is not up-to-date, you need to uninstall and reinstall the agent.

- If the computer is in the LAN, you can uninstall and reinstall the agent from the SoM page under the Agent tab.
- For computers at remote locations, this must be done manually.

**Agent has not picked the configuration yet**

If the agent’s last contact time is before the configuration applied time, wait at least **90 minutes** from the time of deploying the configuration.

Alternatively, you can apply the configurations immediately as follows:

If the Endpoint Central Agent Tray icon is enabled:

- Right-click on the icon.
- Select **Apply user/computer configurations**.

To apply the configurations immediately, execute the following command in the client computers:

- For Endpoint Central below 11.2.2309.01:

```
C:\Program Files\DesktopCentral_Agent\bin\cfgupdate
```

- For Endpoint Central 11.2.2309.01 and above:

```
C:\Program Files\UEMS_Agent\bin\cfgupdate
```

Then use:

- For applying user configurations:
  ```
  cfgupdate user
  ```
- For applying computer configurations:
  ```
  cfgupdate computer
  ```

**If the target has any dummy computer objects**

Clean up your Active Directory to remove dummy or unused computer objects.

Alternatively, create a custom group of computers in Endpoint Central and associate the custom group with configurations.

**Endpoint Central agent is not installed in client machines**

Verify from the SoM page under the Agent tab of the Endpoint Central Server whether the Agent is installed on the client machine. Install the Agent on the client computer if it is not found.

**Deploying the configuration to a remote office when the user belongs to a local office**

Deploy the configuration to the correct remote office or to a specific domain.

---

**Applies to:** Desktop Configuration, Desktop Configuration Status, Ready-to-execute state, Configuration Collection

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