Configuration status does not change

Problem

The status of the configurations is always in "Ready to Execute" state.

Cause

The status of configurations may remain unchanged due to one or more of the following reasons:

Time delay for configuration to get applied

1. User Configurations: User configurations will be applied during user logon, after user logon, or every 90 minutes whichever is earlier. Till then the status will remain only in "Ready to Execute"
2. Computer Configurations: Computer configurations will be applied during system startup, after system startup, or every 90 minutes whichever is earlier. Till then the status will remain only in "Ready to Execute".
The agents' last contact time should be after the configuration created time. For computer configurations, you can verify the agents last contact time and the configuration created time by clicking the status link of the corresponding configuration. For User Configurations, you need to verify the agents' last contact time from the SoM page.
3. Defining a configuration with "Install between time" and the given time is less than the 90 minutes refresh interval. If the install between time is less than 90 minutes, there are possibilites that the agent might not contact the Desktop Central server within the specified install between time, so the configurations will never reach the client computers/users.

Association with an Empty OU

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

Firewall Blockers

Any firewall running in the machine where Desktop Central is installed might block the status update messages that come from client machines.

Agent Version is not up-to-date

Check the agent version from the SoM page for that computer. You will get to see the latest agent version by clicking the License link from the top-right of the client. Both the versions should be the same. If it is not the latest version, you need to upgrade the agent to the latest version

Distribution Server has not synchronized the configuration data yet

If the computer is at the remote location and if you are using Distribution Server, check the DS Status from SoM --> Remote Offices tab. This should be green (healthy)

Absence of Desktop Central Agent in Client machines

Desktop 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 link.

Resolution

Detect and correct the issues as follows:

Time delay for configuration to get applied

You can apply configurations immediately by doing one of the following:

• Right-click on the Desktop Central tray icon and click Apply Configurations
• Execute C:\Program Files\DesktopCentral_Agent\bin\cfgupdate

Association with an Empty OU

Check whether OU specified as the target has users and computers within it.

Firewall Blockers

Add the Desktop Central Port (default 8020) to the exceptions list of Firewall. Steps include:

1. Go to Start and select Control Panel.
2. Select Windows Firewall. This opens the Windows Firewall window.
3. Select the Exceptions tab and click on Add Port.
4. Add the port name and port number here.
5. Add Port 8020 for HTTP and Port 8383 for HTTPS.
6. Click OK.

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 re-install the agent from SoM page. For computers at remote locations, this has to be done manually.

Distribution Server has not synchronized the configuration data yet

If the DS Status is not healthy, there is some problem between the communication between the Desktop Central Server and the Distribution Server. Check the firewall and ensure that all the required ports are open. Ensure that the Distribution Server is healthy by checking its last contact time, next replication time and Upgrade status.

Desktop Central Agent is not installed in client machines

Verify from the SoM page of Desktop Central Server, whether the Agent is installed on the client machine. Install Agent on client computer if not found. If the computer is at the remote locationa and if you are using Distribution Server, ensure that the agent is communicating with the correct distribution server.

Configration using Install between time

When a configuration is deployed using install between time specified, make sure that the specified install between time is more than 90 minutes refresh interval. So this ensures that the Agent will definitely contact the Desktop Central server every 90 minutes, and the configuration will be deployed.

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

Unable to resolve this issue?

If you feel this KB article is incomplete or does not contain the information required to help you resolve your issue, upload the required logs, fill up and submit the form given below. Include details of the issue along with your correct e-mail ID and phone number. Our support team will contact you shortly and give you priority assistance and a resolution for the issue you are facing.  * Mandatory Fields

Other KB articles

24/5 Support

Agent Installation Configurations Inventory Management Patch Management Software Distribution Service Pack Installation Desktop Sharing Active Directory Reports User Logon Reports Desktop Central SP Upgrade Miscellaneous » More

Support will be available 24hrs a day and five days a week (Monday through Friday), excluding USA & India public holidays. Tel : +1-888-720-9500 Email : desktopcentral-support@manageengine.com Speak to us Join the Desktop Central Community, to get instant answers for your queries, register with our Forum. Look out for the latest happenings in Desktop Management, follow our Tweets on Twitter. Get to know the latest updates and Best Practices in Desktop Management through our Blog.