Problem

From time to time, you may need to change the inventory scan local scheduler settings using manage script.

Resolution

Sample Script:

[MACHINES_WIN]

REMEXEC01=<qt/>%LDMS_CLIENT_DIR%\LocalSch.exe<qt/> /del /taskid=555

REMEXEC02=<qt/>%LDMS_CLIENT_DIR%\LocalSch.exe<qt/> /exe=%quote%%LDMS_CLIENT_DIR%\ldiscn32.exe %quote%  /cmd=<qt/>/NTT=CoreServerName:5007 /S=CoreServerName /I=HTTP://CoreServerName/ldlogon/ldappl3.ldz /NOUI<qt/> /taskid=555  /freq=86400  /tod=%quote%14|16%quote% /autodelay=2|60

Note:

1. CoreServerName needs to be replaced by the real core server short name.

2. /NOUI, this is inventory scanner switch, please refer to bleow related document for more switches.

3. /taskid=777, inventory scan local scheduler task ID is always 777 by default. It is recommended to NOT change the ID.  The default vulscan switch is 555.

4. /freq=86400, local scheduler task frequency in seconds, 86400 means 1 day. The value can be changed according to the needs.

5. /tod=%quote%14|16%quote%, time period sets to perform the task, 14|16 means from 2pm to 4pm. The value can be changed according to the needs.

6. /autodelay=2|60, time delay sets to perform the task, 2|60 means 2 hours. The value can be changed according to the needs.

Related document:

Inventory Scanner Switches

Issue

Need to confirm that all registry keys related to a program are removed so you have correct inventory scans.

Solution

Check these locations in the registry editor and delete entries as needed.

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

HKLM\SOFTWARE\Classes\Installer\Products

HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall

HKEY_USERS\(User SID)\Software\Microsoft\Windows\CurrentVersion\Uninstall

There is some more information about the add/remove programs utility here: How Add/Remove Programs Works - Spiceworks

How to:

This guide will show you how to create a full sync inventory scan as a scheduled task.

Note: If you would like to run an immediate sync scan on selected devices it is available on the right click menu.

Step by Step:

1. Log onto the LDMS Console.

2. Select Distribution - Manage Scripts from the menu.

