Data Manager - Lansweeper

Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.

Introduction

Lansweeper is a tool produced by Lansweeper (the company) that is used for Asset Management.

Lansweeper is an Asset Management tool. Data can be consumed from either an on-prem instance of Lansweeper or a Cloud Instance. Two connection methods are available between Lansweeper and Assets Data Manager: an API connection and an SQL query.

How do I connect this tool to Assets Data Manager?

This task requires Data Manager Adapters admin permissions to complete. See how permissions and roles work in Data Manager.

Follow this procedure to connect this tool to Assets Data Manager using the custom-built Adapter:

Gather all of the information listed in the Data Manager Fields section, such as the Name, Object class, Data Source Name, and Data Source Type.
Gather all of the information in the Lansweeper Fields section—this may require consulting with the Lansweeper subject matter expert (SME).
Within Data Manager:
1. Create a new job by selecting the Adapter that matches your tool.
2. Configure all of the required fields with the appropriate information.
Within Lansweeper:
1. Follow all of the steps listed in the Authentication and Authorization section to properly configure Authentication and Authorization.
2. Review the information in the API Call section or the SQL Query, depending on the connection method used, and ensure the endpoints are available.
3. Review the Fields Retrieved section.

Each time this job is run, the data you have selected will be brought into Data Manager using the configured Adapter and become raw data.

To use this Adapter, ensure that the Lansweeper source is enabled with relevant firewall rules established and that the credentials to access the source have been provided.

Note that the authorization requirements differ depending on whether you are connecting via API or SQL.

Data Manager Fields

You will need to specify the following information from Assets Data Manager:

Name - the name of the Connection, visible as the job name in Adapters.
Object - the name of the Object Class you want to the data to be loaded into.
Data Source Name - the type of data being created, which is usually the tool name, e.g., AD, Qualys, etc. Note: This can be the same as Name.
Data Source Type - what type of data is the tool providing? For example, Assets, CMDB, user location, and more.

Lansweeper Fields

Source Type - select API or SQL depending on the connection type you desire.
For an API connection:
- API Token - A unique identifier that identifies the client to use for authentication.
For the SQL method:
1. Username - the username that must be used within Assets Data Manager to connect to Lansweeper. Ensure that the account used has Data Privacy set to none (full access) and the option Finder access enabled. This will allow the use of the Web API.
2. Password - the username that must be used within Assets Data Manager to connect to Lansweeper.

Authentication and Authorization

API Method (Source Type)

Authentication and authorization basics for Lansweeper when using the API connection.

In the Lansweeper home screen, select user's profile logo and then select Developer tools.
Next, select All applications.
At this point, you can create a new application by selecting Add new application. Select the application type as Personal Application.
After filling out all the fields and creating a new application, access the application in the EDIT APPLICATION screen. Use the Authorize button to redirect to the permissions screen.
Here, choose the token expiration time, select the site(s) you wish to grant access to and click ALLOW.
An application identity code is generated. This application identity code is the token and it is populated in the API token field in the Lansweeper job configuration information.

SQL Method (Source Type)

Ensure that the username has been provisioned with Read-Only access to the Lansweeper database.
For the SQL connection, you may also need to ensure that the Lansweeper database is accessible and viewable (i.e. any relevant firewalls are open).

API Call

The API call for Lansweeper is: getAssetResources 

Fields Retrieved - API

The following fields are retrieved with the API response:

assetBasicInfo.name
assetCustom.serialNumber
assetBasicInfo.domain
assetBasicInfo.ipAddress
assetBasicInfo.fqdn
assetCustom.department
assetCustom.manufacturer
assetCustom.model
assetBasicInfo.mac
assetCustom.warrantyDate
assetBasicInfo.lsAgentVersion 
assetBasicInfo.lsPushVersion 
assetBasicInfo.type
assetCustom.dnsName
assetCustom.deviceVersion
assetBasicInfo.lastActiveScan 
assetBasicInfo.lastChanged
assetBasicInfo.lastIpScan
assetBasicInfo.lastSeen
assetBasicInfo.upTime
assetCustom.lastChanged
assetCustom.lastPatched
assetBasicInfo.lastSccmScan 
assetCustom.stateName
assetCustom.location
assetBasicInfo.userDomain
assetBasicInfo.userName
operatingSystem.version
operatingSystem.caption
operatingSystem.buildNumber

Fields Retrieved - SQL

The following fields are retrieved with the below SQL query:

SQL query: tblassets.AssetID = tblOperatingsystem.AssetID

Select tblassets.AssetID,
  tblassets.AssetName,
  tsysassettypes.AssetTypename,
  tsysassettypes.AssetTypeIcon10 As icon,
  tblassets.IPAddress,
  tblassets.Lastseen,
  tblassets.Lasttried,
  tblassetcustom.Serialnumber,
  tblassets.Domain,
  tblassets.FQDN,
  tblassetcustom.Department,
  tblassetcustom.Manufacturer,
  tblassetcustom.Model,
  tblassets.Mac,
  tblassetcustom.Warrantydate,
  tblassetcustom.DNSName,
  tblassetcustom.DeviceVersion,
  tblassets.LastActiveScan,
  tblassets.LastIPScan,
  tblassets.LastChanged,
  tblassets.Uptime,
  tblassetcustom.Lastchanged As Lastchanged1,
  tblassetcustom.LastPatched,
  tblassets.LastSccmScan,
  tblassetcustom.State,
  tblState.Statename,
  tblassetcustom.Location,
  tblassets.Userdomain,
  tblassets.Username,
  tblassets.LsAgentVersion,
  tblassets.LsPushVersion,
  tblOperatingsystem.Caption,
  tblOperatingsystem.Version,
  tblOperatingsystem.BuildType
 From tblassets
  Inner Join tblassetcustom On tblassets.AssetID = tblassetcustom.AssetID
  Inner Join tsysassettypes On tsysassettypes.AssetType = tblassets.Assettype
  Inner Join tblState On tblassetcustom.State = tblState.State
  Inner Join tblOperatingsystem On

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community