My desktop client applications appear not to be using configured policies. What do I do?

The most common problem that relates to the Configuration Agent is the inability to see the effects of a configured policy on desktop client applications. The most common reasons for this problem are an incorrectly configured Agent, an incorrectly configured policy repository or the unavailability of the policy repository. The following guidelines can help you to discover and eliminate such problems:

• Ensure that the Agent is configured.

• Ensure that the Agent is enabled/running. If you need to start the Agent, you must also restart the desktop client applications that are currently open.

• If your problems persist, temporarily increase the granularity of the Agent logging mechanism and, if possible, restart the Agent, so that you have complete and fine grained log messages from the time the Agent starts.

• If the Agent fails to start correctly, consult the section Problems starting the Configuration Agent.

• If the Agent starts correctly but your desktop client applications do not use an available policy, consult the section "Problems getting policy from a running Configuration Agent".

• If you are still unable to resolve your problems, please contact Technical Support.