We are having some problems with the status of a computer blanking out after it has been set. The status is set using the bar code web form. We have the following settings set in LANDesk below for a device to be removed if the Mac Address matches in LANDesk. When someone connects to the VPN they all have the same MAC Address. Most of the computers with the issue of the status changing appear to be a laptop or thin client. Thin clients might not keep the status because of the write filter being enabled when the status is changed not for sure. I can try unchecking the MAC addresses match checkbox and see if it resolves the issue with statuses disappearing. Please let me know your thoughts about changing this setting. Does anyone know of another setting that causes this issue?
I have verified that this issue is caused by computers having duplicate MAC Addresses because of the Cisco VPN. I created a query based off of one of the computers with the issue to find out if any of our computers had the same MAC Address. Several computers came back with the same MAC address. Since LANDesk clears the computers daily with duplicate MAC addresses. I can see a few computers in the query first thing in the morning. The amount of computers keeps growing in the query as additional users connect to the VPN throughout the day. I was able to validate the computers were deleted out of the database by looking at the "Record Creation Date."
We have had the box in the screenshot above checked that says "Both device names and MAC address match." This seemed to cause issues with more missing data and duplicates. We need to find a setting that will allow us to remove computers with duplicate MAC addresses except the one MAC address our Cisco VPN uses. Below is an article that helped me troubleshoot this issue. Does anyone know of a way to solve this issue?
In the LDAPPL3.template file in your LDLogon map, you can add the following, to exclude your VPN adapter MAC Address as being the primary adapter of the system:
; Ignored MACs is a space delimited list of up to 40 MAC addresses that the scanner should
; not consider as a candidate when choosing an address to be used for identification...
; This is the address assigned to "Network - NIC Address" and is used on the core
; to identify duplicate device ID's
; The addresses in this list must match EXACTLY with addresses found in the "Bound Adapter"
; section of a scan file. For this reason, it is best to copy these addresses from a scan file.
; A typical address to ignore is the one that is consistent between machines for VPN client.
; This example is for a 64 bit Cisco VPN client
After changing the settings in this file, don't forget ot won't get 'active' for clients until you click on the 'Make available to clients' button in Reporting - Manage Software List or during nightly maintenance of your LDMS Core Server.
1 of 1 people found this helpful
Below is more detail on how to edit the LDAPPL3 file. I found this information at the following link.
Editing the LdAppl3.Template file
Information about the scanner's inventory parameters is contained in the LdAppl3.Template file. This template file works with the LdAppl3 file to identify a device's software inventory.
You can edit the template file's [LANDesk Inventory] section to configure the parameters that determine how the scanner identifies software inventory. By default, LdAppl3.Template is located in this directory on the core server:
- \Program Files\LANDesk\ManagementSuite\LDLogon
Use this table to help you edit the [LANDesk Inventory] section in a text editor.
Mode Determines how the scanner scans for software on devices. The default is Listed. Here are the settings:
- Listed: Records the files listed in LdAppl3.
- Unlisted: Records the names and dates of all files that have the extensions listed on the ScanExtensions line but that are not defined in the LdAppl3. This mode helps discover unauthorized software on the network.
- All: Discovers files with extensions listed on the ScanExtensions line.
Duplicate Records multiple instances of files. Set the value to OFF to record only the first instance, or ON to record all detected instances. The default is ON. ScanExtensions Sets the file extensions (.exe, .com, .cfg, etc.) that will be scanned. Use a space to separate the file extensions. By default, only .exe files are scanned. Version Is the version number of the LdAppl3 file. Revision Is the revision number of the LdAppl3 file; helps ensure future compatibility. CfgFiles 1-4 Records the date, time, file size, and contents of the specified files. You can leave out the drive letter (for example, c:) if you want to search all local drives. You can specify more than one file on each of the four lines, but the line length is limited to 80 characters.
Separate path names on the same line by a space.The scanner compares the date and size of the current file with that of the previous scan. If the date and size don't match, the scan records the contents of the file as a new revision.
ExcludeDir 1-3 Excludes specific directories from a scan. You can leave out the drive letter (for example, c:) if you want to exclude all local drives. Enumeration must start at 1 and be continuous. You can use environment variables in this format: "%varname%". You can use a wildcard (*) in a "begins with" form only ( ExcludeDir=%windir%\$NtUninstall*\ ). You must end each line with "\". MifPath Specifies where MIF files are stored on a device's local drive. The default location is c:\DMI\DOS\MIFS. UseDefaultVersion If set to TRUE, the scanner reports a match when a file matches an exact filename and file size entry in LdAppl3 on filename only (the version will be reported as EXISTS). This can cause some false positives for applications that share a common filename with an unknown application. In the as-delivered LdAppl3.Template file, this parameter is set FALSE; that is, only add an entry if the match is exact. If the parameter is missing, it defaults to TRUE. SendExtraFileData If set to TRUE, sends extra file data to the core server. The default is FALSE. This means that by default, only path, name, and version are entered into the core database.
Making inventory scan changes available to clients
When you make changes to the LdAppl3.template file, you need to deploy the changes to managed devices in order to change the way inventory scans run. The changes will be applied if the /i scanner command line parameter is used on your managed devices.
To edit the LdAppl3.Template file
- From your core server, go to the LDLogon directory and open LdAppl3.Template in Notepad or another text editor.
- Scroll down to the parameter you want to update and make your changes.
- Save the file.
To deploy scanning changes to managed devices
- Edit and save the LdAppl3.Template file.
- In the console, click Tools > Reporting/Monitoring > Manage Software List.
- Click the Make Available to Clients toolbar button to make the most recent changes available to devices the next time they run an inventory scan.
After adding the following MAC Address to the LdAppl3.template file on the core server and running a full sync inventory on computers on the VPN. They started disappearing out of my "Duplicate MAC Address" query I created. Hopefully this will solve all of the following problems for us:
- Partial inventory of laptops that have been connected to the VPN.
- The status disappearing for these same laptops.
- Laptops disappearing completely out of LANDesk from one day to the next that have been connected to the VPN.
We still need to do additional testing to verify that this has solved our inventory problems.
MAC Address - 00059A3C7800
We ended up removing this setting as it did not seem to solve the issue.
Are you using Data Analytics for the bar coding? As a test, do a change status on a device, check the data is in the inventory and then force a full sync scan on the same device and see if it disappears. if it does, then you will need to look at setting the Attribute Type for that to a Type 99 which does not get removed on a full sync scan.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based
The One-Stop Shop for LANDesk Enhancements