3. Select All Scripts - Inventoryscanner and drag it to My Scripts (we do this so we don't alter the original script)

4. Go to My Scripts. You will see a file name Inventoryscanner(1). Rename the file to whatever you like. (For this example I will use inventoryscannerTEST)

5. Right click inventoryscannerTest and select Advanced Edit.

6. This opens the Edit Custom Script window. Select Use Editor... in the bottom left of the window.

7. Add the switch "/f /sync" to the file at the end of the [MACHINES_WIN] section like so:

8. Save the file and exit notepad.exe. Select Yes when prompted to "Reload changes from external editor?". Select OK at the bottom of the Edit Custom Script window.

9. You can now right click inventoryscannerTEST and select Schedule.

10. Schedule the task as needed.

Additional information:

How to generate an inventory output file from client machine for LANDESK support to do further trouble shooting?

In the root of the inventory of a machine we have Last Scan information for different sections. Here are the different section you can find in inventory:

Last Antivirus Updates Scan Date

Last Blocked Application Scan Date

Last Compliance Scan Date

Last Custom Definition Scan Date

Last Driver Updates Scan Date

Last Hardware Scan Date

Last Security Check Date

Last Software Scan Date

Last Software Updates Scan Date

Last Spyware Scan Date

Last Update Scan Date

Last Updated by Inventory Server

last Vulnerabiltiy Scan Date

Inventory Scan Related Items

Note:A software scan only happens once a day by default. A hardware scan, software scan or a mini scan will change the "Last Updated by Inventory Server" field; even if the scan is discarded into the errorscan folder. A software scan can be forced when using the /F /SYNC switches. By default right clicking on a device in the console and choosing inventory scan does not force a software scan.

• Last Hardware Scan Date: An inventory scan for hardware has run on the client machine.
• Last Software Scan Date: An inventory scan that includes software information has run on the client machine. By default this runs only once a day.
• Last Updated by Inventory Server: This field updates when a hardware scan, software scan or miniscan is recieved by the inventory server service. This field will update regardless; even if the scan is discarded into the errorscan folder.

Security Scan Related Items

Note: Using a Scan and repair setting that is scanning for a group will not update any of these dates. Even if items in the group are types that would result in the date being updated.

• Last Antivirus Updates Scan Date: In the "Scan and Repair Settings" Antivirus Updates is checked off and run on the client machine.

• Last Blocked Application Scan Date: In the "Scan and Repair Settings" Blocked Application is checked off and run on the client machine.

• Last Driver Updates Scan Date: In the "Scan and Repair Settings" Driver Updates is checked off and run on the client machine.

• Last Compliance Scan Date: A compliance setting is applied to the client machine and has run.

• Last Custom Definition Scan Date: In the "Scan and Repair Settings" Custom Definitions is checked off and run on the client machine.

• Last Security Check Date: In the "Scan and Repair Settings" Security Threats is checked off and run on the client machine.

• Last Software Updates Scan Date: In the "Scan and Repair Settings" Software Updates is checked off and run on the client machine.

• Last Spyware Scan Date: In the "Scan and Repair Settings" Spyware is checked off and run on the client machine.

• Last Update Scan Date: In the "Scan and Repair Settings" LANDesk Updates is checked off and run on the client machine.

• Last Vulnerabiltiy Scan Date: In the "Scan and Repair Settings" Vulnerabilities is checked off and run on the client machine

Description: Adding custom data forms that are scanning in or custom data being pulled from clients registry through the LDAppl3 are blocked from being added to the database.

Cause: This is caused by a feature that is added to version 9.0 designed to protect the inventory tree in the database. You can allow custom data to be entered into the database.

Resolution: The attached Document shows when and how to use the Unknown Inventory section of the Inventory service for LDMS 9. Here are some quick steps to allow the data.

On the Core Server

1) Open the 32 bit console

2) Go to Configure | Services

3) Click on the Inventory tab

4) Click on the button labeled Unknown Items

5) Select an item on the list and click Allow

NOTE: Please do not disable blocking unknown inventory items. This feature is very important to protecting the inventory tree from corruption. Allowing the unknown item allows it for all computers. This is not something that is has to be done when each computer scans in.

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

• 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

• 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

• Ten simple steps to troubleshoot inventory
• Inventory Scanner Switches
• Inventory Scans Stopped Processing
• Inventory scan on clients is failing to run
• Multiple Versions of Internet Explorer appear in Inventory after update to IE 8
• 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.

We have tried to filter out computers via OU groups but when I add an OU group to exclude the query will not filter it off?

How can I query OU groups and filter them out of a search?

Thanks guys!

Hi,

I had a look around in Landesk to see if it's possible to retrieve a list of System and User DSNs from the registry. I have looked at custom data -- registry items but what we would be looking for is subkeys within HKLM\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources, these subkeys are unkown since users can call them whatever they want however the custom data requires a known key to retrieve custom data.

Has anyone performed this within Landesk? if so how?

Thanks

This week I replaced a computer lab, after installing the agent some have CBX3__ as the model and no serial number reported.   I ran an inventory scan after but it still looks the same.  attached a screen shot of the problem computers.

Any suggestions on what to try next?

Switches to launch and send a miniscan including additional data

Miniscans in LDMS 9.6 and later are now run and sent via ldiscn32.exe. This allows it to follow the same codepath as delta scans returning the expected results as well as allowing the "Use Connection Address" Inventory functionality.

The following the commandline to run a miniscan using the inventory scanner.

• "C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE"  /mini

Miniscan still retains the ability to include custom data within the scan. Please use the following format:

• "C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE"  /mini /send"=Custom Data - Logged On = Yes"

Where "/send=" is the switch to let the scanner know to include the data that follows in the minscan file. It is important to include the quotes "/send" for the command to work.

