Purpose: Inventory can be perhaps called the backbone of LANDESK. Almost everything relies on inventory. Remote Control, Provisioning, Reporting, and the list goes on and on. In fact some provisioning tasks cannot be launched without the ability for a mini scan to reach the core server and be processed in a timely manner. Remote Control may fail if the IP address in inventory is not up to date and these are just some examples. If there is one thing a LANDESK Admin should understand and keep working it would be inventory. This guide was written to help understand the basic way that inventory works and how to troubleshoot common problems. This is not an in-depth guide on everything that can go wrong with inventory but more the basic information that every administrator should know.

Flow: Although this document is going to cover core and client side inventory most of the flow happens on the core side. Inventory (like several other folders in LANDESK (alertqueue, brokerreq, sdstatus, vulscanresults)) are queue folders. That is...files arrive at the core and are distributed into these folders. Services on the core then watch these folders and process the files contained within. Since these are queues several problems can arise if the folders get backed up.  The C:\Program Files\LANDESK\ManagementSuite\LDScan folder is the queue folder that this document is focusing on and we will first cover file types found in the folder as well as the sub-folders.

Services that watch the LDScan Folder:

• Management Planet Core Scan Processor (LANDesk Data Analytics or LDDA)
• LANDesk Inventory Server

File Types:

• MINI = This is an intermediary file type used by the Core Scan Processor (LDDA).
• MINIMP = This is a mini scan waiting for the Core Scan Processor (LDDA) to process
• MINISCN = This is a mini scan waiting for the Inventory Server to process.
• MP = This is a regular scan file waiting for the Core Scan Process (LDDA) to process
• SCN = This is a regular scan file waiting for the Inventory Server to process.
• TMP = This is a temporary file used when a client communicates to the core server.

Sub-folders:

• ErrorBigScan = Inventory has a default scan file size limit of 10mb. Any scan larger than this will end up in this folder instead of the database. The size can be increased in the Configure - Services - Inventory Tab - Advanced Settings button however the larger the size the more time it will take for the Inventory Server to enter the file into the database.
• ErrorScan = If the inventory has a problem with the scan received it will end up in this folder and a message in the OS Application Event Log will be generated.
• Storage = This is an optional folder that may or may not show up. By default the inventory server will remove all scans unless the option is turned on to keep them.
• ErrorTrans = These are scans that had a problem while transmitted to the core.
• Decomp = Scans related to encryption/compression

Process:

