Landesk
Configure the Landesk connector to retrieve asset information from Landesk
Objective
The purpose of this document is to provide you with a procedure for setting up the connection with Landesk. This procedure will allow you to retrieve asset information (VMs, etc.) from Landesk.
Prerequisites
CSV Export
The extract must contain all necessary fields, including the Bitlocker status of hard drives.
API
Prerequisites
- Implementation of a site-to-site VPN.
- Opening of flows to the Landesk server (HTTP / HTTPS) according to the server installation mode via VPN.
Required Data
- Provision of the server IP Address.
- Creation of a Username and Password.
- Assignment of the Auditor role in Landesk.
- Addition of the user to the Microsoft security group "Landesk Management Suite".
Configuration Steps
1. VPN Setup
Ensure that a site-to-site VPN is established between your network and the Landesk server infrastructure.
2. User Account Creation
- Create a dedicated service account in Active Directory
- Assign the Auditor role in Landesk Management Suite
- Add the user to the "Landesk Management Suite" security group
3. Network Access
- Configure firewall rules to allow HTTP/HTTPS traffic to the Landesk server
- Verify connectivity from the connector to the Landesk server
- Test authentication with the created service account
4. Data Validation
- Verify that all required asset fields are accessible
- Confirm Bitlocker status information is available
- Test data retrieval through the API
Information to provide in OverView
| Field | Description |
|---|---|
| Server URL | Ivanti Landesk server URL |
| Username | Username for authentication |
| Password | User password |
| Use NTLM Authentication | Use NTLM authentication method |
Ensure that your VPN connection is stable and that the necessary firewall rules are in place before configuring the connector.
- Use a dedicated service account with minimal required permissions
- Regularly rotate service account passwords
- Monitor API access and usage logs
- Ensure VPN connection is properly secured
Parameters
These parameters are optional. Leave them at their default value unless you have a specific reason to change them.
| Parameter | Description | Default |
|---|---|---|
| Column Sets | JSON configuration for mapping Landesk API column sets to asset fields (hardware and software). Defines which column sets to query and which columns to extract for each resource type. Example: {"hardware": {"disk_encryption_status": {"column_set": "Bitlocker", "column": "Computer.Mass Storage.Drive Encryption.Conversion Status"}}} | — |
| Verify SSL | Verify SSL certificate when connecting to the API | Disabled |
Conclusion
By following these steps, you will be able to configure the connection between Landesk and retrieve asset information. Ensure that all prerequisites are met to avoid any errors during integration.
Alternative: file import through DropPoint
The API access described above is the recommended method for this connector. Where it is not available (a segregated network, a version or licence without API, an export you already produce), OverView accepts file exports, to be uploaded to the bucket dedicated to Ivanti Landesk.
Bucket : s3://landesk/
Example : s3://landesk/export.csv
The procedure is described in the OverView DropPoint guide: generating credentials, configuring the client, then sending files from the OverView web interface, the AWS CLI or an SDK. Its examples come pre-filled with this bucket when you follow this link.