• Active Directory
  • Application
  • Desktop & Mobile
  • Help Desk
  • Network
  • IT Security
  • MSP
  • On-Demand
 
 
Device Management, made easy
Manage control and secure your workstations, mobile
devices and tablets
 
 
Help Desk for Everyone
IT Help Desk Software and Customer Support Software
 
 
Protect Your IT. Save Your Business
Build a secure fortress with our security management solutions
 
 
MSP
Manage services faster, with multi-tenanted, ITIL-ready, and unified RMM solutions
 
 
On-Demand Solutions
IT Help Desk, Active Directory, and Operations Management from the Cloud
 

Desktop MSP Configuration Status

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:

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

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.

Agent Version is not up-to-date:

Check the agent version from the Customers page for that computer. If it is not the latest version (in comparison with the other computers), you need to upgrade the agent to the latest version

Firewall Blockers

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

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"

Agent has not picked up the configuration yet:

Check the Agent last contact time in Customers. The time should be greater than the time at which the configuration was applied

Distribution Server has not synchronized the configuration data yet:

If you are using Distribution Server, check the DS Status from Customers --> Remote Offices tab. This should be green (healthy)

Resolution

Detect and remediate the issues as follows:

Desktop Central Agent is not installed in client machines:

Verify from the Customers page of Desktop Central MSP Server, whether the Agent is installed on the client machine. Install Agent on client computer if not found.

Agent Version is not up-to-date:

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

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 8040) 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 8040 for HTTP and Port 8041 for HTTPS.
  6. Click OK.

Time delay for configuration to get applied:

If Desktop Central Agent Tray icon is enabled then, right click on the icon and select Apply user/computer configurations.

To apply the configurations immediately, execute the "C:\Program Files\DesktopCentral_Agent\bin\cfgupdate" command in the client computers as below:

  • For applying the user configurations: cfgupdate user
  • For applying computer configurations: cfgupdate computer

Agent has not picked up the configuration yet:

If the agent last contact time is before the configuration applied time, you need to wait for at least 90 minutes from the time of deploying the configuration. Alternatively, you can apply the configurations immediately using the cfgupdate command as stated above.

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.

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

Remote Desktop & Mobile Device Management Software for MSPs trusted by