1. Scans arrive at the core server. If LDDA is licensed and enabled on the core then the files will be MP, MINIMP, or MINI otherwise they will be MINISCN, or SCN.
2. If LDDA is in use the Management Planet Core Scan Processor (LDDA) will pickup the files and run it's active rules on them.
3. Once LDDA is done (or if it's not enabled) the file type will be changed to MINISCN or SCN.
4. The Inventory Server picks up the files and enters them into the database.

Core Side Problems: Since the LDScan folder is a queue folder it's important to tell if the queue is completely stopped or working slowly. The folder (like all queue folders) should be empty or processing at a good speed at any given time. Troubleshooting steps will depend entirely on how the queue is working.

Technics for watching the LDScan folder:

• Using the right-click properties window over and over and over. This will produce a high number of files (as it includes sub-folders) but after repeated attempts at this you should be able to tell if the total number of files is going down consistently or never going down and going up instead.

• Clicking on a file in the LDScan folder. This option is available to newer OS's and will produce a total number at the bottom.

Complete Stoppage: The number of files in the LDScan folder is never going down or staying the same.

Troubleshooting possibilities:

• Restart the corresponding service. See the "File Types" section at the top of this document. As mentioned before there are two services that watch this folder to it depends on the file type as to which service gets restarted.
  • "LANDesk Inventory Server"
  • "Managed Planet Core Scan Processor"
• Check the event logs for errors
• Activate the core server using the "Core Server Activation" utility.

Slow Processing: The number of files is decreasing but at a slow rate.

• Just like the complete stoppage above look at the "File Types" section at the top of this article to see which service is at fault.
  • Managed Planet Core Scan Processor
    • Check for Web Rules that are running as Active. Active rules run for each inventory scan received. Some rules scrape the web and can be VERY costly in regards to CPU and memory. Some web rules are fine and are enabled by default (like: Lenovo Warranty Info, IBM Warranty Info, HP\Compaq Warranty Info, and Gateway Warranty Info) however others like Apple rules etc should not be run actively. Right click these rules and "Set Inactive" and then restart the Managed Planet Core Scan Processor service.
    • Make sure the Advanced Inventory settings for "Do Delta" are not turned off. Full scans will make the Core Scan Processor run all of it's rules and slow the process down.
  • Inventory Server
    • The primary job of the Inventory Server is to process the scan files and insert them into the database. Therefore the service is generating SQL (primarily insert statements) and running them on the database server.
      • Test the connection between the core and the database server. There are in-depth documents on doing this but most of the time a simple ping test will suffice.
      • Analyze database performance. This may need to be done by a DBA and/or perhaps using a SQL Trace to analyze what tables are taking a long time to process. Generally as long as proper database maintenance is being performed this usually isn't a problem. Otherwise the database server may need to be upgraded.
      • Large scans files. The default maximum scan file size is 10mb. The default size can be changed to allow for larger scans to process. The bigger the scan the longer it will take the Inventory Server to insert them into the database.

OS Application Event Log: The Inventory Server specifically will log errors and warnings regarding scans and other problems in this log. It is important to understand the events and what they mean.

• 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.

Client Side Problems: Below are some ideas on different types of scans as well as the general process the Inventory Scanner goes through. Most of the time port blockage and name resolution are common issues but the following link can help as well. The link contains switches that can be passed to the Inventory Scanner and used in troubleshooting.

Inventory Scanner Switches

Type of scans:

• Full = Self-explanatory. A full hardware and software scan of the device.
• Delta = Changes. This scan will only contain the changes since the last full scan was performed. This is a default setting on the core server.
• Mini = A simple scan that contains basic information in order to communicate an IP address change on the device. These scans help keep the core server up to date on where the device is located on the network.

General Process: The first thing the Inventory Scanner on a device does is attempts to contact the Inventory Server on port 5007. (this will also involve name resolution as well). Assuming that connection is made the device will check/update it's copy of the ldappl3 file. The ldappl3 is a central configuration file maintained by the core that defines what the Inventory Scanner should scan for. After the check for ldappl3 is done the scanner will scan the device and communicate the scan up to the core server.

Generating and output scan and carrying it to the Core Server: Below are methods of generating and output scan on a device. To test communication and other issues with inventory it's helpful to manually move these scans to the core server and drop them into the LDScan folder. This can be done repeated times for troubleshooting as well.

• Macintosh
  • Output scan for Macintosh Machines
• Windows
  • How to generate an output scan

Description:

  We need to generate scan files manually sometimes, so we can identify if the scan files is consistent with the inventory information on the core server.

Resolution:

On the client machine, run below steps to generate inventory scan files manually:

1. Click Start-All Programs-LANDesk Management-Inventory Scan
2. Right click on Inventory scan, click on Properties
   
   
3. Select all the content in the Target, click copy
   
   
4. Open CMC window, paste the content into CMD window
5. Add parameter at the tail of command line: /O=c: \test.scn
   
   Note: /f is Force a full scan, /SYNC is to Synchronize data to the core, /O= is to provide an output log file of what the agent collects,then the path and file name of the text log file.
6. Open window browser, open c drive,check if c:\test.scn scan file is generated on c drive
   
   

ldiscn32.exe crashes every time, locally on one of my Win7x64 client machines.  no ldiscn32.log file is created.  even the /o switch won't produce a log file.

event viewer shows minimal info.  Faulting application/module name: LDISCN32.EXE, version: 9.60.2.111, time stamp xxx.

Event ID =1000, Task Category = (100).  Exception code: 0x40000015

running locally or remotely (via psexec) both return error code 3.  I can run miniscan.exe successfully via psexec which will update the ip in ldconsole, allowing remote control.

I've tried to reinstall the entire client twice but the issue persists.  The client machine seems totally fine outside of ldiscn32...

This is how the wscfg32.log file ends the client install process:

Tue, 09 Jun 2015 14:25:07 Processing [Final Post Copy]

Tue, 09 Jun 2015 14:25:07 INI:  EXEC01=C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE, /NOUI /NOCD /SYNC /F, INSTALLONLY

Tue, 09 Jun 2015 14:25:07 Starting process: C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE /NOUI /NOCD /SYNC /F

Tue, 09 Jun 2015 14:25:13 Processes returned : 3

Tue, 09 Jun 2015 14:25:13 CheckProcessExitCode processed app name: LDISCN32.EXE

Tue, 09 Jun 2015 14:25:13 FAILED:  Running application: C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE /NOUI /NOCD /SYNC /F

Tue, 09 Jun 2015 14:25:13 FAILED:  bCriticalError set to TRUE. Processing C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE

Tue, 09 Jun 2015 14:25:13 Overall Install Status:

Tue, 09 Jun 2015 14:25:13 FAILED:  Finished

Tue, 09 Jun 2015 14:25:13 SUCCEEDED:  Delete (c:\ENUNTCFG.MRL)

Tue, 09 Jun 2015 14:25:14 FAILED:  bCriticalError is true.  Setting exit code to ERROR_INSTALL_FAILURE

Tue, 09 Jun 2015 14:25:36 WorkThreadProc()wscfg32.exe not call reboot here directly since either reboot not needed or ignore reboot set to true

Tue, 09 Jun 2015 14:25:36 UPdateClientDbStatus:  Core Name is:

Tue, 09 Jun 2015 14:25:36 Application exit value is 1603

I haven't tried the UninstallWinClient.exe from ldmain yet... but it seems a client re-installation first uninstalls all modules before re-installing... not sure if there's a difference there.

Suggestions?  We're running LDMS 9.6 sp1.

Inventory for LANDESK Management Suite

• If you want to review additional content regarding this component, please use Documents or Discussions buttons on the overview page.

Initial Installation and Configuration

• Video:Management Suite 9 Fundamentals Inventory Overview
• Video:Configuring the Inventory Server Service
• Video:Configuring Inventory Server
• Sending Custom Data with a Miniscan.
• Inventory Scan & Bandwidth consumption.
• Understanding the Last Scan Information in Inventory.
• Custom Data is not Entered - Using the Unknown Items Inventory Tool.
• What is the Duration attribute that appears in the inventory for a Package and in which measurement unit is expressed?
• Best Know Method to Configure Rollup in LDMS 9.6

Additional Options and Information

• Video:Inventory Scan Options
• Video:Inventory Custom Data
• Video:Inventory Custom Data Forms
• Video:Inventory Scanning Architecture
• Video:Viewing Basing Inventory Using the Web Console
• How to purge the Inventory History
• How to use inventory attributes in custom script
• How to extend the Inventory Scanner capabilities
• Inventory Delta Scan Whitepaper
• How to Add Directory Size Information to LANDesk Inventory
• How to read content of INI files on clients into the inventory scan
• How to scan for the contents of a text file and return it with Inventory.
• How to retreive the Run registry key from the clients and store it in the Inventory
• How to get the overwrite policy of the system event logs in the LANDesk inventory
• How to Report on Computers with Out-of-Date Inventory and Send it in E-mail
• Tip/Trick - Show Extra Patch Related Columns In System Inventory.
• Inventyfier: Random inventory scan generator

Troubleshooting

• Video:Inventory Troubleshooting
• Video:Inventory LDAPPL3
• Video:Inventory Scanner Switches
• Ten simple steps to troubleshoot inventory
• Inventory Scanner Switches
• Machines only send Miniscans
• Inventory Scans Stopped Processing
• Inventory scan on clients is failing to run
• Inventory Server service will not start on the Off-Core Inventory server
• Multiple Versions of Internet Explorer appear in Inventory after update to IE 8
• LD 9.0 - Custom Registry entries are not appearing in the Inventory of the client
• Inventory Scans are not being processed with the error: DELETE FROM PRODUCTCOMPUTER)
• LANDesk Inventory Server Service not Running - Microsoft Visual C++ Runtime Library: Runtime Error!

