Previous Topic: Rule with Variable Does Not Deploy On EndpointNext Topic: DNSDOMAINNAME Variable Does Not Have a Value


Built-In Variable Is Not Refreshed

Symptom:

I changed the system settings on a CA ControlMinder endpoint, but the value of a built-in variable has not changed to the value of the new system setting.

Solution:

Use the following procedure to troubleshoot this problem:

  1. Verify that the value of the policyfetcher_enabled configuration setting in the policyfetcher section on the endpoint is 1.

    A value of 1 for this configuration setting specifies to run policyfetcher. If policyfetcher is not running, it cannot check the CA ControlMinder database for updated variables.

  2. Verify that policyfetcher has sent a heartbeat after you changed the system setting, as follows:
    1. In CA ControlMinder Enterprise Management, click World View and click the World View task.

      The Search screen appears.

    2. If required, define the search criteria to locate a particular subset of data, and click Go.

      The results matching the criteria you defined are displayed by category.

    3. Verify that the update time in the Last Status column is later than the time at which you changed the system setting.

      If the update time in the Last Status column for the endpoint is earlier than the time you changed the system setting, policyfetcher has not sent a heartbeat and has not yet checked for updated variable values.

      Note: You can change the interval between heartbeats by changing the endpoint_heartbeat configuration setting.

  3. Restart CA ControlMinder and verify that the system setting has changed.

More information:

Built-In Variables