Original Message:
Sent: Jun 25, 2023 04:59 AM
From: Peter Grundler
Subject: Centralized Agent Upgrade (CAU) : installation and example
Hi Thomas,
changing HOST_TargetVersion has also worked for me on my test system.
>At the moment deleting the the HOST_TargetVersion for an agent seems to be the better way, but let's wait for the feedback of the support ;-)
Has support replied? What's the solution from Broadcom?
best regards,
Peter
------------------------------
Automic Certified Professional/Expert & Broadcom Knight
For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
Original Message:
Sent: May 12, 2021 07:25 AM
From: Thomas Steckbauer
Subject: Centralized Agent Upgrade (CAU) : installation and example
Hi,
have you already tried to reset the HOST_TargetVersion attribute in the HOST table? It seemed to work for us, but I will try to get this verified by the support. The agent and AutomationEngine have already been restarted and still no current downgrade attempt.
Really hard when the agents and ServiceManagers are downgraded after a manual upgrade of the AutomationEngine and one agent to version 12.3, afterwards the windows service couldn't be stopped anymore and all processes had to be killed.
Btw, at a first workaround we renamed the Windows agent packages in client 0 which are located in PACKAGES\APPDATA\PCK.AUTOMIC.CAU_AGENT_WINDOWS, but still downgrades were tried and produced errors in Upgrade History.
At the moment deleting the the HOST_TargetVersion for an agent seems to be the better way, but let's wait for the feedback of the support ;-)
BR
Thomas
Original Message:
Sent: 03-31-2020 10:50 AM
From: Elina McCafferty
Subject: Centralized Agent Upgrade (CAU) : installation and example
Hi @Carsten Schmitz, thank you for the input. My team will take a look, from the documentation perspective.
Best regards,
Elina
Original Message:
Sent: 03-30-2020 03:45 AM
From: Carsten Schmitz
Subject: Centralized Agent Upgrade (CAU) : installation and example
> I believe the packs are installed in STORE objects and you can
> find these objects for agents under client 0 \PACKAGES\APPDATA\
> and they will be the PCK* objects. I haven't tested this
Good lead, thanks!
But I would really appreciate a PM to publish something about the design of this aspect, or the documentation department ( @Elina McCafferty).
It should not always be upon community members to test out existential features, such as the required regular cleanup task for CAU packages, only because the impact of not cleaning up will hit some poor soul a few years down the line.
Just my €0.02.
------------------------------
These contain very good advise on asking questions and describing supposed bugs (no, you do not need to go to StackExchange for Automic questions, but yes, the parts on asking detailed, useful questions ARE usually relevant):
http://www.catb.org/~esr/faqs/smart-questions.html
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
I will not respond to PM asking for help unless there's an actual reason to keep the discussion off of the public forums.
Original Message:
Sent: 03-27-2020 07:25 AM
From: Jared Kessans
Subject: Centralized Agent Upgrade (CAU) : installation and example
I believe the packs are installed in STORE objects and you can find these objects for agents under client 0 \PACKAGES\APPDATA\ and they will be the PCK* objects. I haven't tested this, but I would assume that you could delete those objects to remove them from the database.
Original Message:
Sent: 03-26-2020 08:36 AM
From: Carsten Schmitz
Subject: Centralized Agent Upgrade (CAU) : installation and example
More "additional info" for future reference.
- the "packs" screen must be used in Client 0, as Antoine already pointed out. While it does exists in Client > 0, it will not show any content there, which I find mildly confusing.
- while the "packs" screen claims that you can only ever install one pack of each type ("agent unix"), this appears to be untrue. I was able to downgrade to a version that according to the message had been replaced by a newer one just fine. There is the cosmetic issue that a downgrade is repeatedly proclaimed to be an upgrade :)
- it's nice that one can manage multiple versions with this! On the other hand, this also probably means that all packs will accumulate in the database, with (to me at least) no readily apparent way to ever purge old versions of packs. You know, since the "packs" screen, which could provide this, never shows more than one line per pack type. Over time, this would likely eat up significant DB space for the packs.
Hth.
------------------------------
These contain very good advise on asking questions and describing supposed bugs (no, you do not need to go to StackExchange for Automic questions, but yes, the parts on asking detailed, useful questions ARE usually relevant):
http://www.catb.org/~esr/faqs/smart-questions.html
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
I will not respond to PM asking for help unless there's an actual reason to keep the discussion off of the public forums.
Original Message:
Sent: 04-24-2017 07:36 AM
From: Antoine Sauteron
Subject: Centralized Agent Upgrade (CAU) : installation and example
Version 12 introduces this feature, that allows you to upgrade agents directly from the Automation Engine server.
This method has several pros :- You don't need to make a local copy of installation files / binaries from the newer version on each agent
- The AE server updates the agents then restarts them, and writes an upgrade report.
- You can bulk update agents from a single installation package.
There are a few prerequisites and restrictions though:- It only works for agents > v12. You cannot use CAU to update a V11.2 agent for instance.
- Agents can only be restarted by the AE server after the upgrade if they are linked to a Service Manager.
- The user must have the 'Execute System Upgrade' privilege
- CAU is only possible for these agent types:
Install the Plugin Manager
This is a separate component of the AWI that you will need to get from the Download Center. Unzip the compressed file and move the .jar to
<Tomcat>\webapps\<AWI>\WEB-INF\autoinstall : Sign out from the AWI then reconnect to Client 0. The "Packs" view has been added to "Administration":
Download an update package
Each agent has its own package. You can get it at the download center. Look for items whose name start with "PCK".
Once you have downloaded a package, import it by pressing
from the "Packs" view.
Then choose the PCK location and validate:
Update your agent(s)
Once the PCK has finished loading, you can update the agent(s).
Go to Administration > Agents & Groups > Agents, then right-click on the agent > Agent Upgrade.
Set the target version - "latest" is set by default - then press "Upgrade":
The update will start running:
You can get the update report @ Agents & Groups > Upgrade History:
Best regards,
Antoine