Notice: Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level.

NOTE: This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Inventory if this page hasn't helped.

Introduction

This document covers how the LDMS Inventory Delta Scan works.

Assumptions

This white paper assumes that the reader is an experienced LDMS Administrator / Technician.

Design

The LANDESK Inventory component was designed to do delta scans for efficiency. A delta scan is a difference between what the client has sent previously and what the scanner finds on its current scan. A delta scan is typically a fraction of the size of a sync (Full) scan. It contains only items that have changed and select data which is sent with every inventory scan such as network information. An easy way to identify if a scan is a delta scan is at the end there is a Deleted section followed by End Deleted. No other scan type contains this.

Initial Scan & Invdelta.dat

When the client initially scans it will send a full scan with software. Upon completing the scan it will write a copy of what the machine knows its inventory contains. It’s important to note this is disconnected from the actual processing of the scan as that can take some time based on how busy inventory is, there is no need to keep a network session open while waiting. This file written is called the invdelta.dat. The reason for doing this is now the client can know what has been sent when it runs scans further so it does not have to send the same information again. The invdelta.dat is formatted exactly as an inventory scan is. In this file the scanner writes a last hardware scan date. This is used as a reference by the client, this is the date it last knows it sent an inventory scan.

The Inventory Server

The Inventory Server listens for clients to send in scans. When a client contacts the Inventory Server, an initial handshake takes place where the Inventory Server can pass settings to the client. These settings are called parameters. Parameters include: Send Software, Do Delta, Force a Sync Scan, Create a new device ID (GUID). For the initial scan the Inventory Server on the Core will process the initial scan and write records for the machine. Because the device is not in the database there will be no parameters passed so the scan will run as called. Once the initial scan completes processing the Inventory writes to the database the last hardware scan date for its reference.

