From Lansweeper Inventory to a License Position

The Lansweeper logo beside LICENSEWARE product screens: the Lansweeper Cloud data source feeding five apps, the SQL Server overview and Java licenses required.
LICENSEWARE

Lansweeper + LICENSEWARE: your inventory, your license position

If you run Lansweeper, you already know what is in your estate. Lansweeper finds managed and unmanaged assets across IT, OT and cloud. You can see which servers you have, which virtual machines run on them and what software is installed on each.

A software vendor asks a different question. It wants to know how many licenses that estate needs under its own rules. Oracle counts processors, Microsoft counts cores and client access licenses, and Red Hat counts socket-pairs. Answering that usually means exporting the inventory, rebuilding it in spreadsheets and reading the contract terms by hand. The data was never the problem. Turning it into a position took the time.

That is the job LICENSEWARE does with your Lansweeper data. You keep the platform you already run. LICENSEWARE reads the inventory it holds and works out the license position. No second agent goes onto your devices.

Your inventoryDevices, installed software, hardware and virtualization
Seven LICENSEWARE apps
Your license positionLicenses required, under each vendor's rulesInstalls set against your entitlementsEvery result traced to the source record

What the integration does

LICENSEWARE connects to Lansweeper Cloud through the Lansweeper API. You choose which Lansweeper sites to share. LICENSEWARE then reads the devices and the software installed on them, and syncs on a schedule. Lansweeper's documentation lists three data types you can turn on: hardware and virtualization data, installed Microsoft software, and Java installations with device user information.

If you run Lansweeper On-Prem, you export custom reports from Lansweeper and upload them to LICENSEWARE. Lansweeper lists the integration for Lansweeper Cloud and On-Prem version 10.0.1 or higher, on the Pro and Enterprise plans.

Works withLansweeper Cloud, On-Prem 10.0.1+
Lansweeper plansPro and Enterprise
SyncTwice a week
First importUp to 24 hours

Seven LICENSEWARE apps read your Lansweeper data, each for its own question:

NEO, the LICENSEWARE AI SAM analyst, answers licensing questions across all of it, from your own data.

On lansweeper.comLICENSEWARE in the Lansweeper Integrations directoryThe LICENSEWARE listing in the SAM category, with its requirements and the bundle, on Lansweeper's own site.

Setup, step by step

These steps summarize the LICENSEWARE help center guide and Lansweeper's own documentation. The full screens are in both.

In Lansweeper Cloud

  1. Sign in as an administrator. Your role needs permission to let API clients access the site.
  2. Open Developer Tools, go to API clients and create an API client.
  3. Choose Personal Access Token as the authentication method.
  4. Give the client a name and set Integration to LICENSEWARE.
  5. Choose when the token expires.
  6. Grant access to the sites you want to sync, then create the client.
  7. Copy the token. Lansweeper shows it only once.

In LICENSEWARE

  1. Open Datasources, search for Lansweeper and select Lansweeper Cloud.
  2. Select Connect, paste the token, verify the connection and save the credentials.
  3. Turn on the data syncs for the apps you need.

The first import can take up to 24 hours to process. After that, LICENSEWARE syncs twice a week. The connection belongs to the LICENSEWARE project you set it up in, and that project sits in the region you signed up in. LICENSEWARE is SaaS only, in three separate production regions: European Union (West), United States (East) and Australia (APAC). It is SOC 2 Type 2 audited.

Three questions you can now answer

Question 1

How many SQL Server core licenses do your VMware hosts need?

Microsoft Deployment Manager reads the SQL Server installs Lansweeper reports. Infrastructure Mapper places each virtual machine on its host. Together they give a core count you can defend.

The SQL Server overview in Microsoft Deployment Manager: SQL Server installs split into virtual and physical
Microsoft Deployment Manager: SQL Server installs, virtual and physical.

Question 2

Which of your devices run Oracle Java, and on which versions?

Oracle Java Deployment Manager reads the Java installations Lansweeper already found. You see the exposure before the next conversation with Oracle.

Licenses required in Oracle Java Deployment Manager: Java versions with licensing by processor, named user plus and employee
Oracle Java Deployment Manager: licenses required per Java version.

Question 3

Where do your installs exceed your entitlements before the next renewal?

License and Contracts Manager sets your agreements and renewal dates against the installs in your Lansweeper inventory. You go into the renewal knowing what you use and what you can drop.

The contract renewal timeline in License and Contracts Manager: renewals over the next 12 months grouped by days to renewal
License and Contracts Manager: every renewal in the next 12 months, by days left.

Every result traces back to the source record in Lansweeper, so you can produce the evidence when you need it.

Better together

Lansweeper gives you an inventory you trust. LICENSEWARE turns it into a license position you can act on. Neither one replaces the other, and you do not collect anything twice.

LICENSEWARELansweeper integrationHow the integration works, step by stepWhich apps read your Lansweeper data, Cloud and On-Prem, and the questions people ask before they connect.

Get started

Alex Cojocaru

Alex Cojocaru

Alex has been active in the software world since he started his career as an Analyst in 2011. He had various roles in software asset management, data analytics, and software development. He walked in the shoes of an analyst, auditor, advisor, and software engineer, being involved in building SAM tools, amongst other data-focused projects. In 2020, Alex co-founded LICENSEWARE and is currently leading the company as CEO.