Configuration Status Not Changing

1. Time delay for configuration to get applied

• User Configurations: User configurations will be applied during user logon, after user logon, or every 90 minutes, whichever is earlier. Until then, the status will remain in "Ready to Execute".
• Computer Configurations: Computer configurations will be applied during system startup, after system startup, or every 90 minutes, whichever is earlier. Until then, the status will remain in "Ready to Execute".
• The agent's last contact time should be after the configuration creation time. For Computer Configurations, you can verify the agent's last contact time and configuration creation 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 a configuration is defined with Install between time and the specified time is less than the 90-minute refresh interval, the agent may not contact the Endpoint Central server within the specified window. As a result, the configuration may never reach the client computers or users.

2. Association with an Empty OU

If the OU specified as the target for a configuration does not contain users or computers, the status will remain unchanged.

3. Firewall Blockers

Any firewall running on the machine where Endpoint Central is installed might block status update messages from client machines.

4. Agent Version is not up-to-date

Check the latest agent version from the Summary page under SoM in the Agent tab. You can find the agent version of the affected computer on the Computers page under the Agent tab. Both versions should be the same. If the agent is not running the latest version, it needs to be upgraded.

5. Distribution Server has not synchronized the configuration data yet

If the computer is at a remote location and uses a Distribution Server, check the DS Status under Agent → SoM → Remote Offices. The status should be green (healthy).

6. Absence of Endpoint Central Agent in Client Machines

The Endpoint Central agent may not be installed on all computers within the defined scope. To verify this, check the Agent Installation Summary on the Agent page under Scope of Management.

7. Configuration or Collection is Suspended

If the configuration or its collection is suspended, deployment does not proceed. Check the status column. A suspended configuration must be resumed before it can be applied.

8. Another configuration is already deploying to the same target

Configurations are applied sequentially to a target computer. If another configuration is still deploying to the same computer, the subsequent configuration remains in "Ready to Execute" until the earlier deployment completes.

The Remarks column displays a message indicating that another configuration is in progress and that the queued configuration will be deployed after it completes.

9. Configuration shows "Executed (Failed)"

A common cause is a registry hive mismatch, such as writing to a per-user registry hive (HKEY_CURRENT_USER) through a Computer Configuration.

Values under HKEY_CURRENT_USER must be deployed as a User Configuration.

1. Time delay for configuration to get applied

You can apply configurations immediately using one of the following methods:

• Right-click the Endpoint Central tray icon and click Apply Configurations.

For Endpoint Central versions below 11.2.2309.01:

Execute:

C:\Program Files\DesktopCentral_Agent\bin\cfgupdate

For Endpoint Central versions 11.2.2309.01 and above:

Execute the following on the agent machine:

C:\Program Files (x86)\ManageEngine\UEMS_Agent\bin\cfgupdate.exe

2. Association with an Empty OU

Check whether the OU specified as the target contains users and computers.

3. Firewall Blockers

Add the Endpoint Central port (default 8020) to the firewall exceptions list.

1. Go to Start and select Control Panel.
2. Select Windows Firewall to open the Windows Firewall window.
3. Select the Exceptions tab and click Add Port.
4. Enter the port name and port number.
5. Add port 8020 for HTTP and port 8383 for HTTPS. Also allow inbound ports 8027 and 8443 to the Endpoint Central server.
6. Click OK.

4. Agent Version is not up-to-date

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

• LAN computers: Uninstall and reinstall the agent by clicking Computers under SoM on the Agent page.
• Remote computers: Uninstall and reinstall the agent manually.

5. Distribution Server has not synchronized the configuration data yet

If the DS Status is not healthy, there may be a communication issue between the Endpoint Central server and the Distribution Server.

• Check the firewall and ensure that all required ports are open.
• Verify the Distribution Server's last contact time.
• Check the next replication time and upgrade status.

6. Endpoint Central Agent is not installed in client machines

Verify whether the Endpoint Central agent is installed on the client computer from the SoM page under the Agent tab of the Endpoint Central server.

Install the agent on the client computer if it is not found.

If the computer is at a remote location and uses a Distribution Server, ensure that the agent communicates with the correct Distribution Server.

7. Configuration using Install between time

When deploying a configuration using Install between time, ensure that the specified installation window is longer than the 90-minute refresh interval.

This ensures that the agent can contact the Endpoint Central server during the specified window and receive the configuration.

8. Configuration or Collection is Suspended

Check the status column of the configuration or collection. If the status is Suspended, click Resume before proceeding with deployment.

9. Another configuration is already deploying to the same target

Wait for the ongoing deployment on the target computer to complete. The queued configuration will then be applied automatically.