The rest of the command line follows the rules for custom data. Remember, this is a snippet of information only, up to 255 characters.

This is useful to get information such as if someone is logged onto a workstation, or any other information that might be needed. This can be combined with a localscheduler task to send the information.

Note this switch is still valid for miniscan.exe

Is it possible to configure the scanner to scan c:\users\ and all folders in that directory for a certain subset of folders and files? specifically I want to know if there is a file with a certain extension in the roaming folder of each user listed. Thanks.

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.

Hi,

I am running a parallel upgrade 95 sp1 to 96 sp1.

I am pushing the new 96 agent using a scheduled task on the 95 server.

I noticed that machines with the new agent are reporting there inventory to both servers.

Inventory has been stripped off some switches that were pointing to the Core server.So I understood that the client was picking the Core server name from the registry. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\LDWM\coreserver

Since the registry of the machine I am looking at has the correct name for the core server does it mean the client is getting the old server name from the certificates??

Thank you

I need some advice on how to add a couple of custom data fields.  I need to add custom fields from a previous database, and I need to add my own custom "Function" field.  I only have the Management Suite 9.6 sp 0.  No other addons like the Inventory or Analytics.

Custom Fields from Previous Database

I've been given from a previous inventory system a list of computer names, serial numbers, and custom fields.  I can match it all up using serial number as a key, but  I need to add the custom data fields.  These are department and cost center.  The list is for about 6,000 computers, most of which were manually collected.  Because of the effort involved in collecting the data, I need to get these into the database, even if they aren't used much.

Custom "Function" field

I also found with my last large deployment that I need to classify computers based on it's function.  A custom "Function" field.  It's a hospital, so some computers are in the OR and others run a TV screen of advertisements.  They have different deployment requirements then a secretary or patient room computer.  Actually the rule list became quite complicated.  That's fine, but all I had to categorize them is OU, subnet, name, model, and installed software.  With no ability to use another query in a query, or a temporary table, my queries became very complicated and slow.  A "function" field would help a lot if it gets close to 100% coverage.

I've got the custom field in the registry, and have inventory collecting it.  It works nice, but I won't get full coverage with it.  For example, I might not be allowed to write to a registry on some computers (ie Vendor owned that runs lab or surgery equipment).  I've tried deploying a .bat file, but didn't get 100% success, and I'm starting to think 100% of any deployment is unrealistic.

I've played around with thecustom forms.  That looks good.  It could help with future collection of department, cost center, computer function fields.  It could get some more coverage of the custom data if I have compliance from field support.

I've seen how I can manually add a field in the Inventory window for a specific computer. But wow that'd be slow.  We have 12,000 objects in our inventory.  Even if half are old, It'd take forever to do it that way.  Having to even do 100 would be a cause for beer at lunch, I mean at 5.

I've access to the Database and the thought of sql insert/update queries has crossed my mind.  But the database is big and would take some time to figure out.  I have a lot of other work to do so holding that off as a last resort.

Any advice would be appreciated.  I'd rather do this within the Console because I'm trying to avoid making this too difficult for someone else to step in and do.  But if this has to be done using some programming or outside manipulation of the database then its something I definitely consider since both are very important.  I'm functional in c#, powershell, and sql.  I have a database admin who should be a sql master and a couple guys who know a bit of VB who could potentially help.  Also I might be looking at it wrong, so if there is another process that can accomplish the division of computers besides the custom field that could work too.

Thanks

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

Description

For some LANDESK administrators the need arises to locate the table name as well as other database information about items in their Inventory. This could be for custom querying or troubleshooting.

Inventory is comprised of Objects (containers in the Inventory tree) & Attributes (labels for the actual data).

Object (AKA MetaObject) is the container on the left hand side of the Inventory tree. There can be multiple sub-objects within the Inventory tree. Attribute (AKA MetaAttribute) is the name which labels the value on the right side of the Inventory tree.

In this screenshot both Browser and Internet Explorer are Objects, Version is an Attribute.

Resolution