Delta Scan Detection

As the scan is received and begins to process (this is after the handshake), this is on the processing side of the Inventory Server, considered the back end. Upon loading the scan into memory the Inventory Server compares what the scan file contains as its last hardware scan date vs what is in the computer table. This is done to ensure the data the client has sent matches what is in the database. If this were not done the client and the database could have completely different Inventory with no mechanism to correct. If the dates match the database record is updated with the information from the scan.

Out of Sync

Based on the comparison, if those dates do not match the scan file is rejected. The Inventory Server writes a row in the keyvaluestringarray with the device’s GUID with a keyvalue_idn that indicates it is out of sync. The file goes to errorscan and the machines database record is unchanged. The inventory server keeps keyvalue and keyvaluestgringarray data in cache. The next time a device contacts the core to send inventory, during the handshake the Inventory Server tells the client to force a full scan as it has read the cache and knows the device’s last scan was not in sync and it must send a full scan to resync the client and the core. Once done the row from keyvaluestringarray is removed and the device is considered back in sync.

Perpetual Out of Sync

The only way a device is perpetually out of sync is if when it follows the out of sync process, tries to sync up and it’s record cannot be processed every time. An example scenario would be if a device has an invalid product definition. Each time it tries to sync, its scan is rejected and its last hardware scan date will still continue to not match with the date in the database. This is why it is important to research rejected scans and correct them, so devices do not stay perpetually out of sync.

Miniscan

Miniscans are processed regardless of whether a device is out of sync or not.

Conclusion

This concludes the whitepaper on why LANDESK Inventory does delta scans and how they work.

To the maximum extent permitted under applicable law, LANDESK assumes no liability whatsoever, and disclaims any express or implied warranty, relating to the sale and/or use of LANDESK products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right, without limiting the rights under copyright.

LANDESK retains the right to make changes to this document or related product specifications and descriptions, at any time, without notice. LANDESK makes no warranty for the use of this document and assumes no responsibility for any errors that can appear in the document nor does it make a commitment to update the information contained herein. For the most current product information, please visit www.landesk.com.

Copyright © 2014, LANDESK Software, Inc. and its affiliates. All rights reserved. LANDesk and its logos are registered trademarks or trademarks of LANDESK Software, Inc. and its affiliates in the United States and/or other countries. Other brands and names may be claimed as the property of others.

Hi,

I have upgraded agents to 96sp1.

I noticed by looking at the inventory shortcut or local tasks that the inventory command line is truncated.

"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /V  instead of    "C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /NTT=Server:5007 /S=Server  /I="C:\Program Files (x86)\LANDesk\LDClient\Data\ldappl3.ini" /v /f /sync

6: C:\Program Files (x86)\LANDesk\LDClient\ldiscn32.exe /noui

     handle    : 777

     start     : Fri Jun 12 00:57:13 2015

     frequency : 86400

     Filter 1  : [Auto delay] State=(Not ready) Min=(0) Max=(60)

     Filter 2  : Time of Day 0 to 2

  7: C:\Program Files (x86)\LANDesk\LDClient\ldiscn32.exe /mini /noui

     handle    : 778

     start     : Mon Jun 08 09:09:08 2015

     frequency : 600

     Filter 1  : IP Address Change Filter

  8: C:\Program Files (x86)\LANDesk\LDClient\ldiscn32.exe /noui

     handle    : 780

     start     : Mon Jun 08 10:09:27 2015

     frequency : 600

     Filter 1  : OS Event (logon)

     Filter 2  : [Auto delay] State=(Not ready) Min=(60) Max=(60)

I created another agent( also rebuild all) and get the same.

As far as I remember the creation of local task was not part of the ntstacfg.in#

Is that part of the change in 96 SP1?

I have heard / seen a couple of mentions of the attached Network Printers now being available in Inventory, but am not sure where to find them in the inventory window.  Any ideas where I should look?  do i need to enable anything special on my Inventory settings?

Thanks!

I'm making a query to see what computers have a specific software installed to help with deployment verification.  And another to see which ones do not so we can schedule a deployment.  But I'm not quite sure what the difference between some of the categories in  Machine Component tree.  I'm using Landesk Management Console 9.6.0 without the Inventory add-on.

In Computer -> Software, what's the difference between..

Add or Remove programs -> Program

Package Manager -> Package

Product

Where does the inventory scanner find this information?

Right now I've used the GUID field in the Product category.  I've used "like" in the name fields in either Add or Remove programs -> Program or Product.  They seem at first glance to be the same.

Thank you.

Hello,

1) A specific device appears on All Queries, but did not display Type, OS Name, Last Software Scan column. In the Inventory I could see the Last Software Scanned dates and other details in the Inventory for the device. How do I get the details displayed on the All Queries?

2) We have a server on a workgroup installed with Landesk in one country. I cannot ping that server from our network in another Country, but locally using an IE (http://xxx.xxx.xxx.xxx:9595) we could see Landesk logo on IE. On a third country that has a workgroup server, it also had a similar issue.

Thanks for your Help

Thomas

LDMS 9.6 SP2; I've added a file type (.KEY) to the list of file types to be scanned, but when I perform a scan on my machine, the file (which I know is there) isn't showing up under Software - Packages. ldappl3.ini shows a correct modify date and when I look in there, the file type is shown, but the actual file that I'm looking for doesn't show up in inventory. Any thoughts?

In reference to running the inventory scanner automatically after software package installation, does that only apply when LANDesk does the installation or does it run automatically after any software is installed. Like through add/remove program? One last question, is there any way to run a software scan when package is removed?

Purpose

This document outlines how to Import and Export inventory records. This can be useful when migrating a record(s) to different Core's for review, or submitting to Support for troubleshooting.

Export

2 ways to export an Inventory record are provided.

Using Database Doctor

• In the LDMS core click Tools | Data Analytics | Database Doctor
• In the Database Doctor window, click the Export Computers icon

• In the Export Computers window select Only selected computers and click Next

• In the Select Computers window click Add

• In the Select Computerswindow select the machines to be exported, and click Ok.
  • Multiple machines can be selected by holding the CTRL key while selecting machines, or holding Shift while selecting to select a range of machines.

• In the Select Computers window, the list of Computers to be Exported will reflect the selected machines.
• Click Next

• In the Export Computers window -
  • Directory: Select a where to save the *.scn file to.
  • Attribute: Select an inventory attribute to use while naming the output *.scn file
• Check the Perform Export Now box
• Click Finish

• In the Perform Operation window click Start
• Once the Messages window shows Finished Rule click Close.

The *.SCN file will be located in the directory you defined during the export. Locate this file and it can be imported into an LDMS core.

Using LDScan Folder

Enable Inventory Record Storage

Note: If using this method, consider Disabling Inventory Record Storage once finished. If left on the Storage directory may become very large after time.

• In the LDMS Core click Configure | Services
• In the Configure LANDESK Software Services window click the Inventory tab
• In the Inventory section click Advanced Settings

• In the Advanced Settings window select Store Scans and set the Value = 1, then click Set
• Verify the List shows Value = 1
• Click Ok

Note : To disable Store Scans, set Value=0

• In the Configure LANDESK Software Services window click Apply
• A prompt will appear, select Yes

The LANDESK Inventory Server service must be restarted before your changes will take effect.

Do you wish to restart the local service now?

• After the Inventory Service restarts, click OK
• A new directory will be created to store copies of inventory scan records (*.scn) as clients send them to the Core

C:\Program Files\LANDesk\ManagementSuite\ldscan\Storage

Run Full Sync Scan

• Right click the intended client and choose Inventory Scan | Full Sync Scan

• Once the Inventory Scan finishes, check the Storage directory for a new *.scn file

Example: C:\Program Files\LANDesk\ManagementSuite\ldscan\Storage\SCA64A7.SCN

The stored *.SCN file can now be imported into an LDMS core.

Import

Using Database Doctor

• In the LDMS core click Tools | Data Analytics | Database Doctor
• In the Database Doctor window, click the Import Computers icon

• In the Import Data window select All computers in directory and click Next

• In the Import Data window-
  • Directory: Navigate to the location that contains your *.SCN file(s).
  • Check the Import Now box

• In the Perform Operations window click Start
• When the Messages box lists Finished Rule, click Close
  

The imported *.SCN Inventory records will now be visible within the LDMS Core for review.

Using LDScan Folder

• Copy the *.SCN Inventory Recordinto the LDScan folder

Example: C:\Program Files\LANDesk\ManagementSuite\ldscan

• The Inventory Service should automatically import the *.SCN file, so you may not see it paste into the directory

Note: If Inventory Record Storage is still on, the Storage directory will get a copy of the file copied into the LDScan folder.

The imported *.SCN Inventory records will now be visible within the LDMS Core for review.

Is there a way to add a shortcut's "Target" path to an inventory scan so I can see where it points to? I added the .lnk to the ScanExtensions and I am able to see the shortcut under Software - Package, but the Target is not included in the file information.

Versions affected: LDMS 9.5 SP1

A new feature to come with LDMS 9.5 service pack one is to detect and report on the size, location and name of date files with the extensions .ost and .pst. Outllook files.

This can be useful when locating pst or ost files before reimaging a machine, because losing all a users archive mail is something no one wants to do, and situation that no IT administrator wants to be in.

So to help with this possible issue, LANDesk has increased the inventory compatibly of the inventory scanner so it can pick up these files.

Walkthrough

Here are some steps to follow to allow you to activate this feature and allow clients to report the new information to the core:

1) On the core server, modify the c:\Program Files(x86)\LANDesk\ManagementSuite\ldlogon\ldappl3.template with a text editor (for example, notepad)

2) Scroll down to the just below 'scanextensions'

3) Add the following line:

DataFileExtensions=.pst

Example Extract :

[LANDesk Inventory]
; Duplicate can be ON or OFF.  If ON any applications that are found more
; than once by the scanners will be entered into the database.  If set to
; OFF, the scanners will only find the application once.
Duplicate=ON

; ScanExtensions lists the extensions that will be searched for.
; Regardless of what is entered in the Applications section, if the extension
; of the file is not listed here, the application will not be found.
; This list is currently limited to 40 extensions.  If there are more than 40
; extensions, only the first 40 will be used.
ScanExtensions=.exe
;ScanExtensions=.exe .com .sys .nlm .lan .dll .hlp .lvl .crh .lib .run .jar .dat

DataFileExtensions=.pst .ost     ;########### Changes made and implemented here

; MultimediaExtensions lists the extensions that will be scanned for inclusion
; in a computer software report.  This information can be found under the Multimedia
; database attribute and will include the total number of multimedia file, the

4) Save the LDAPPL3.TEMPLATE file and close the text editor.

5) Open the LANDesk Management Suite console.

6) Go to Tools | Reporting/Monitoring | Manage Software List

7) Click on 'Make Available to Clients'

8) Now clients will start sending this new information along with their next full inventory scan.

To test

9) Run the full inventory manually , by adding the switch /SYNC to the inventory short cut in the start menu and the item will appear in the inventory of the device.

Under the following heading in the inventory of the computer:

Software -Data Files

Versions affected: LDMS 9.6

in 9.6 you modify the scanner behavior via the console under manage software list. Under settings you can add the extensions to the DataFileExtensions and this will give you the path, filename, and size of the files that have the extension. You can add the extension in the MultimediaExtensions and it will give you a count of how many files have the extensions in this list. You can add the extension to the ScanExtensions list and then you can add the specific file to the to be scanned list to scan for just one file.

Walkthrough

Here are some steps to follow to allow you to activate this feature and allow clients to report the new information to the core:

1) On the core server, open Toolbox->Reporting/Monitoring->Manage software list->settings

2) Double click DataFileExtensions', add .jpg or .bat, click ok button

3) Click "Make available to clients" button on top menu.

4) Now clients will start sending this new information along with their next full inventory scan.

5)  make sure the following line is added into ldappl3.ini on the client machine:

DataFileExtensions=.jpg

6) Example Extract :

[LANDesk Inventory]

Version=3.0

Revision=1.02

ScanExtensions=.exe

DataFileExtensions=.bat .jpg .PST

Ignored MACs=

MacMultimediaExtensions=.aac .aiff .gif .jpg .m4p .mov .mp3

MacScanExtensions=.dmg .pkg

MacSearchFolders=

MIFPath=C:\DMI\DOS\MIF

MultimediaExtensions=.AIFF .BMP .GIF .JPEG .JPG .M4P .MOV .MP3 .mpeg .MPG .WMAS

To Test

7) Run the full inventory manually , by adding the switch /SYNC to the inventory short cut in the start menu and the item will appear in the inventory of the device.

Under the following heading in the inventory of the computer:

Software -Data Files

Environment

LANDESK Management Suite 9.0

LANDESK Management Suite 9.5

LANDESK Management Suite 9.6

Issue

• After having changed IP address on a managed device, the inventory data in Management Console keeps showing the old IP address
• The Management Console reports the IP address of a network connection that is not the one the managed device is using to communicate to the Core Server
• The IP reported in the in the Management Console is not correct so it's not possible to remote control the managed device
• The inventory of the virtual guest computers report the wrong IP address, using the localhost address rather than the actual network IP address
• It's not possible to schedule a task targeting these computers as the Management Suite is not pointing to the right destination IP address.

Cause

There are a few reasons why this can happen, the most common are the following.

1. The option Encrypted Data Transport is enabled in the Inventory server settings
2. The option Use Connection Address is set to 0 in the Advance settings of the Inventory server settings
3. The network interface used to communicate to the Core Server doesn't precede the other interfaces in the binding order

Resolution

1. In the LANDESK Management Console, go to Configure > Services > Inventory and deselect the option Encrypted Data Transport
2. In the LANDESK Management Console, go to Configure > Services > Inventory > Advanced settings and set to 1 the option Use Connection Address
3. On the device affected by the issue, open the Network and Sharing Center, then click on Change adapter settings

          Press the ALT key, click Advanced, and then Advanced Settings.
          If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

          Click the Adapters and Bindings tab.

          Under Connections, click the connection the device is using to communicate to the Core Server and move it on the top of the list.

          Under Bindings for <connection name>, select the protocol that you want to move up or down in the list.
          Click the up or down arrow button, and then click ok.

Other resources

[Microsoft Technet] DNS: Valid network interfaces should precede invalid interfaces in the binding order

To whom it may concerns,

     There is a fixed hard drive serial number incorrect situation. We found several customer machines which installed LDMS 9.5 SP3 got this problem.  Please see the image file serialnumber2.png, This pic was captured this machine inventory tree, and the hard drive serial number is incorrect. But if see the image file named serialnumber1.png. This pic was captured from the machine powershell command line. and it did returned the correct hard drive serial number. I have checked the workaround solution from https://community.landesk.com/support/docs/32711. But I hope this problem can be fixed future.

Hey there,

we have some hundreds of HP Thin Clients in use. I just noticed, that they report the operation system.

OS - NT Info - Current Build =2600

OS - NT Info - Current Type =Multiprocessor Free

OS - NT Info - Current Version =5.1

OS - NT Info - Registered Organization =XX

OS - NT Info - Registered Owner =XX

OS - NT Info - System Root =C:\WINDOWS

OS - NT Info - Server =No

OS - NT Info - Language =ENU

OS - NT Info - MUI Language =German

OS - Name =Microsoft Windows XP Embedded

OS - Version =5.1

It's based on Windows XP Embedded, but should show up as Windows Embedded Standard 09. Is there a way to get this info out of the client? We have DTS licenced.

So, I did some research first and found a few threads about this issue and I've gone through some steps recommended in them, but still can't find an answer.

We are running 9.6 SP1 in our environment.

There are several devices that are not updating the Last Hardware Scan, Last Software Scan and Last Policy Sync Dates.

Other dates, such as Definition Scan, Security Check, Vulnerability Scan are current, and therefore, Last Updated by Inventory Server is as well, as expected.

If an Inventory Scan is launched manually from the device (All Programs - LANDesk Management - Inventory Scan), it works properly and the device record is updated in the console.

However, if a scan is executed on the device from the console (Right Click - Inventory Scan - Full Sync Scan), it finishes in ~30 seconds and the non-current dates mentioned above still do not update.

I've also tried to deploy the "inventoryscanner" script in Manage Scripts, however, that fails with the error "The system cannot find the file specified".

The "Restore Client Records" script completes Successfully, but the dates remain unchanged.

I've checked the ErrorScan folder in LDSCAN (along with the other Error folders) and the scan is not getting dumped there.

There is also no Inventory Server errors in Event Viewer.

The agent has been removed completely (using UninstallWinClient.EXE) and reinstalled via self contained EXE.

After the uninstall/reinstall, it is up to date in the console, but eventually the problem scans fall behind.

Anything else I can try?

Any input/suggestions would be appreciated.

Thank You!

Problem :

After changing the Core IP Address, this value is wrong on its inventory

Cause :

After changing the IP address, a value in the registry isn't updated so the "Network.TCPIP.Bound Adapter" stays with the old value

Resolution :

1 - You must manually change this registry key to the new IP address :

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}\Parameters\Tcpip

-> IPAddress

2 - And run a full scan

=>The new IP address will be registered in the database