Note on third‑party tools
We aim to provide accurate and helpful details about third‑party tools, but we can’t guarantee that this information is always complete or up to date. For the most reliable information, please always refer to the third‑party tool’s official documentation.
Licenseware is an add-on to Lansweeper. You can also acquire Lansweeper and Licenseware together in one combined subscription. See Lansweeper SAM, powered by Licenseware.
Network Discovery and the IT Agent usually find every device and installed application you need. The Licenseware integration reads that inventory through the Lansweeper API, so in most cases you don't need to install anything else.
For 2 use cases, add the Licenseware Collector alongside Network Discovery and the IT Agent. The Collector is a free agent that sends data directly from a device to Licenseware, adding evidence that the Lansweeper inventory doesn't contain:
- Usage evidence. You need to know which installed software people run, and when they last ran it, so you can reclaim unused licenses.
- Running-state evidence. You need to know what a server is running now, such as a database, middleware, or Java process, to calculate vendor-specific license positions.
If neither use case applies, use Network Discovery and the IT Agent only.
The Collector doesn't replace the IT Agent. A device can run both without conflict, because each one sends data to a different place.
Compare the Collector with Network Discovery and the IT Agent
| Network Discovery | IT Agent | Licenseware Collector | |
|---|---|---|---|
| How it works | Scans devices over the network | Runs on the device as a lightweight agent | Runs on the device as a background service |
| Sends data to | Your Lansweeper site | Your Lansweeper site | Your Licenseware tenant |
| Works off the network | No | Yes. The agent stores results and sends them when the device reconnects | Yes, if the device can reach the internet |
| Data collected | Hardware, operating system, installed software, and user information | Hardware, operating system, installed software, and user information | Adds software usage and running state: when programs last ran, which processes and services are running, and which users are logged in |
| Cost | Part of Lansweeper | Part of Lansweeper | Part of Licenseware |
The Lansweeper API integration sends Network Discovery and IT Agent data to Licenseware. Usage and running-state data reaches Licenseware only through the Collector.
In Licenseware, you set the priority of each data source. Licenseware uses the highest-priority source first, then fills any gaps from the next source. If a device sends data from both Lansweeper and the Collector, Licenseware joins the 2 records, and the Collector fills only the usage data that Lansweeper doesn't hold. You set the priority for each source as a whole, not for each data point.
What you will need
Before you start, confirm you have:
- On the Lansweeper site you're connecting, the Allow API clients to access this site permission. The Administrator and Application admin roles have it by default.
- A Licenseware account
- To install the Collector (optional): an enrollment token from the Licenseware platform, and administrator rights on each target device
Decide whether to use the Collector
Decision guide
| Situation | Add the Collector? | Reason |
|---|---|---|
| You need installed software, versions, and publishers for devices Lansweeper already scans | No | The Lansweeper API integration already supplies this data |
| Devices are remote or off the network, and the IT Agent already covers them | No | The IT Agent already reports their inventory |
| You need to reclaim unused licenses and require evidence of when people last ran each application | Yes | The Collector records execution history and running processes |
| You must prove which server software is running now for a vendor audit | Yes, on the servers in scope | The Collector records running processes, Windows services, and systemd units |
| You're not yet sure what you need | No | Run the default path first. Add the Collector only when a report shows missing evidence |
Which devices to install it on
Install the Collector on a selected set of devices. Don't install it on every device by default.
Install first:
- Endpoint devices, such as laptops and desktops, that run the software you want usage evidence for.
- Servers that run software with vendor-specific license rules, such as databases, middleware, Java, and Red Hat Enterprise Linux.
- Servers that an upcoming vendor audit or renewal will review.
Don't install on:
- Devices you don't own or manage, or that you have no authority to manage.
- Devices where privacy rules, works council agreements, or local law don't allow the collection of usage and logged-in user data. See the privacy considerations below.
Privacy considerations
The Collector collects personal data, such as local usernames, logged-in sessions, and per-user program execution history. It doesn't collect file contents, email or message content, browser history, keystrokes, screen content, or network traffic.
Before you deploy the Collector, follow the privacy guidance Licenseware publishes on its legal page. The Licenseware Collector documentation lists every item of data the Collector collects.
Set up the Lansweeper integration
For the prerequisites and steps to connect Lansweeper to Licenseware, see the Licenseware page in the Lansweeper documentation. This is the default path for most customers.
Install the Collector (optional)
Follow these steps if a use case from the decision guide applies to you.
-
Create an enrollment token in the Licenseware platform.
-
Install the Collector on each target device.
-
Register the device with the token.
For the supported operating systems, network requirements, and detailed steps, see these pages:
- Licenseware Collector documentation covers downloads, installation on Windows, Linux, and macOS, deployment with Intune or SCCM, proxy and certificate settings, and troubleshooting.
- Licenseware Collector overview in the Licenseware Knowledge Center gives a high-level description.
Checking results in Licenseware
After you install the Collector, open the Licenseware platform and check that the device appears in your project.
If it doesn't, see the logs and troubleshooting section and the quick reference section of the Licenseware Collector documentation.
Summary
- Connect Lansweeper to Licenseware with the Lansweeper API integration. This is the default path for most customers.
- Use the decision guide to check whether a use case needs usage or running-state evidence.
- If it does, install the Collector on the selected devices only, and register each one with an enrollment token.
- Check that each device appears in your Licenseware project.