→ 🚀What's New? Explore Lansweeper's Fall 2024 Updates! Fall Launch Blog !
‎06-26-2023 01:40 PM - last edited yesterday by Mercedes_O
Hi everyone!
Lansweeper is delighted to announce the availability of its new IT Agent in your Lansweeper Site, now in Preview. Track your hard-to-reach assets using the IT Agent which tracks the details of a single computer running Windows, Linux, or Apple MacOS and sends these directly to your Lansweeper Site.
After a successful installation, the IT Agent(s) will be shown in your Lansweeper Site in Scanning > Discovery systems.
To see the asset data, you can open Inventory > All assets (and you can use the search/advanced filter on the top right to filter on the specific assets/installation where IT Agent is running)
Topic |
|||
Summary |
Newest generation local tracking of any IT device running Windows, Linux or macOS device (including guest virtual machines and connected monitors) |
Older generation local tracking of any IT device running Windows, Linux or macOS device (including guest virtual machines and connected monitors) |
Discover all IT assets in your network. OT discovery will be added to the same installer/package later on |
Asset reach |
By default, local tracking only, no other network devices are discovered. This can be changed, but we recommend using Network Discovery for discovering network devices instead |
Local tracking only, no other network devices are discovered. To discover network devices in combination with LsAgent, we recommend using Lansweeper On-Premise |
Tracks both the machine running Network Discovery and discovers IT (and later OT) assets remotely |
Asset data |
Expanded default IT discovery data set (extra data like user info on macOS) |
Default IT discovery data set |
Expanded default IT (and later OT) discovery data set (extra data like user info on macOS) |
Credentials |
No credentials required for local tracking (runs as local system or similar elevated user by default). Credentials are optional for remote discovery but we advise to use Network Discovery for discovering network devices instead. |
No credentials required for local tracking (runs as local system or similar elevated user by default). |
Requires credentials to get all asset details remotely. Can recognize assets without credential though |
Network access |
|
|
|
Auto update |
Auto update on Windows, Linux and macOS |
Auto update on Windows. Linux and macOS require manual updates |
Auto update on Windows, Linux and macOS |
Vulnerability risks |
Built on .NET 8.0 with a reduced vulnerability risk in comparison to .NET FW 4.8 |
Built on .NET FW 4.8 (Windows) and .NET 6.0 (Linux, macOS) |
Built on .NET 8.0 with a reduced vulnerability risk in comparison to .NET FW 4.8 |
It's time for us to let you try and test this new feature. We hope this first version will give you an easy-to-deploy agent-based discovery.
Finally, we're all ears! Your feedback is valuable, and we'd love to hear it.
Feel free to share in the comments or share your logs and screenshots privately to preview@lansweeper.com
Kind regards,
Gilian De Raes
Product Manager | Lansweeper
‎10-16-2024 03:10 PM
Hello,
I've just installed IT Agent on our first computer. After pasting a working code, the installation failed because a link to our Lansweeper site could not be made. From the log:
[2024-10-16 15:00:26] Unknown error while running curl.exe -k "https://localhost:59530/status/hub" -o "C:\Users\xxx\AppData\Local\Temp/ls_cloudlinking.json"
[2024-10-16 15:00:26] Setting variable IsLinkedToCloud from jq-win64.exe
[2024-10-16 15:00:26] Error running jq-win64.exe -r "\"\(.linkingInfo.isLinked)\"" "C:\Users\xxx\AppData\Local\Temp/ls_cloudlinking.json": jq: error: Could not open file C:\Users\xxx\AppData\Local\Temp/ls_cloudlinking.json: No such file or directory
Why does it look for a file that doesn't exist? Bug in the installer?
‎10-17-2024 12:33 PM
Hi @RGommersElcee , thanks for raising this issue.
I've created an internal bug for this ACME-26065
Meanwhile, you can download the latest IT Agent installer for Windows from "https://app.lansweeper.com > Scanning > Discovery systems > Downloads/packages" and save the following code as a new file called ITAgentCleanup.bat.
@echo off
:: BatchGotAdmin
:-------------------------------------
REM --> Check for permissions
>nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
REM --> If error flag set, we do not have admin.
if '%errorlevel%' NEQ '0' (
echo Requesting administrative privileges...
goto UACPrompt
) else ( goto gotAdmin )
:UACPrompt
echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs"
set params = %*:"=""
echo UAC.ShellExecute "cmd.exe", "/c %~s0 %params%", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs"
del "%temp%\getadmin.vbs"
exit /B
:gotAdmin
pushd "%CD%"
CD /D "%~dp0"
:--------------------------------------
:: Uninstall Lansweeper IT Agent
"C:\Program Files\Lansweeper IT Agent Discovery\uninstall.exe" --mode unattended
:: Sleep for x seconds to continue
TIMEOUT /T 300
:: Ensure lingering services are stopped and removed
sc stop "Lansweeper IT Agent Discovery Hub Service"
sc delete "Lansweeper IT Agent Discovery Hub Service"
sc stop "Lansweeper IT Agent Discovery Sensor Service"
sc delete "Lansweeper IT Agent Discovery Sensor Service"
sc stop "Lansweeper IT Agent Discovery Update Service"
sc delete "Lansweeper IT Agent Discovery Update Service"
:: Sleep for x seconds to continue
TIMEOUT /T 60
:: Delete default install directory
del /S "C:\Program Files\Lansweeper IT Agent Discovery\*"
:: Cleanup first reg location
for /f "delims=" %%a in ('reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Lansweeper" ^| find "Lansweeper IT Agent Discovery"') do (set "regs=%%a")
echo %regs%
reg delete "%regs%" /f
:: Cleanup second reg location
for /f "delims=" %%a in ('reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" ^| find "Lansweeper IT Agent Discovery"') do (set "regs=%%a")
echo %regs%
reg delete "%regs%" /f
:: Reinstall Lansweeper IT Agent
:: Todo: in the following line, correct the path to the actual location of theinstaller and also the cloudtokenvalue from your LS Site in https://app.lansweeper.com > Scanning > Discovery systems > Link discovery system. After doing so, uncomment the last line (removing the ::) and run this file
:: C:\Temp\Lansweeper-IT-agent-discovery-0.23.2-windows-x64-installer.exe --mode unattended --accepteula 1 --path "C:\Program Files\Lansweeper IT Agent Discovery" --cloudtoken cloudtokenvalue
Edit the last line in a text editor and run it on your computer.
‎10-14-2024 05:54 PM - edited ‎10-14-2024 05:55 PM
Searched around for a bit and didn't find the answer, but I want to make sure before I assume so... I remember IT Agent being limited to 500 assets but I can't seem to find if that is still the case.
Is IT Agent still limited to only 500 assets, or can we deploy company-wide?
‎10-15-2024 09:33 AM
Hi @rinks ,
We offer an FAQ on IT Agent, which you can find here: IT Agent Discovery: Frequently Asked Questions - Lansweeper. There you'll find the answer being there's no limit and you can deploy company-wide.
‎09-27-2024 04:58 PM
First and foremost I'm flabbergasted on the support Lansweeper provides for the IT Agent. The excuse is always in preview and unsupported. Go to this group. You would think being in preview ("beta") that they would want to know of any potential issues, but no. Ok, rant over.
I have linked our on prem server to the Cloud and installing the IT Agent on our machines with Intune and Jamf. The install is actually going quite well. However, I'm not sure how IT Agent assets function in the new cloud version. I know they do not show up in the on prem assets for now.
One of the questions I have... we have over 500 assets in Lansweeper. Most of those are now macs using the IT Agent. I have some IP Locations setup (they were setup in Classic) and machines are not being assigned to those locations.
From the looks of it, only machines from Classic with LsAgent are in these locations, but that is only like 50 or so. We are missing a bunch.
Is this a manual process? I've got machines in several offices and all over the world (some connecting over VPN) and would like to be able to look at an asset and know where it last connected. Is this even possible?
‎09-30-2024 11:11 AM
Thanks for raising this. We certainly want to know about potential issues as this improves the quality of our preview features for all users. Our current process is: GA features are covered by our global support team while Preview features are covered by the product/development team using this community and preview@lansweeper.com.
IP locations are used to give your IP ranges and VLANs a unique name, grouping the included assets based on their IP address. IP locations are specific to any LS On Premise installation and do not include IT Agent/Network/Cloud Discovery assets (yet). If you also use these discovery systems, you can create a new custom report in Reports > Create new report. When you use the fields and filter below you can create a report for each relevant IP range.
Fields:
‎10-02-2024 04:23 PM
Ok, I can do a report then to get the information I'm looking for in this way. However, it makes me wonder what the purpose of an IP Location in Lansweeper then? I may be misunderstanding what it is used for.
‎10-02-2024 04:28 PM
IP locations give you the option to address a filter of IP ranges with a chosen displayname. This is fully functional for LS On Prem but not yet ready for Network/IT Agent/Cloud Discovery. For this to work, IP locations should no longer require an "installation" property which they still do at the moment. We plan to solve this so IP locations are fully managed at the inventory side in your LS Site, across all assets, regardless of where/how they were added to your inventory.
‎10-02-2024 05:01 PM
Ok. For now I will rely on the Reports until the IP Locations work with IT Agent. thx
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now