There are two ways to search, either by Object or by Attribute depending upon preference and how unique the name is for it.

• To search by Attribute name use the following. Replace the highlighted text with what you are searching for:

--Grabs Tablename, Objectname, Attributename, Parent Object number by Metaattribute def

select moar.TABLENAME, mo.OBJECTNAME, ma.ATTRNAME, mor.PARENTREL_IDN as'MetaObjRel ID 4 MObjParent'

from METAOBJATTRRELATIONS as moar

innerjoin METAOBJRELATIONS as mor

on mor.METAOBJRELATIONS_IDN = moar.METAOBJRELATIONS_IDN

innerjoin METAOBJECTS as mo

on mo.METAOBJECTS_IDN = mor.METAOBJECTS_IDN

innerjoin METAATTRIBUTES as ma

on ma.METAATTRIBUTES_IDN = moar.METAATTRIBUTES_IDN

where ma.def like'%Version%'

---If you need the parent object you have to select from metaobjrelations to get the object ID based on the parent ID. Then select the object from metaobjects.

• To search by Object name use the following. Replace the highlighted text with what you are searching for:

--Grabs Tablename, Objectname, Attributename by Metaobject def

select moar.TABLENAME, mo.OBJECTNAME, ma.ATTRNAME

from METAOBJATTRRELATIONS as moar

innerjoin METAOBJRELATIONS as mor

on mor.METAOBJRELATIONS_IDN = moar.METAOBJRELATIONS_IDN

innerjoin METAOBJECTS as mo

on mo.METAOBJECTS_IDN = mor.METAOBJECTS_IDN

innerjoin METAATTRIBUTES as ma

on ma.METAATTRIBUTES_IDN = moar.METAATTRIBUTES_IDN

where mo.DEF like'%Internet Explorer%'

Background

If the .scn file is more than 10M, inventory server will not deal with this scn file by default, because the Max Scan File Size is set as 10M by default, the scan file which is more than 10 M will be moved into ErrorBigScan folder, please refer to below screeshot:

In order to deal with the inventory scan file which is more than 10 M , we need to adjust the settings for the Max Scan File Size, adjust this parameter as more than 10 M.

Configuration steps

1. Navigate to the service window in the console: Configure > services
2. Click on the inventory tab
3. Click on advanced settings. In this window find the attribute 'Max Scan File Size':
   Change this number from 10000000 to 20000000
4. This will allow larger scan files to be accepted by the database. A restart of the LANDesk Inventory server service will be required as well for the changes to take effect

Versions affected: LDMS 9.5 SP1

Note: For LDMS 9.6 - Use this article How to scan .jpg or .bat extension files (or any other extension) on LDMS 9.6

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

Hello

I am confised , please help me, I installed Visio and Project 2010 but LANDesk Inventory software show up two instances in Software-->Add or remove programs-->program and one instance in Software-->Licensed Sofware. And when a create a report i got a report with instances o licenses duplicates. Could you explain me why?. Or which  is the best way to create a software report or query  ?

Thank you in advance

Hello everyone,

Wondering if anyone else has had this problem before?  I'd like to collect some custom registry data however the option to make the policies available to clients is disabled.  I can't find a way to enable this.  Thanks in advance for any help you can offer.

Note: We are using LDMS 9.6 SP1.

Problem:

Agent doesn't appear to be working right. Able to run inventory scans on the client, but they don't sync up to the core. Inventory scans from the core fail. On the core, the directory \LANDesk\ManagementSuite\ldmain\ldscan\ErrorBigScan contains files over 10 MB in size. In one instance the inventory scan wasn't pulling inventory information about "Add or Remove Programs".

Resolution:

Increase the cap on the file size LDMS allows for scans.

1. From the Core select "Configure - Services" from the menu bar.

2. Select the "Inventory" tab. Select "Advanced Settings".

3. Change the value from Max Scan File Size from 10000000 (10 MB) to 30000000 (30 MB).

4. Click the "Set" button and make sure the change has been made. Click OK.

5. Click "Apply" and then "OK" to save the changes.