Description

The purpose of this document is to provide a walkthrough of utilizing the ability to scan for custom Windows Management Instrumentation ( WMI ) items using the Inventory scanner included with Ivanti Endpoint Manager. This feature gives you the ability to pull WMI values from a client device and model them within the device's inventory. This allows the captured information to be included in reports, queries, etc.

Note: With the release of Endpoint Manager 2017.1, the ability to pull WMI information from non-standard WMI namespaces was added.

Resolution

1. On the core server, navigate to Tools > Reporting/Monitoring > Manage software list
   
2. Within the 'Manage Software List' expand 'Custom Data' and select 'WMI Items'. Within the pane that appears on the right-hand side, right-click and select and select 'Add'
   
3. Within the new window that appears entitled 'WMI Scan Item Properties' you will place the WMI call criteria necessary for obtaining the WMI information. Each object required is expanded on below:
   
   A. NameSpace: This is the WMI namespace. The most common namespace used is root\cimv2, however, this can be a different namespace such as root\security or root\microsoft to name a few.
   B. Class Name: This is where the WMI class name is input. This can be a number of things and can be found in in the level below the namespace. The class name is case sensitive, please keep this in mind when adding      this value.
   C. Display Object: The display object is used to determine where the data will be displayed within the inventory tree of the device. Items are listed in hierarchical order and must be separated with " - " (space dash space)      to accurately be displayed in the inventory. The first item input here is the name in the inventory tree that will contain the data, such as 'Custom Data', 'BIOS', etc..
   
   An example of possible input information can be found below:
   
   Once this information has been input click the 'Add' button.
4. Now that the WMI object has been added to the WMI Items, Properties can be added. The properties specify what the scanner searches for once it accesses the specified WMI namespace and class. In order to add properties, click the 'Add' button. Upon clicking the 'Add' button you will be able to input data into the 'Property Name' and 'Display Name' boxes as described below:
   Property Name: The property name of the WMI value in which you are wishing to pull information from.
   Display Name: This is the name used within the inventory tree to identify the WMI property. This input will appear one level below the 'Display Object' within the inventory tree on the device(s).
   
   Once these values have been input, click 'Apply' and then click 'OK'.
   
   Note: The 'Key' checkbox is used when a qualifier needs to indicate whether the property is part of the namespace handle.
   
   
5. Now click the 'Make available to clients' button to ensure the updated product definition files used by the inventory scanner are updated and attainable by the client for its next scan.
   
6. Run an inventory scan on your client device and ensure the data is being pulled in with the inventory scan. Below is a screenshot of the data returned for the example custom WMI item used for this document.
   

Discovering VMWare ESXi virtual hosts using Ivanti Endpoint Manager ( EPM ) version 2017.x

1. In order to discover VMWare ESXi hosts using Ivanti Endpoint Manager ( EPM ) version 2017.x you will need to enable Agentless scanning -- please see https://help.ivanti.com/ld/help/en_US/LDMS/11.0/Windows/inv-c-agentless-scanner.htm
2. Within the Management Console > Tools > Configuration > Self-electing subnet services > Agentless Scanner Settings -> Enable ESXi scan
   
3. Within the Management Console > Tools > Configuration > Credential manager > ESXi servers enter credentials for the VMWare ESXi host(s)
   

Within the Management Console > Tools > Configuration > Self-elected subnet services > Agentless scanner there is a tab "ESX Scan" where you will / should see "Enabled" if everything is configured and working properly

Within 24 hours within the Management Console > Network View > Virtual OS Hosts > All virtual OS hosts you will / should see VMWare ESXi host(s)

Additional information

https://help.landesk.com/docs/help/en_US/LDMS/10.0/Windows/umd-c-virtual-hosts.htm?Highlight=esxi

Discovery problems with VMWare ESXi hosts using default self-signed certificates

When installing ESXi, you have the option of using a built-in, self-signed certificate. The problem with this certificate is that the ESXi hostname defaults to "localhost" and the hostname won't be unique on the network or to UDD. UDD treats all hosts with the same hostname as a single host, resulting in a single entry in the inventory database for all hosts sharing that hostname.

VMWare strongly recommends that you not use the self-signed certificate in a production environment. For virtual host discovery to work correctly, all ESXi installations must have a unique CA-signed SSL certificate and hostname. See the following links for more information:

• http://kb.vmware.com/kb/2034833
• http://blogs.vmware.com/vsphere/2012/11/automating-ca-self-signed-certificates-for-esxi-5-1-for-use-with-resxtop.html

Download

DISCLAIMER

USE OF THE DBRepair.EXE APPLICATION SOFTWARE IS SOLELY AT THE USER’S AND/OR COMPANY’S OWN RISK.  THIS SOFTWARE APPLICATION IS AVAILABLE “AS IS,” AND LANDESK SPECIFICALLY DISCLAIMS ALL WARRANTIES INCLUDING ANY IMPLIED WARRANTIES.

Download the appropriate attachment and extract dbrepair.exe to the ManagementSuite directory on the core server. The path to the ManagementSuite directory is by default C:\Program Files\LANDesk\ManagementSuite.

Instructions for Use

1. Stop the inventory server service on the core server before running DBRepair.
2. Verify that DBRepair.exeis in the ManagementSuite directory. Double click DBRepair.exe to run it.
   
   Note: Once DBRepair.exe opens, anything that appears in the tree is unmodeleddata. This includes either custom data that you have deliberately added (via a custom data form or by modifying ldappl3.ini) or data corruption.
   
   
3. Delete database corruption if ifis present as it can cause various issues.
   
   Note: If you have no custom data that you want to keep, then click on Computer at the top of the window and click the 'clean' button. If you have some custom data that you want to keep, click on the data you do  *NOT* want to keep, and click the 'clean' button.  You will need to remove (clean) each unwanted item individually.
   
   
4. Close DBrepair.exe.
5. Restart the Inventory Server service.

Example

If an item in the DBRepair.exe tree list appears to be a valid part of the inventory tree, it's not. Keep in mind that everything listed is unmodeleddata, so it can be safely removed. You only need to keep the items that you have added specifically as Custom Data.

DBRepair.exe that looks like this:

Computer

-Custom Data

-Motherboard

-Loftwa6re

Normally there is no such value as Loftwa6re. Clearly, the Loftwa6re item represents database corruption. However, even though Motherboard looks valid, by virtue of it being in this list, it is not valid and it should be removed.

Overview

This article addresses how to resolve a specific issue with inventory records being overwritten due to duplicate device IDs in your environment caused by a misconfigured image or an imaging process that was done without correctly following your internal imaging process. Most likely the LANDesk agent was added to the image or was installed to a machine out of order during a new build.

Determining if this is caused by imaging with an EPM agent installed

Unfortunately, some of this is going to be you, your admin, or other console users saying that devices are just missing or not displaying in the network view. Noticing this issue may be occurring requires more detective work than a distinct and clear error.

If you are seeing weird behaviors with a batch of similar machines disappearing/reappearing in Inventory, review your Core server ldscan folder

%LDMS_HOME%ldscan\ErrorScan

When opening the various .scn files (.scn file extension is the OOTB default for EPM, your environment may be configured differently), you will be looking for the following information:

Device ID ={***************************************}

Device Name =***********

Network - TCPIP - Host Name =************

If you see multiple files with matching device IDs but different device name/hostname then you probably have an issue with how the machine was imaged

The reason these items are showing up in ErrorScan is because the core doesn't recognize the information even though it thinks it already has a matching device ID. Prove this by looking at the LANDesk Inventory Server warnings in the Application section of Event Viewer on the core

1. Run eventvwr.msc
2. Expand Windows Logs
3. Click Application
4. You can filter or sort by Source (this may take a few minutes)

Resolution

NOTE: As a user with Administrative privileges on the client device

1. STOP all LANDESK related services
2. Delete the following Registry Keys for 32bit clients:
   
   HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
   HKLM\SOFTWARE\LANDesk\Common Api\UniqueID
   HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
   HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
   
   
3. Delete the following Registry Keys for 64 bit clients:
   
   HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID
   HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID
   HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons
   HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog content
   
   
4. Delete C:\ProgramData\LANDesk (delete the entire directory and subdirectories, this is a hidden directory)
5. Run Security Scan - look for this line "Sending current settings information to core. Failed: Core has no inventory data for this computer". Without this step, you may encounter an error stating "LDISCN32: The inventory server [CORE] did not respond"
6. Open command prompt and run C:\"Program Files (x86)"\LANDesk\LDClient\LDISCN32.EXE /V /F /SYNC

Troubleshooting Inventory

Inventory Installation

Inventory is installed as a result of the agent installation and includes and/or uses the following files:

Installation files

• LDIScn32.exe
• ldapwhoami.exe
• AMTScanner.exe
• ClientRollingLog.dll
• ClientRollingLog.log4net
• elogapi.dll
• GatherProducts.exe
• GPMM.exe
• HPScanner.exe
• Lclxclnt.dll
• ldaccount.dll
• ldapinfo.dll
• ldappl3.ini
• ldapwhoami.exe
• ldavhlpr.dll
• LDISCN32.exe
• LDServerRoles.exe
• LDMBBApi.dll
• LDProfile.exe
• libhttp.dll
• loc32vc0.dll
• LocalPrtInfo.exe
• log4net.dll
• ltapi.dll
• processrunner.dll
• psapi.dll
• ServerScanner.exe
• ThinClientScanner.exe
• vulscan.dll
• WMIRulesScan.exe

Possible Installation issues

If the following option is checked within the agent configuration when the agent is deployed, you could possibly see a delay in the installation completing and the first inventory scan being sent:

To start: How to use 10 simple checks to Troubleshoot Inventory - Devices not updating, Duplicated or Missing Scans

In order to effectively troubleshoot Inventory a general understanding of the Inventory workflow is necessary.

Inventory Service Settings

Settings for the inventory service can be found on the core server by opening the 'Ivanti Configure Services' (SvcCfg.exe) application from the Start Menu, from the \Program Files\LANDesk\ManagementSuite\ directory, or by navigating to Configure > Services > Inventory.

For additional information on these settings as well as the Advanced Settings please click here.

Inventory Client Settings

Client inventory settings can be found within the agent configuration or agent settings options within the 'Configuration' menu in EPM.

For additional information on the client settings please click here.

General Inventory workflow

Initiating an Inventory Scan

Inventory Scans are initiated on the client by calling LDISCN32.exe.

LDISCN32.EXE is located in the LDCLIENT directory on the client.

Typically if there is an issue related to the scanner you will be asked to gather a debug output file.

From the run line on client computer run the following command:
"C:\Program Files\LANDesk\LDClient\LDISCN32.EXE" /F /O=c:\ioutput.txt

This will create an output debug file with additional troubleshooting information.

Client Initiated

1. Inventory scan launched through the Local Scheduler on the client
   
2. Inventory Scanner is run from the Ivanti Management Program group on the core server using the following syntax:
   

   "C:\Program Files (x86)\LANDesk\LDClient\LDICN32.EXE" /V

• A Managed Script is Scheduled and run the client computer through Scheduled Tasks.  This is accessed by going to the Distribution tool group, and then the Manage Scripts tool.  Within that tool there is an "inventoryscanner" script that contains the following commands:

Core Initiated

1. Right-clicking a computer or computers and selecting Hardware Scan, Hardware and Software Scan, or Full Sync Scan
2. Using the Manage Scripts tool.  Go to the Distribution tool set and select "Manage Scripts".  Within there is an "inventoryscanner" script.  Right click this script and schedule it.

Scanning for additional data such as registry keys, additional file types, etc

Scanning for additional data and other additional Inventory settings can be found in the Manage Software tool.

For additional information:https://help.ivanti.com/docs/help/en_US/LDMS/10.0/Windows/inv-c-settings.htm?Highlight=manage software

Communication with the Core Server

1. Inventory Scanner connects to the Core Server to get Scan Instructions using the Syntax below
   
   GET /ScanInstructions/InventoryService/PING/{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} (Where xxx .. is the Computers Device ID)
   After the Inventory Scanner completes running it posts the information to the Core "PostingData" web service using the following syntax taken from the IIS log:
   
   

   POST /postingData/scan.upload prefix=ldscan\decomp&suffix=.SCN

data-mce-style="padding-left: 30px;" style="padding-left:30px"

• TMP = This is a temporary file used when a client communicates to the core server.
• SCN = This is a regular scan file waiting for the Inventory Server to process.

By default, the server has a limit in scan file size of 10000000 (or 10 meg) for scan files.  This number can be modified in Configure Services -> Inventory -> Advanced Settings -> Max Scan File Size. If the number exceeds the set amount, scans will be moved to the ERRORBIGSCAN folder If the scan files in the LDSCAN folder exceed this number you can change this number to a more suitable one.

Inventory Server Service

Inventory Server Service file location

"C:\Program Files\LANDesk\ManagementSuite\LDInv32.exe"

Inventory Server Service Log Files

The service log file is located here: C:\ProgramData\LANDesk\LDINV32.LOGThe Event Viewer is an excellent way to view activity for the Inventory Server Service.  Useful events will be listed in the Windows Logs - Application section.You can filter by Event Levels "Critical", "Warning", and "Error" and then filter the Sources to show "LANDesk Inventory Server" to show only events relating to the Inventory Server Service.

1. From the Event Viewer - Windows Logs - Application log, click on the "Filter Current log" in the right-hand pane.
2. Select "Critical", "Warning", and "Error" in the "Event Level" section.

There are three different types of messages to look for:

• Out of sync scans: By default, the Inventory Server will "flag" a machine as out of sync if it hasn't heard from the machine in more than 24 hours. This basically means that the next time the device sends in an inventory scan it will be a full scan. When experiencing problems and backups with inventory a large number of these log entries are normal as the inventory catches up over the next 1-2 days.
• Errors: There are many possible errors that the Inventory Server can log so without going into detail it would be best to search the community for the error in question. There is usually a document or discussion that explains the error in more detail and how to correct it.
• Blocked Inventory Items: The Inventory Server will flag unknown or unexpected information in a scan file and block the scan from being inserted into the database. That information is recorded on the core under Configure - Services - Inventory Server - Unknown Items. Most of these entries are normal and should be left as blocked as they may contain corrupt information that doesn't need to be in the database, however, when using Custom Data, for example, the information may need to be allowed.

Possible Issues

Issue: Unable to start LANDESK Inventory Server Service and settings missing from Configure Services

Issue: Core Will Not Process Inventory Scan Due To Large File Size

Error: "The Inventory Server Did Not respond" when running Inventory Scan

Error: Committing on Table...Increased column size might be necessary (Event ID 4100)

Reinstalling the service

At times it may be necessary to remove and re-install the LANDesk Inventory Server service.

"C:\Program files\LANDesk\ManagementSuite\LDInv32.exe" /Remove"

"C:\Program files\LANDesk\ManagementSuite\LDInv32.exe" /install"

Managed Planet Core Scan Processor Service

If the "Enable Real-time Processing" option is turned on in Data Analytics the Inventory Scanner service will ask the core for Scan Instructions and normal scan instructions plus additional instructions are sent with Data Analytics data.  This includes active rules that are set in Data Analytics.

The service watches the LDSCAN folder for the .MP, .MINIMP or .MINI files.  The Managed Planet Core Scan Processor service must be running in order to process scan files as they come in.

When the "Enable Real-time" processing function is turned on in Data Analytics the Intermediate File Extension in Configure Services -> Inventory -> Advanced settings is set to ".MP' as depicted below.

If the Managed Planet Core Scan Process Service is not consuming the Data Analytics scan process and they are piling up in the MP_TEMP folder, check the account that the Managed Planet service runs with.  This account must have rights to access the LDSCAN folder.

Basic Troubleshooting Guide - Data Translation Services - Real-Time Processing

Enable Core Scan Debugging and Data Analytics Logging

Communication with the Core Server

The Communication process with the Web Service is the same as the regular process, but the files have a .MP, .MINIMP, or .MINI suffix and instead of the regular Inventory Server service processing the file the file is processed by the Management Planet Core Scan processor service and then modifies the scan file to ready it for LANDesk Inventory Server service and is moved to the regular LDSCAN folder.

Service file location

"C:\Program Files\LANDesk\ManagementSuite\MPCore.exe"

Log Files

C:\Program Files\LANDesk\ManagementSuite\log\MPCore.Exe.Log

Possible Issues

Issue: MP files are collecting in the LDSCAN folder

Thousands of .MP files are stacking up in the LDSCAN folder

The following rules should not be made active due to performance impact:

Web Import

B2B Connectors

Import Data

Calculate Data

Tasks

Inventory is run based upon the criteria inventory settings criteria within the agent configuration. You can view the scheduler tasks through the local scheduler on the device by following the documentation below:

How To: View Local Scheduler Tasks on a Client

When running a task from the core server you may encounter various Status messages as the scan progresses,

Directories

Registry Keys

Database Tables and Inventory Information

Quick SQL Script to find all of your Inventory Attributes in your LANDesk Database

How to determine the table size of a Microsoft SQL Server database

How to find out Database information for Inventory Items by the Object or Attribute name

Gathering logging information for Ivanti support

About Inventory Scanner Switches

How to generate an inventory output file from a client for LANDESK support to do further troubleshooting?

How To: Enable XTrace Diagnostic Logging for the LANDESK Core and Clients

Standard Log Files

Windows Application Event Viewer - Most LANDesk Inventory Server errors or exceptions are logged to the Application Log

Gatherproducts.log - \Program Files (x86)\LANDesk\LDClient\Data

ldiscn32.log - \ProgramData\LANDesk\Log

LDInv32.exe.log - \Program Files\LANDesk\ManagementSuite\log\

Trace Log Files

ldapwhoamixtrace logging - ldapwhoami.log - \ProgramData\LANDesk\Log

Note: This log file will only be created if xtrace in enabled.

Debug Logging

