we have deactivated automatic updates of OneAgents on environment for various reasons and have recently done manual updates to version 1.303.
During this, the upgrade of OA on one Windows server failed and after some debugging it seems the root cause was the OS being too old (Windows 2012). This is not something we can resolve, the server will probably be decommissioned soon. We will probably have to live with the outdated OA version until then.
In the meantime however, we have daily notifications in our tenant that another update attempt was made and failed.
So my question is: Is there any way to stop these daily update attempts?
thanks for your suggestion. Unfortunately the update mode was already set to “No automatic updates” - at most I could try to toggle it on and off again.
Regarding the host specific setting for the target version, I can see this option available for other OAs. But it’s not there for this one:
The fact that there are daily attempts to update the agent, even when starting the update manually, can make sense for Unix servers where there is not enough space in the filesystem. Then the agent will be updated within 24 hours of making enough room in the filesystem. But in this case I really would like to be able to stop these update attempts.
the agent’s version is 1.299.45 but there is also a version 1.299.50 available. I set it to “automatic updates at earliest convenience” and chose the target version 1.299 (I can’t chose sub-versions below that) but I assume the update attempt will be done anyway. I’ll check this again tomorrow.
We are facing the exact same problem. It seems that even with Automatic updates disabled in every level, when the OA starts trying to update it will do so forever. It doesn’t make sense for it t ignore the no auto update directive even if it fails.
We haven’t resorted to oneagentctl yet, since we want to first understand why is the No Automatic Update policy ignored.
