
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2021 10:33 AM
In our report, all versions are still indicated with 7.x. But we have already installed Lansweeper Server 8.20.x ...
Is there a wiki and / or a howto on how the clients (all Windows) update themselves automatically?
as hoanv9 already mentioned in a post in 2018:
BTW, for normal windows, the user don't have the permission to install software by themself. Pls also consider about that.
Please help about this, because we have hundreds of Clients...
Solved! Go to Solution.
- Labels:
-
General Discussion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2021 01:55 PM
LsAgent not updating automatically
LsAgent for Windows can update itself when scanning direct to server or via the relay. However, keep in mind that the LsAgent version is not directly related to the Lansweeper version. Our latest LsAgent will in most cases not have the same version number as Lansweeper. As the OP described a version 8.2, this version corresponds with a 7.2 LsAgent version, you can find the list of Lansweeper versions and their corresponding LsAgent client version on our changelog page.
The latest LsAgents were not always immediately updateable via the relay, but they were when connecting direct to server. This is because of a delay on our part for making the agent available on the relay server itself.
LsAgent removing itself (from add/remove programs)
This was a bug in LsAgent release version 8.4.100.142 and 8.4.100.144. It has been resolved in the latest version, 8.100.149. This version can be automatically updated to by updating Lansweeper to version 8.4.110.3.
Keep in mind that LsAgent didn't actually delete or uninstall itself. What happened is that the service cleaned up its own registry entries due to a version mismatch. Outside of that the agent was fully functional.
LsAgent installing .NET Framework 4.8
As of LsAgent version 8.x (corresponding Lansweeper version 8.4.100), the minimum .NET Framework required for the agent is 4.8. This means that:
- Some operating systems are no longer supported, e.g. vanilla Windows 8, very early Windows 10 builds
- When a lower .NET framework is found, the agent tries to update .NET before updating itself (connecting to microsoft.com)
- A reboot may be required post installation before the agent is functional. This reboot requirement is detected by Microsoft's installer and is dependent on whether or not updated libraries were in use at the time of installation.
We published this updated .NET requirement in our knowledgebase and specifically mentioned it in our changelog when version 8.4.100.9 was released:
Changed: LAN-8239 To strengthen security and to allow for the implementation of new scanning technologies, LsAgent for Windows now requires .NET Framework 4.8 to be installed on the client machine. If not already present, LsAgent will automatically try to install .NET 4.8.
https://www.lansweeper.com/knowledgebase/lsagent-installation-requirements/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-25-2021 05:43 PM
Shame on me for not reading the release notes appropriately, but just deploying .NET to my boxes was not cool.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2021 01:55 PM
LsAgent not updating automatically
LsAgent for Windows can update itself when scanning direct to server or via the relay. However, keep in mind that the LsAgent version is not directly related to the Lansweeper version. Our latest LsAgent will in most cases not have the same version number as Lansweeper. As the OP described a version 8.2, this version corresponds with a 7.2 LsAgent version, you can find the list of Lansweeper versions and their corresponding LsAgent client version on our changelog page.
The latest LsAgents were not always immediately updateable via the relay, but they were when connecting direct to server. This is because of a delay on our part for making the agent available on the relay server itself.
LsAgent removing itself (from add/remove programs)
This was a bug in LsAgent release version 8.4.100.142 and 8.4.100.144. It has been resolved in the latest version, 8.100.149. This version can be automatically updated to by updating Lansweeper to version 8.4.110.3.
Keep in mind that LsAgent didn't actually delete or uninstall itself. What happened is that the service cleaned up its own registry entries due to a version mismatch. Outside of that the agent was fully functional.
LsAgent installing .NET Framework 4.8
As of LsAgent version 8.x (corresponding Lansweeper version 8.4.100), the minimum .NET Framework required for the agent is 4.8. This means that:
- Some operating systems are no longer supported, e.g. vanilla Windows 8, very early Windows 10 builds
- When a lower .NET framework is found, the agent tries to update .NET before updating itself (connecting to microsoft.com)
- A reboot may be required post installation before the agent is functional. This reboot requirement is detected by Microsoft's installer and is dependent on whether or not updated libraries were in use at the time of installation.
We published this updated .NET requirement in our knowledgebase and specifically mentioned it in our changelog when version 8.4.100.9 was released:
Changed: LAN-8239 To strengthen security and to allow for the implementation of new scanning technologies, LsAgent for Windows now requires .NET Framework 4.8 to be installed on the client machine. If not already present, LsAgent will automatically try to install .NET 4.8.
https://www.lansweeper.com/knowledgebase/lsagent-installation-requirements/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2021 09:26 AM
LsAgent for Windows can update itself when scanning direct to server or via the relay.
What about updating automatically the Linux agent ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2021 01:25 PM
Antoine EVRARD (Stormshield) wrote:LsAgent for Windows can update itself when scanning direct to server or via the relay.
What about updating automatically the Linux agent ?
At the moment the Windows client is the only one that is updating automatically. Updating the Linux and MAC client is on the wish list. We gave this an extra vote. Hopefully this is something we can do in the future.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-19-2021 12:27 AM
FrankSc wrote:Antoine EVRARD (Stormshield) wrote:LsAgent for Windows can update itself when scanning direct to server or via the relay.
What about updating automatically the Linux agent ?
At the moment the Windows client is the only one that is updating automatically. Updating the Linux and MAC client is on the wish list. We gave this an extra vote. Hopefully this is something we can do in the future.
You can have my vote for Linux/macOS auto update as well.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2021 12:39 PM
Is that the service concept that is reflected in the annual subscription prices?
I don't want to appear malicious, but my question here is not that trivial !!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2021 03:11 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2021 11:22 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2021 09:50 PM
In other news I was really frustrated (with myself mostly) that I didn't catch the .Net 4.8 installation. I would have removed the majority of the LSAgent server installs I had prior to the upgrade.