Debug Scanner log - ldiscn32.log - \Program Files (x86)\LANDesk\LDClient\Data
Inventory Server Service log - ldinv32.exexxxxx_xxxxx.log - \Program Files\LANDesk\ManagementSuite\log\LDInv32.exexxxxx_xxxxx.log

Note: This is the rolling log and must be manually enabled in Configure | Services | Inventory | Advanced Settings | Use Rolling Log = 1 on the core server.

Performance Issues

Performance issues are typically manifested by scans not processing or scan processing too slowly.  Further information on making sure this process goes smoothly can be found here in How to keep inventory up to date and flowing correctly.

Check the DoDelta setting through Configure Services

Ensure this setting is set to 1 unless otherwise specified, otherwise, every scan that comes in will be a full scan which can inhibit performance.

About Inventory Delta Scans

Active Rules configured incorrectly

What rules should be Scheduled and not included in the DTS Active group for Data Analytics?

Overall tuning for EPM and MSSQL

IIS Troubleshooting and LANDESK Management Suite: 101

Recommendations for tuning EPM (LDMS) and MS SQL for large enterprise Core Servers

How to troubleshoot IIS using Log Parser Studio from Microsoft

Overview

During inventory troubleshooting Ivanti support may request an inventory output file or a dubug of the inventory scanner for further troubleshooting.

Here are the steps to generate the inventory file from the client machine manually depending on the OS of the client.

Windows

1. On the client machine, open a run prompt (Windows Key + R) and enter the following command:
   
   LDISCN32.EXE /f /v /sync /debug /o=C:\Windows\Temp\Output.txt
   
   
   
   

   Detailed information on the inventory scanner switches can be found in this document: About Inventory Scanner Switches

2. Once the scan finishes, the scan output text file (Output.txt) will be in the C:\Windows\Temp\ folder. The debug log will be file located in C:\Program Files (x86)\LANDesk\LDClient\Data\ldiscn32.log. Send both of those files to support for further troubleshooting.

Mac

1. Browse to Library\Application Support\LANDesk\bin and Open the LANDESK Agent.app
   
2. On the Inventory tab, click the lock in the bottom left to change the settings. (This will prompt you for your credentials)
3. Click the box "Save scan in directory", "Force Software Scan", and then click the Lock again to lock the settings:
   
4. Now click on the Overview tab and click the "Scan Now" next to the Inventory Scanner:
   
5. After the scan finishes, browse to Library\Application Support\LANDesk\Scans and grab the latest scan to send to support. It is also recommended to grab the latest Mac log file as well. See the links below on how to gather those logs depending on your agent version.

Linux

1. Browse to /opt/landesk/bin
2. Run ./ldiscan -f -V255 -o /tmp/output.scn
   
3. Copy the scan off of the device and send it to support. If needed, you can also gather the Linux logs and send those to support as well. See the link below on how to gather those logs.

Wondering what the best practice is, if there is one, for how to treat device inventory records when a device is decommissioned. Under what circumstance would I archive a device, and when should I just delete it?

• Problem
  • Cause
  • Workaround 1
  • Workaround 2
  • Example of exact problem replication steps
• Solution
  • Requires Access To
  • Verification example

Problem

On some client machines, the inventory seen from the console level is almost empty. The issue comes from the presence of some incorrect registry keys in CustomFields. Usually, even if these keys have been authorized in "Configure > Inventory > unknown elements" they do not appear in "Configure > Inventory History / Custom Data > Registry > Landesk Custom Fields".

Cause

If your Core has just been migrated from an older version, those keys probably existed already in one of your older version of LANDESK, but did not cause such an inventory error. There may have been a problem during the schema update process during installation.

Workaround 1

If you do not need the blocking registry keys just delete those keys from the client registry. The inventory should then be displayed correctly.

Workaround 2

1. Rename the impacted key in the METAATTRIBUTES table of your database.

2. Restart the inventory service on your Core server.

3. Launch a complete inventory scan on the impacted client computers.

4. After that, the inventory display should not be blocked anymore

Example of exact problem replication steps

• Inventory of the impacted machine S1003FR1 seen from the console level => Inventory almost empty:

• Inventory history: the key, which is well present in the inventory of the machine does not appear in the history.

• Inventory of the same machine S1003FR1 seen in the web console => the key DAL-FLU-06 does not appear.

The table that contains the names of the variables used in the inventories: METAATTRIBUTES

