Helping us help you - Behaviour of tacmd updateagent
ShaunR 2700005SW1 Visits (2937)
So this one was spawned following a question from a customer. They asked us why upgrading one agent, such as the OS agent, was leading to other agents on the same machine being restarted even when they hadn't done anything to them.
This is because an upgrade to any agent that causes the underlying agent framework to be updated will cause all agents on the machine to be stopped and then restarted after the upgrade is complete. Any agent running when the upgrade starts is stopped and then restarted after the upgrade.
If an agent is not running when the upgrade occurs, if it is the one being upgraded, it should be started automatically after the upgrade. However, if it was not being upgraded it will remain stopped after the upgrade. We try to leave things as we found them after the upgrade is complete. If deploy is used to upgrade a single agent and it does NOT update the agent framework, then only that specific agent is stopped and started after the upgrade is complete.
Hope that clears things up!
Subscribe and follow us for all the latest information directly on your social feeds: