Description

By default the LANDesk inventory scanner (ldiscn32.exe) will scan for files with extensions of *.EXE. However, the scanner is capable of scanning for any file type with an extension.

(This information applies to the Windows inventory scanner.) Scan for custom information. Scan for .DLL files. Scan for EXE files. Scan for custom files. Change ldappl file to scan for other files.

Resolution

To search for one specific file that you know the name of, follow these steps.

1. Edit the LDAPPL3.template file on your core server. Open up the file and go to the section that looks like this:
   
   ; extensions, only the first 40 will be used.
   ScanExtensions=.exe
   ;ScanExtensions=.exe .com .sys .nlm .lan .dll .hlp .lvl .crh .lib .run .jar .dat
   
   Change the ScanExtensions= line to include the filetype of the file you want to search for. For example, if you want to search for a .pst file, it should look like this:
   
   ScanExtensions=.exe .pst
   
   
   
   
   
2. Go to the section of the ldappl3.template file that looks like this:
   ;Mode=Unlisted
   ;Mode=All
   Mode=Listed
   
   Ensure that it is set to Mode=Listed. If it is set to Mode=All, it will search for all files of the extension types you specified above. This can kill performance, so if they know the name of the exact file, leave it on Listed.
   
   
   
   
   
   
3. Make sure that the folder that the file is in on the device you want to search is not in the Excluded Folders section. If it is, you will never find it on a computer. If the folder is listed, just put a ; in front of the line.
   
   
   
   
   
4. For version 8.8, Open Software License Monitoring and go into Inventory>Files. Right click on To Be Scanned, and click New File. Enter the file information in the screen. If you do not know the exact size, or do not want to specify a size, enter 1, which is the wildcard for size. If you do not know what the Product Name, Vendor, or Version is, you can enter an X, which is the wildcard for any of these character strings.
   
   
   
   
   
5. For version 9.0, Open Reporting/Monitoring and select 'Manage Software List', > Right click on To Be Scanned, and click New File. Enter the file information in the screen. If you do not know the exact size, or do not want to specify a size, enter 1, which is the wildcard for size. If you do not know what the Product Name, Vendor, or Version is, you can enter an X, which is the wildcard for any of these character strings.
   
   
   
   
   
6. Click Make available to clients icon.
   
   
   
   
7. Run two full inventory scans with /f /sync switch on the clients. This command should be like follow: "C:\ProgramFiles\LANDesk\LDClient\LDISCN32.EXE"/NTT=[CORE_SERVER]:5007 /S=[CORE_SERVER] /I=HTTP://[CORE_SERVER]/ldlogon/ldappl3.ldz /V /f /sync
   
   NOTE: replace [CORE_SERVER] with your core server's name.
8. Once you have scanned machines that have the files, go back in to step 4 or 5, (depending on LDMS version) to where you created the wild card file, but this time find the new files in To Be Dispositioned, and move them to the To Be Scanned folder and run the Make available to clients.

You can now write a query to search for the file, something like this would work:

"Computer"."Software"."Package"."File Name" Like "msdia80.dll"

1. Right-click on inventoryscanner and select 'Schedule'.
2. Drag all the desired devices from the Network View down to the newly-created Scheduled Task.
3. Right-click on the new task and select 'Start Now'.

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?

Hello all,

   I am interested in inventorying only a specific JSON file in a specific directory.  I was looking for ways to do this and I know we can add Files -> To be scanned.  As I understand this, I need to add the JSON extension to the Inventory -> Settings -> Scan Extensions. 

Is there another way to do this?

And/Or, what is the impact of adding the JSON extension to this? (Next Inventory Scan, SQL database size increase, etc.)  I am not expecting very much, but I appreciate all expert advice.

Sincerely,

-Pat

Running Landesk 2016 sp3

In my event viewer I have several 4100 events that are specific to what column to increase but I have this one which has no specific column that is located in the Datamart.xml file. Below is a scaled down version of what it says.

Error committing on table VIDEO:   DATA PROVIDER OR OTHER SERVICE RETURNED AN E FAIL STATUS

Increased Column size might be necessary. Thread ID 3044

Any ideas?

When I display the Computer.OS.Name in query results, it displays the long name of the operating system.  We're all Windows, so unfortunately the left part of the column is wasted, since it only tells me that a particular system's OS is Microsoft Windows.  Is there any way to create a customizable substitution table somewhere, so whenever that field says, for example, "Microsoft Windows Server 2012 Server Standard Edition (full installation), 64-bit" it instead displays something like "Server 2012 Std x64"?

Hello,

We are in the process of deploying Office 2016 to our devices and have seen a few issues with add-ins from time to time.  I am trying to determine the best way to identify add-ins that are installed for the office products, in an effort to minimize potential issues.  I may have missed it out there, or I'm just not searching correctly, but does anyone know or have a way on how to determine this? 

Any help would be appreciated. 

2016.3 SU3 is the version that we are on. 

Thanks!

Scott

The attached document details the new changes to Inventory in Ivanti Management Suite.

The notable additions include:

• Windows 10 optional features gathered
  • Installation date of optional features
  • Install status of optional feature
  • Description of optional features
• Embedded OS names correctly gathered
• Dedicated thread within the inventory service for mini-scans

Problem:

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 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 breakdown 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 Can I 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 lets 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: Custom Data is not Entered - Using the Unknown Items Inventory Tool

Description:

This document describes how to resolve "Database Exception" errors found in a core servers Event Viewer.  Event ID 4100 and sourced from the "Landesk Inventory Server".

Database exception: EXAMPLE.scn, LDInv.dll

-2147467259

Data provider or other service returned an E_FAIL status.

Error committing on table :   DATA PROVIDER OR OTHER SERVICE RETURNED AN E_FAIL STATUS.

     Increased column size might be necessary, Thread ID:

Cause:

Inventory scans sent to the core server contain attributes whose values exceed the amount of characters allowed in database schema of the attributes associated column.

Resolution:

In order to resolve these error we must increase the column size(VARCHAR) for the effected attributes. This must be adjusted in the core servers database schema configuration file (Datamart.xml) otherwise your changes may be overwritten by "CoreDBUtil.exe"

Updating database schema

The database schema is configured in DataMart.xml. After modifying this configuration you can apply the changes to the database using CoreDBUtil.exe . Both "Datamart.xml" and "CoreDBUtil.exe" can be found in the core servers installation directory. (Program Files\LANDesk\ManagementSuite)

Modifying the Database Schema Configuration:

1. Open "Datamart.xml" in notepad or your preferred text editor
2. Modify the "Varchar" value of all the effected columns to "Varchar(MAX)"

   • Effected Tables/Columns

     Tables	Columns	Modifications
     BiosSettings	CurrentSetting
     BiosSettings	PossibleValues
     EnvironSettings	Name
     EnvironSettings	ValueString
     PeripheralAdapters	Type
     Printer	Version
     Services	Path
     Services	Description
     Video	DriverName

3. Save Datamart.xml
4. Apply Configuration changes to the Database
   

Apply Configuration Changes

1. Stop the "LANDesk Inventory Server" service.
2. Navigate to Program Files\LANDesk\ManagementSuite
3. Launch CoreDBUtil.exeas administrator
4. Click "Build Components"
5. Click OK when complete
6. Restart the "LANDesk Inventory Server" service
7. Confirm resolution by reprocessing scans

Manually Updating the Database Table Schema

If a database is hosted in an SQL Cluster or if "CoreDBUtil.exe" fails to commit the changes for any reason you will need to update the effected tables in your LDMS Database manually using SQL Management Studio.

1. Allow saving changes to the DB tables.
   • Navigate to "Tools > Options > Designers" and Uncheck "Prevent saving changes that require table re-creation"
2. To increase this value, run the following in a new SQL query:

alter tableBiosSettingsalter column CurrentSettingnvarchar(max);

alter tableBiosSettingsalter column PossibleValuesnvarchar(max);

alter table environsettingsalter column namenvarchar(max);

alter table environsettingsalter column valuestringnvarchar(max);

alter tableperipheraladaptersalter columntypenvarchar(max);

alter tableprinteralter columnversionnvarchar(max);

alter tableservices alter column path nvarchar(max);

alter tableservices alter column description nvarchar(max);

alter tablevideoalter column drivernamenvarchar(max);

Confirm resolution by reprocessing scans

Confirm Resolution

To validate that the changes were applied as expected you can "re-process" your failed scans

1. Navigate to Program Files\LANDesk\ManagementSuite\ldscan\ErrorScan Your
2. Move all files that have been modified within the last 24 hours to Program Files\LANDesk\ManagementSuite\ldscan\ the

• It is common for scans to become out of sync after recovering from errors. If your scans return to "ErrorScan" you should review the Event Viewer to validate the cause.

• Out of Sync Scans are moved to "ErrorScan" and log as Warnings in the Event Viewer

I have read through the forums for information on this issue, but nothing seems to quite fit.  I have systems that are showing up and disappearing on their own in my 2017.3 console.  When I look, they do show up in errorscan, but the previous admin tells me just to delete them and the systems will catch up later on.  This does not seem to be the case since I can install the agent on a system and it shows up, then I can run a scan and it disappears.  The details of this process are varied, but it happens to many machines several times a day.  From what I have read on error scans, the systems will stay in inventory until their days to keep value has been exceeded.  Mine is set to 30 days, yet I can see systems show up and disappear several times a day, so that does not seem to apply.  Am I wrong in that error scans are produced and not processed when either the server or the database cannot process them in time?  If that is the case, how do I go about determining which one?  Are there other causes I should look at?  Assistance is appreciated.

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

