‎05-10-2024
06:13 PM
- last edited on
‎05-21-2024
04:41 PM
by
Riley
We use a Powershell script to install the LsAgent across the enterprise. This works great. It downloads the newest version of the agent and runs it fine. Now we are trying to use the same process to upgrade LsAgent to the newest version 11.1.10.0. Here is the line in our Powershell script that does the work.
‎07-26-2024 11:31 AM
function Download-LansweeperAgent {
$url = "https://content.lansweeper.com/lsagent-windows/"
$downloadPath = "$env:TEMP\LansweeperAgentInstaller.exe"
Invoke-WebRequest -Uri $url -OutFile $downloadPath
}
function Install-LansweeperAgent {
$installerPath = "$env:TEMP\LansweeperAgentInstaller.exe"
Start-Process -FilePath $installerPath -ArgumentList "--mode unattended --unattendedmodeui minimalWithDialogs" -Wait
}
Download-LansweeperAgent
Install-LansweeperAgent
‎07-17-2024 07:32 PM
Hello @DonnyBuckman
Your LsAgent installs *should* update when you update your Lansweeper installation. If there's a new LsAgent version included with the Lansweeper update, it will be detected, downloaded, installed, and restarted. This updated version will come directly from the scanning server that was recently updated or through the agent relay server.
So, technically, you shouldn't have to run an update command on your LsAgent installs. But if you have found a bug in this performance, please open a ticket with Support so we can get this resolved.
Best wishes.
Tim
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now