Overview
The Liongard Agent regularly checks in with Liongard and reports information about the computer it is installed on, such as hostname and FQDN information, operating system details, and the agent version.
It is normal for some of these details to update on a different schedule than the agent's online status. This article explains why, and what to expect after you make a change to a machine — for example, renaming a Windows computer.
What the agent reports
During its regular check-ins, the agent collects current system, configuration, and runtime information and sends it to Liongard. Some of this is gathered from the local machine (such as hostname, operating system details, and PowerShell version), and some reflects the agent's own configuration or runtime state.
Examples of the information a check-in may include:
Hostname and FQDN information
MAC address
Operating system name, version, and build
PowerShell version
Agent version
Service account the agent runs under
Relevant agent runtime and job information
These are examples rather than a complete or fixed list, and not every value is necessarily displayed in the same place or saved on exactly the same schedule.
How often the information updates
There are two different rhythms to be aware of, and they are not the same:
Online status (frequent): The agent checks in with Liongard frequently. These check-ins keep the agent's online status and last seen time current, so connectivity is reflected quickly.
Machine details (about once per day): The broader machine details — such as hostname and FQDN information, operating system details, and PowerShell version — are saved less frequently. Liongard generally stores these broader details during the first eligible successful check-in of the day.
Because of this, an agent can correctly show as online with a recent last seen time while its machine details still reflect an earlier value. This is expected behavior, not an error.
There is one common exception. When the agent reports a new agent version, Liongard may save the broader machine details during that successful check-in rather than waiting for the next normal daily update.
Why a recent change may not appear immediately
If you recently changed something on the machine — most commonly by renaming the computer — the new value may take some time to appear, for two reasons:
The daily save has not happened yet. Broader machine details are normally saved once per day during a successful check-in, so a change made after that point will appear at the next one.
(Windows) The operating system may not report the new name yet. Windows commonly requires a restart before a computer-name change is fully applied and reported consistently. The agent reports the value currently provided by the local machine, so until the operating system reflects the new name, the agent will continue to report the previous one.
How long should you wait?
While the agent remains online and continues to check in successfully, broader machine details should normally update by the next daily save. In general, allow approximately 24 hours.
The delay may be longer when:
The agent is offline.
Check-ins are failing.
A Windows computer was renamed but has not yet been restarted.
The operating system has not yet begun reporting the new value.
The agent's online status and last seen time should update much sooner and are not subject to this delay.
Do you need to take any action?
In most cases, no action is required — the updated information appears automatically once the machine reports it and Liongard performs its next daily save.
If you renamed a Windows computer, restart the machine so the operating system begins reporting the new name.
Basic troubleshooting
If the information has not updated after the expected time:
Confirm the agent is online. Check that the agent has a recent last seen time in Liongard.
Confirm the change is complete on the machine. For a rename, make sure the new name is fully applied by the operating system. On Windows, this commonly requires a restart.
Confirm the agent is on a supported version.
Allow a full daily cycle before concluding that something is wrong.
(Optional) Restart the Liongard Agent service after confirming it is running normally. This prompts the agent to check in again and can refresh the online status, but it does not necessarily bypass the normal interval for saving broader machine details. Repeatedly restarting the service is not a required troubleshooting step.
When to contact Liongard Support
Contact Liongard Support when:
The agent remains online and checks in successfully, but the information is still outdated after 24–48 hours.
The machine has been restarted after a Windows rename, but the previous value remains.
The agent cannot maintain an online status or a recent last seen time.
The agent service is running, but check-ins appear to be failing.
The behavior continues after confirming the agent is on a supported version.
When you contact Support, please include:
Agent name
Environment name
Old and new values (for example, the previous and current hostname)
Approximate date and time of the change
Whether the computer was restarted
The agent's current online or last seen status
The installed agent version, when available