In order to discover VMWare ESXi hosts using Ivanti Endpoint Manager ( EPM ) version 2017.x you will need to

1. 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)

Download

Download dbrepair06022011.zip for LANDESK 9.0 and 9.5 databases. Compatible with 9.0 supported Core OS's: Windows Server 2003 32 bit and Windows Server 2008 R2x64. This dbrepair includes the new snapshot function as described in UsingSnapshotInDbrepairRev1.pdf.

Download DBRepair9.5 For Landesk9.5

Download 96DBRepair.zip for LANDESK 9.6

Download 9.6SP1dbrepair.zip for LANDESK 9.6 SP1, SP2 & SP3

Download DBRepairLDMS2016.0.zip for LANDESK Management & Security 2016.0

Download DBRepairLDMS2016.3.zip for LANDESK Management & Security 2016.3

Download DBRepairEPM2017.1.zip for Ivanti Endpoint Manager 2017.1

Download DBRepairEPM2017.3.zip for Ivanti Endpoint Manager 2017.3

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.

For LDMS 9 it should only need to be run initially after upgrading because 9.0 doesn't allow client scanner corruption to enter the database unless configured otherwise. See DOC-7456 for more information on how this is accomplished and how to allow custom unmodeled data into the database. In some circumstances it may be necessary to allow unknown items, in those cases using snapshot and a scheduled dbrepair is useful. This is also described in the UsingSnapshotInDbrepair pdf.

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.exe is in the ManagementSuite directory.

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

4. Delete database corruption if if is 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.

5. Close DBrepair.exe.

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

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.

Hello

Do you  know if is possible to  collect the profilelist (regedit) from a client  through inventory scan  .

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.

How to determine if you are having a duplicate device ID issue resulting from the imaging process already including a LANDesk agent

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

[COREPATH]\Program Files\LANDesk\ManagementSuite\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 =************.domain

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

Run eventvwr.msc

Expand Windows Logs

Click Application

You can filter or sort by Source (this may take a few minutes)

How to resolve duplicate device IDs overwriting inventory records caused by an image with the LANDesk agent

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

          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 contents

3. C:\ProgramData\LANDesk (delete the entire directory and subdirectories, this is a hidden directory)

4. Run Security Scan - look for this line "Sending current settings information to core. Failed: Core has no inventory data for this computer" (this is important to make the inventory scan work, otherwise it will fail and you will see the entry in Event Viewer)

    Without this step, I was encountering an error stating "LDISCN32: The inventory server [CORE] did not respond"

5. Open command prompt and run C:\"Program Files (x86)"\LANDesk\LDClient\LDISCN32.EXE /V /F /SYNC

You do not have to wait for Security Scan to finish, it will probably fail anyways until it can properly sync up with the right inventory information

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.

How to determine if you are having a duplicate device ID issue resulting from the imaging process already including a LANDesk agent

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

[COREPATH]\Program Files\LANDesk\ManagementSuite\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 =************.domain

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

Run eventvwr.msc

Expand Windows Logs

Click Application

You can filter or sort by Source (this may take a few minutes)

How to resolve duplicate device IDs overwriting inventory records caused by an image with the LANDesk agent

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

          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 contents

3. C:\ProgramData\LANDesk (delete the entire directory and subdirectories, this is a hidden directory)

4. Run Security Scan - look for this line "Sending current settings information to core. Failed: Core has no inventory data for this computer" (this is important to make the inventory scan work, otherwise it will fail and you will see the entry in Event Viewer)

    Without this step, I was encountering an error stating "LDISCN32: The inventory server [CORE] did not respond"

5. Open command prompt and run C:\"Program Files (x86)"\LANDesk\LDClient\LDISCN32.EXE /V /F /SYNC

You do not have to wait for Security Scan to finish, it will probably fail anyways until it can properly sync up with the right inventory information

Description:

This Document contains an inventory process flowchart from Agent to Core to Database.

I recently deleted a user PC (Windows 8.1)from All Devices and reimaged it with Windows 10 Build 1803 through Landesk and it named it same as the old name. I did this twice but the PC name is not getting picked up back to the All Devices for me to push applications. Then I have noticed that there was an entry under Pending Unmanaged Devices so I deleted that. I ran the inventory and vulnera scan from the client machine few times, shutdown and restart, install reinstall the client agent, also did a scan by IP from Management console and it picked up the existing name but no luck to get it to the All Devices. Is there the possibility that the old entry was still there somewhere?

I'll try renaming the PC with different name and see how I go.

Thanks in advance.