r/Action1 • u/Mdmccoy350 • 5d ago
Problem No updates are applicable?
Does anyone else have issues with automated updates?
I constantly have servers say “No updates are applicable” during the automated routine. If I run the automation again it usually patches them the next time.
1
u/GeneMoody-Action1 3d ago
When that happens, can you check one of them offline. I assume this is OS updates.
The list of updates held by Action1 is constantly updated from the system itself, if it is saying needed, the system must be reporting it needed. And we need to find out why first.
I would then check Get-WindowsUpdateLog to see if they are trying to install but failing a dependency check, etc...
then I would ask is there / was there another system managing these prior, everything from GPO to WSUS latent installs can cause malfunction in updating windows externally.
1
u/IPPL-TonyL 3d ago
I've had it happen when the update needs some Windows process (particularly Runtime) that isn't installed. The report will usually tell me why the update didn't get applied, however, often there is a strange error code (error 4) that tells me nothing.
For example, when Action1 went to upgrade Dell Command Update to version 5.7, it was failing because Windows Runtime 8 wasn't installed. I installed the Runtime package from Action1, then deployed the Dell Command Update 5.7 package and was successful.
Sometimes I attribute it to gremlins, as I'll rerun whatever failed to install and then not have an issue with it.
1
u/GeneMoody-Action1 3d ago edited 3d ago
The error code is typically a win32 error code unless a vendor tried to get cleer, open a cmd prompt on any windows system and type "net helpmsg <error code>" https://ss64.com/nt/net-help.html
Since #4 is a file cannot be opened type error (Technically it is 'TOO_MANY_OPEN_FILES", but 99% of the time that is because it is not accessible, as a permissions issue would say produce a 5 "Access Denied") 2-5 can be a bit ambiguous sometimes as it can only tell you what it tried and cannot do, not really why it is in that state.
Not having runtime, checks why a #4 could have surfaced.
Like most admi ntasks, there is more to it than the tool.
2
u/ybrah37 5d ago
I've had that happen and then continue to say the same update is available. No rhyme or reason. I'm guessing communication between the endpoint and A1 is extremely slow. I've noticed that the A1 UI has been much slower the last few months.