Agent fails after Microsoft patching

Has anyone else had issues installing agents on endpoints after Microsoft updates? We recently installed KB5017035 and KB5018411 on our Windows server that hosts NPM and can no longer complete agent installations on remote endpoints. It could be our local AV also, but I am working to test that now.

Find more posts tagged with

Agent

agent issues

Accepted answers

All comments

bshopp

I am not aware of any issues, but if needed, please open a ticket with support to investigate further.

admin_nsn

Yes, for the longest time we have had issues with the agent failing after patching Windows Servers. The resolution can be different from time to time. Sometimes just restarting the service resolves the issue, sometimes changing the polling engine. In the most severe cases the agent has to be reinstalled on the monitored servers.

We've tried to contact SW support regarding the issue, but they keep pointing to issues with our database and seems to brush of the actual issue with the agent. I recognize the issues from the health report being pointed out, but it has nothing to do with a service on a windows server breaking.

Fred.Loucks

Yes, we have similar issues but we may not have the same issue you are experiencing. Our problem occurs when patches have been pushed to Windows Servers; however, patches aren't fully implemented because a server restart is required for patching processing to complete.

We have hundreds of servers that get patched and need to be restarted every month. If restart doesn't occur, servers drop, disappear, and start polling weird in SolarWinds. Now that occurs to both Agents and WMI polled servers. The commonality is servers are Windows and restarts are required for patch implementation. If patches sit there for a few days, servers will absolutely fail in SolarWinds. Restart servers, patches fully apply, and the servers become happy in SolarWinds again.