Force Clients to update AMP connector and definitions

[nibose]

Hi,

I am trying to update the Cisco AMP connector on our clients.  Is there anyway I can force the updates from the AMP console, as even when I schedule the updates, some of the hosts are not updating the clients.

Is there also a method to update the definitions from the AMP console?

Thanks,

Nitin

[Troja007]

Hello,
quick question, just to be sure to understand your question right. You are asking for a "real time action" started from the Secure Endpoint Console for a specific task, e.g signature update, on the endpoint, right?

Sorry to say, this feature is not available in the product. Today, the endpoint does a regular scheduling for Signature updatew based on the policy settings.

Actually we already started a project for a Re-design of the policy handling. I have no infos how the task scheduling will be changed, but you may ping your Cisco representative to get more infos. Or, in addition, your Cisco Representative can open a Feaure Request for you.

Greetings,
Thorsten

[nibose]

Hi Thorsten and others!

Thanks and hope you've all had a great weekend!

I was referring to the connector update, from ver  7.3.9.20091 to ver 7.3.13.20165.  I've created two groups based on the connector version: 7.3.9.20091 and 7.3.9.20091

I had scheduled it for a time range and I move hosts from the lower version group to the higher version groups in batches of say, 20 hosts at a time.  I've noticed that the hosts do not get their connectors updated but take quite sometime and some hosts do not get their connectors updated.  I've checked the option in the policy "not to reboot" during a connector update

Is there any way for me to force this update?

regards,

Nitin

[Troja007]

Hello,
FYI, with connector version 7.x we added a feature called "no reboot updates". This means, when upgrading from version 7.x to 7.x there should not be any reboot needed. 

There may be some situations, where a reboot is required. This can be if you upgrade from a 6.x version or if there is a major upgrade necessary in the future.

Even i would love to see improvements for the whole scheduling for the deployment in our product, it works very robust today.  I´m not aware of any known bug or problem within the upgrade procedure. If the client is communicating with the Secure Endpoint Backend, if you see the policy upgrade for the endpoint and it is still not upgrading, but other endpoints in the same group do the upgrade, it may makes sense to open a TAC case. You may add a "Diagnostic package" to the TAC case, so an engineer can take a deeper look what is going on at the endpoint.

Greetings,
Thorsten

[larry.siegelman]

Hi,

I'm sure this thread may be old, but do we have to set a specific connector version in the policy, or does it automatically look for the latest?

I have the same setting for both Windows and Mac, i.e. none chosen.

The Windows connectors appear to be all updated, but the Macs are not.

[Troja007]

Hello @larry.siegelman ,
there is no option to automatically install the latest available connector version. This must be done in the policy. But, we are already working on bigger updates on the console to simplify this operational task.
Greetings,
Thorsten

[larry.siegelman]

Hi @Troja007 

This is my question.

Is what is set correct?

See pic.