CA Client Automation

Hi all.

I want to deploy the default policy in all my environment, I have 3 domains managers and i modify this policy from the Enterprise Manager. "The modifications are minimal (Only in Remote Control)"

The idea is that all the new equipment discovered take the default with the changes, and in the already discovered take them back, I have eliminated all the previously policy´s  generated.

I can not create a job pointing to the default policy from the EM and neither from any of the DM

Thanks.

There's no need for you to do anything. When you update the default policy and SEAL it, it will automatically be replicated from the EM to the DMs, then it will be automatically pushed out from the DMs to all computers. You can check if an individual computer has received the update by looking at it's configuration policy last update time

Steve McCormick

Services Principal Consultant

Thanks for youre support

How can i check the last update time ?

There is an image from one of the devices added

If there was some error in deploy what would be the way to correct it ?

Regards

The screenshot shows this device was last updated on March 28th, and has an update scheduled since May 18th. It is marked as out of date.

If the device is online and has updated inventory but is not updating its config policy, try restarting the CAF CCNF components on the Domain, sometimes they get stuck.

If the config policy still won't update, verify the Domain and Scalability Server can communicate with the Agent by using CAMPING from the Domain  and SS to the Agent. If the Domain/SS cannot camping to the Agent but the Agent can camping to the SS, verify there is no Windows or 3rd party firewall running on the Agent. Otherwise open a support case for more assistance.

Hi thank you very much,

When send "caf stop all" and "caf sart all" in the DM´s, the CAF CCNF restarts or what is the correct way to do it?

HI,

caf stop/start will restart CCNF. 

I'd like to explain Stephen's advice with screenshots.

1. "Activation time" means last update date/time for configuration policy. It doesn't mean the agent was restarted at this time or collect inventories.

2. Unseal default configuration policy, and seal the policy again. And then, DM will check which agents have the policy, and create job to update it automatically.

3. If target agent is online, configuration policy will be applied and update "Activation time" without any operations on agent side.

It seems your stage is above step 2. It means the agent is off line or cannot communicate with DM through SS. So, we need to check connectivity among DM/SS/Agent using ping/camping/caf ping.

https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1855521.html

Additionally, I recommend to restart CAF on the agent as well.

> caf stop

> caf start

> caf status

Thanks

Yas

Thaf will work but it restarts the whole DM. Try 'caf status' then 'caf stop' for each of the components with 'ccnf' in the name, then 'caf staff's will restart all stopped components.

Steve McCormick, ITIL CA Technologies Principal Services Consultant Stephen.McCormick@ca.com

Default configuration policy automatically always updates to all computers. You should never have to deploy it anywhere. As long as the Enterprise agent is correctly pointing to one of the DM's or one of the DM's Scalability Servers, it should receive that policy automatically as well.

Depending on the system, possible issues could be:

1. Name resolution in the reverse direction (run 'camping -a <other machine name>' from each end of a connection to test)

2. UDP instability with larger chunks of data (run 'camping -s 20000 <other machine name> from each end to test)

3. Something hung on the SS or Client side (reboot each to confirm)

4. A damaged installation (Record any patches applied, run a repair, reboot, apply patches and reboot once more)

Barring that, CCSMAPI and CCSMACT on the DM side can be recycled if the DM cannot be rebooted, and any logs with those terms in the name as well as CCNFAGENT, CCNFAGENTAPI and CCSMAGENT should be checked/collected where they exist on the DM/SS/Client side (they don't all exist on all levels) to look for a deeper cause.

Thanks,

Joe Puccio

Senior Engineer, Software Support