Document updating the agents, and harden the Windows update check
- AGENT_UPDATE.md: when an agent needs updating, how (reuse the stored token or rotate it), how to do many servers, how to check it worked, and why a server can stay 'not reported'. - Windows agent: the Windows Update search runs in its own process with a 150 s limit (the scheduled task is stopped after five minutes), a failed search is not retried for an hour, and the cache is read the same in PowerShell 7 and Windows PowerShell 5.1. - Linux agent: says in the journal when the package manager could not be read. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
171511c6db
commit
3da5c639b1
5 files changed
+225
-18
No files matched your search
@@ -436,7 +436,8 @@ The Linux agent asks apt, dnf or zypper (only what they already know; nothing is
|
||||
installed or refreshed) and the Windows agent asks Windows Update (at most every six
|
||||
hours, cached under `%ProgramData%\HomelabManager`). A server whose agent hasn't
|
||||
said — an older agent, or another package manager — shows "not reported", never "up
|
||||
to date"; run its install command again to update its agent. It only looks: to apply
|
||||
to date"; run its install command again to update its agent (how, and how to
|
||||
tell it worked: [AGENT_UPDATE.md](AGENT_UPDATE.md)). It only looks: to apply
|
||||
updates, run a playbook.
|
||||
|
||||
**Customising the dashboard.** Customise (top of the dashboard) lets you move each
|
||||
|
||||
Reference in new issue
Block a user