Me again
I need to disable autoupdate on all nodes in my SAM 6.2.1 install. I know the value is in Orion.AgentManagement.Agent table AutoUpdateEnabled (Boolean)... How do I set this to false for all Nodes?
Thanks!
Why not just disable automatic updating under the Global Agent settings?
I have that set but does not seem to affect those Nodes that have autoupdate already set.
Get-SwisData $swis "SELECT name,AutoUpdateEnabled FROM Orion.AgentManagement.Agent"
These all come back as True.
The issue I am trying to resolve is that it seems that the update will take place (which is fine) but if there is a pending reboot I am stuck... The agent does not fully function. So I am assuming from your answer here that this Global Agent Setting should resolve my issue?
The Agent simply detects if the endpoint requires a reboot for any reason. Typically it's related to Windows Updates that have been installed but not yet applied until a reboot is completed. If the agent is fully functional already then agent upgrades should not be impeded by the fact that the endpoint is awaiting a reboot. This is primarily an issue when the agent is initially deployed and the agent is unable in install required dependencies such as .NET 4.0 or the C++ Runtime because Microsoft blocks those from being installed if there are other updates awaiting a reboot.
OK, good to know. I am really trying to avoid the situation where there are pending reboots and SW pushes out a new agent. The current servers that say "Reboot Required" are not fully functioning as far as the agent goes. I try to probe them for resources and it tells me a reboot is required. This is what leads me to believe that the global agent setting is not working, but I could be wrong. Can you confirm if that is supposed to prevent the agent from autoupdate?
woops wrong post - ignore that lol
OK - It turns out that this issue I am chasing seems to be with the new SW Agent 1.2.78. I logged into a node that SW said needed to reboot. I reran the agent-setup.msi and all came up great. There was also a problem trying to restart the agent service SolarWindsAgent64 ... So it seems that the autoupdate install broke it on many nodes.
It's important to note that the Agent's global setting is respected, but it does not change the value for the individual agents in Agents database table. So you will continue to still see “true” for all agents Auto Update, but that does not mean it is ignoring the global flag.
If you disabled the global Auto Update setting after upgraded SAM then the update was already pushed to all agents, so this will not fix anything by disabling it now.
Also note that there is currently no API to change the auto-update setting on a per-agent basis. This must be done via the Web Interface, or directly through the database. I would however advise against changing this setting directly in the database.
Alter - Yep, i know that it wont do anything now but the agent caused allot of problems in our environment, which I realize is not about autoupdate. The agent is a mess and I have opened a ticket with SW support.
Turns out this is a know issue with SAM 6.2.1 from talking to SW dev. It was preventing autoupdate from working because it thought that the node needed to be rebooted, which it did not. Support reset agent status and I was able to manually update all the hosts. I will be disabling autoupdate to maintain control.