• In the METAATTRIBUTES table, replace the impacted key DAL-FLU-06 by another one like for example DAL-FLU-X6
• Restart the inventory service.
• On the inventory display of your impacted workstation (let's say S1003FR1) that did not complete a full inventory scan yet, the inventory should be blocked now by the key "DAL-FLU-X6" just after renaming it in the database.

• Launch a complete inventory scan now on the impacted computer. After that it should not be blocked anymore by the key DAL-FLU-06:

• Launch a complete inventory scan on another impacted client machine - let's say S1082fr2FR2
• The inventory display of the S1082fr2FR2 should be correct now.

• The key DAL-FLU-06 should appear again in the "Unknown Elements"

• Let's authorize the key DAL-FLU-06.
• Restart again the inventory service.
• Relaunch a complete inventory scan on S1082FR2
• The inventory display of S1082fr2FR2 should be still correct, and the key DAL-FLU-06 should now appear in the "Custom Fields" in the console.

• Add another blocking key "FIL-BEA-01S" to the registry of the same client machine S1082FR2 (this key were blocking the inventory display of other client machines)
• Relaunched a complete inventory scan on S1082FR2
• The inventory of S1082FR2 should be now blocked again

Solution

1. Stop the inventory service on your Core server

2. Launch a DB Repair with a cleaning of corrupt or incorrectly positioned entries - more info at How to download the Database Repair Utility (DBRepair.exe). You should clean all the corrupted values as well as duplicate root "custom data" in your language as well as in English.

3. Launch a CoreDbUtil in order to update the schema and display name with the correct language - more info at Running CoreDbUtil to reset, rebuild, or update a database.

4. Restart the inventory service

5. Complete cleaning of unknown inventory items to start with a healthy database and revalidate it on a case-by-case basis after receiving each new inventory scan.

Requires Access To

Database Server Access is required to complete these steps.

Verification example

• When we tested the client machine S1082FR2 the inventory was no longer blocked, but the key FIL-BEA-01S did not appear.

• It was present, however, in the registry of this machine.

• When we started a synchronization inventory scan the key started to appear again in unknown elements.

• We authorized the key and relaunched an inventory scan. Then the key appeared correctly in the console without blocking the display anymore.

• Why do we need it ?
• Versions list
  • 2018.1
  • 2017.3
  • 2017.1
  • 2016.3
  • 2016

Why do we need it ?

You can use the ldiscn32.exe version to check the version of the agent installed on the device. This can be done easily using a query. For additionnal informations, you can check How to: Easily determine LANDesk agent name and version using a query.

Versions list

2018.1

2017.3

2017.1

2016.3

2016

• Open up SQL management studio
• Right click on your database and select "New Query"
• Paste in the following query:
  
  

SELECT TABLE_CATALOG, TABLE_NAME as tablename,COLUMN_NAME as columnname, DATA_TYPE,CHARACTER_MAXIMUM_LENGTH, *

FROM INFORMATION_SCHEMA.COLUMNS

WHERE TABLE_CATALOG = '<epmdatabase>' order by tablename,COLUMNNAME

• Replace <epmdatabase> with the name of your database.
• Right click on the results and select save results as.

Issue

When attempting to perform an Inventory scan or Patch and Compliancescan request from Windows Console the Status of requested actions returns the Results seen below. Although this indicates that CBA is malfunctioning you can see in the image below that the Agent Status icons will often report correctly.

CBA 8, no certificates were found on the core server

Cause

     Most commonly presented on Core servers recently upgraded with an inline methodology. The Core server is using an old certificate that does not exist on the client when requesting connections.

Resolution

1. Validate that the HTTPS bindings of the Default Web Siteare configured to use the LANDesk Secure Token Serveras seen in the image to the right:

2. Move all but the latest modified *.cer, *.crt, *.key and *.0 files from LANDesk\Shared Files\Keys  to a new folder called Backup Keys

   • Note: The remaining .0 file should match the certificate found on the client

3. Flush all temporary ASP.NET files like so:

   1. Stop IIS (IISRESET /Stop)

   2. Delete all files and folders from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

   3. Start IIS (IISRESET /Start)

4. Restart all LANDesk and Managed Planet services with the following command in an elevated PowerShell:

   • Stop-Service -DisplayName LANDesk*,Managed* -Verbose -Force;  Start-Service -DisplayName LANDesk*,Managed* -Verbose

          If issue reoccurs, please perform the following steps:

          1. Open IIS Manager

          2. Go to Application Pools > LDAppMain > Advanced Settings...

          3. Change Maximum Worker Processes value to 2

          4. Change Regular Time Interval (minutes) value to 240

          Please contact Ivanti support if the above steps do not solve an issue.

Description

Within some environments, there have been reports of the Landesk Scanner Group WMI rules causing the inventory scanner to take a substantial amount of time to complete.

Cause

The WMI calls within Tools > Data Analytics > Discovery Services > WMI Groups > Landesk Scanner are experiencing issues accessing the classes for the components within the scanner list.

Resolution

Within the 2017.1 SU1 release of Endpoint Manager, an option to disable this scan from running has been implemented. In order to disable it please complete the following:

1. Navigate to Configure > Services and select the 'Inventory' tab.

2. Click on the 'Advanced Settings' button and within the new window navigate to the 'Do WMI Rules' option. Alter the value from a '1' to a '0', click 'Set' and apply the changes.

Note: As seen in the graphic below, this will result in a restart of the Landesk Inventory Service.

Description

How to : Check which agent settings are used on a client.

It can be very useful to check which agent settings are used on a client to troubleshoot issues when agent isn't behaving as expected. In this article, we are going to explain how to check agent settings on a particular device. Keep in mind that you can create a query to show agent settings used on all devices as explained in article How To: Create A Query To View Agent Settings.

Solution

We are going to use a Distribution and Patch settings for this example. However, this process applies for all type of settings and OS (mobile device included).

1. Go the Network View.

2. Double click on the device you would like to check to open inventory.

3. Go to Landesk Management > Agent Settings > Distribution and Patch.

4. Take note of settings name. In this example Distribution and Patch Settings 16.

5. Open Tools > Configuration > Agent Settings.

6. Scroll down to All Agent Settings.

7. Open the Distribution and Patch section.

8. Find the agent settings name noted previously and open it.

You can now check the settings applied on the client.

Last week I added some Custom Data fields (registry values for Java Update info).  After the inventory scan, the values showed up for the machines (JavaRT & Policy)

Over the weekend I ran a job to update the registry enties to what we require and inventory got updated as picture above.   However, upon reboot, the registry entries reset to the original values (that;s a different can of worms).

The Inventory has not reverted even with a FULL SYCN SCAN.   If I use REGEDIT on the machine the values are different then the LDMS Inventory.

At this point I can't trust the Custom Data I have in inventory.

How can I get this corrected?

I'm running LDMS 9.0, SP3.

Thanks for your help.

Issue

Custom Data is not being sent in inventory or you would like to start pulling registry information using the Custom Data registry pulls.

Cause

There are a number of different problems that can cause this issue. See solution below for further troubleshooting

Solution

First, let's take a look at the formatting of the Custom Data to better understand how that data is being saved and how the data is pulled. Most issues with Custom Data come down to a configuration issue. This could be a misspelled path, a trailing space or \ at the end of the path, not selecting "Make Available To Clients" on the Custom Data window, and some other issues that will be explained in this document.

First, we will break down the different sections of the Registry Items. Use this image below and numbers for references

Section 1 - Root Key: This will usually be set to HKLM (HKEY_LOCAL_MACHINE). If you need to pull registry information from HKCU please follow this document: How to Get Data from the HKEY_CURRENT_USER (HKCU) registry root?

Section 2 - Key: This is the path that follows HKLM. In this example, we are pulling the information from the key SOFTWARE\CustomData. This is how that path looks like in Regedit:

Once you know where the data is located in Regedit, you can easily copy the path from Regedit by highlighting the data you want to pull, selecting Edit - Copy Key Name, and then entering that path into the Key Value in Custom Data:

Copying the path this way helps alleviate any issues caused by misspelling for incorrectly entering the path in Custom Data.

Once copied, you need to remove the "HKEY_LOCAL_MACHINE\ " from the copied path since that is already selected in the drop-down menu from section one:

Now that we know the path is valid let's continue on to value.

Section 3 - Value: This is the name of the value in Regedit. In this example, the name is TestMe. Make sure when you enter this value it is spelled exactly how it is seen in Regedit and has no trailing spaces when entered:

Now for the last section, Attribute Name.

Section 4 - Attribute Name: This is how the data will show in inventory. This path can be named however you would like. We recommend keeping the attribute name Custom Data as the top of the tree just for organizational purposes. You can use a more detailed tree but make sure each section is denoted by a hyphen ( - ) and a space on both sides of the hyphen like so:

The last step is the publish the list. In the toolbar for the Manage Software List is computer with a green arrow() this is how the devices get updated on what registry items to scan for. If you haven't already pressed the button, the window will show "(Unpublished)" like so:

Once you are confident that the custom data has been entered correctly and the attribute name has been set up how you would like, press the "Make Available To Clients" button to let the devices know there is an update to the registry list. The registry information will now be scanned on the next inventory scan. You can expedite this process by requesting an inventory scan from a device that has the previously set up registry key to confirm that everything is working. This is how my custom data shows in Inventory:

NOTE: If you have followed all of the previous steps and your registry data is still not coming in, please review the following document to make sure the data isn't being blocked: Issue: Custom Data is not Entered - Using the Unknown Items Inventory Tool

Recently  we are facing issue with inventory scans not working on most of new client machines. We are able to successfully push the Landesk inventory agent  to a new PC. It seems to install fine but the PC is still sitting in Pending Unmanaged Client Deployment. It fails when sending scan results to the core server. When I tried to run a inventory scan manually ,it fails and displays the below error.

Inventory Services seem to be up and running within the PC and core server.
I can telnet from the PC to the core with ports 5007.
Windows firewall is disabled.

Appreciate your timely help and support on this

Next, I havent configured anything under cloud services appliances,does it have anything do with this inventory scan fail?

We are a Dell shop.  We're using Dell Command|Configure to access the BIOS information from within Windows.  Dell CC can spit out a .ini file listing the characteristics, one per line, like "sysname=OptiPlex 7020".  I would like to include these in each machine's inventory.  I've tried the following approaches, but haven't gotten any results to show up in the Inventory of a machine that I know has the file.

How to read content of INI files on clients into the inventory scan
https://community.ivanti.com/docs/DOC-22005

How to Include Contents of LDAPPL3.INI in inventory
https://community.ivanti.com/docs/DOC-42549

Gather INI information via inventory
https://community.ivanti.com/thread/16610

It would be very helpful, especially as we're trying to implement a directive to add a BIOS password to every machine, if we could pull this .ini file into Inventory in a way that we could then query on the results.  What's the best way to do this?

Issue

A managed device inventory scan is rejected with the following error:

Event ID 4100, Database exception, <scanname>.scn, LDInv.dll -2147467259. 

Data provider or other service returned an E_FAIL status. 

Error committing on table SERVICES: DATA PROVIDER OR OTHER SERVICE RETURNED AN E_FAIL STATUS. increase column size might be necessary, Thread ID. xxxx.

Cause

Intel is providing an "Intel Driver Update Utility" that you might be invited to install when updating drivers from the Intel Corporate website (downloadcenter.intel.com).

This will install the utility; however, the path for the service is over 1400 characters long.  For example:

Path ="C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\esrv_svc.exe" "--AUTO_START" "--start" "--address" "127.0.0.1" "--port" "49330" "--depend_on_key" "SYSTEM\CurrentControlSet\Services\ESRV_SVC_WILLAMETTE" "--depend_on_value" "run" "--time_in_ms" "--pause" "5000" "--library" "C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_modeler.dll" "--no_pl" "--watchdog" "10" "--watchdog_cpu_usage_limit" "50" "--end_on_error" "--kernel_priority_boost" "--shutdown_priority_boost" "--device_options" " time=no output=w output_folder='C:\ProgramData\Intel\SUR\WILLAMETTE\IntelData' limit_output_by=time output_limit=3600000 output_buffer=1024 il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_process_input.dll','process_input_options.txt' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_system_power_state_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_quality_and_reliability_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\acpi_battery_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\sema_thermal_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\wifi_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\devices_use_input.dll','service=yes' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_disktrace_input.dll','pause=60000 working_dir=C:\ProgramData\Intel\SUR\WILLAMETTE\IntelData override_existing_tracing=no limit_output_by_filesize_mb=10' os='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\os_counters.txt' "

The LANDESK Inventory Database's "Path" column size is only 1024 characters long, so inventory scans containing the above information are rejected.

Resolution

To resolve this issue, you need to:

1. Backup your database
2. It is recommended to turn off the LANDESK services before manipulating the LANDESK database
3. In Microsoft* SQL Server Management Studio, run the SQL statement:  ALTER TABLE Services ALTER COLUMN Path nvarchar(2048)

Purpose

This article will tell you how to generate a login/logout report of a user for all the workstations. This information is gathered by Vulscan in dbo.PatchHistory table.

Requires Access To

Database Server Access is required to complete these steps.

Instructions

If you need to gather this information only for a few machines you can do it step by step on each device via Patch Manager. To do it please follow this article. However, if you need to generate such a report for all your machines, the only way to do it is a new SQL query. The information visible in the abovementioned article is stored in the "Message" column of the dbo.PatchHistory table. If the "Message" cell is empty, you can also deduct it from the "ActionCode" column, where the code 40 corresponds to a connection event and the code 39 corresponds to a disconnection. In the column "CurrentUser", you can find the name of the user concerned. In the same table, you have also the column "Computer_Idn" by which you can correlate this table with the dbo.Computer table.