Bug(?): File Scanning differences between %ProgramFiles(x86)% and %ProgramFiles%

[mdouglas]

I believe I found a small bug in the file scanning function. After some testing it appears that when using %ProgramFiles(x86)% in the path it will detect the "File version" attribute and when you use %ProgramFiles% it will detect the "Product version" attribute of the file.

This can be duplicated if you take a random executable file that has different "File version" and "Product Version" attributes and place it in C:\Program Files\Test\ and another copy of the same file it C:\Program Files (x86)\Test\

[Hemoco]

This problem was discussed via email. The information provided by the customer confirmed that WMI itself returns incorrect information. There is nothing we can do about this unfortunately.

The problem appears to be limited to certain executables and certain operating systems. 32/64-bit architecture does not appear to be a factor. We were able to get correct file version results for the LansweeperService.exe on a 32-bit Vista machine for instance, but the same executable on a 32-bit XP machine returned blank file info.

[Hemoco]

We cannot reproduce this behavior. The version number detected should always be the File Version. Could you contact us at support@lansweeper.com and provide us with the following:
- For easy reference, a link to this forum thread.
- Screenshot of your web console landing page. You can access your landing page by clicking on the Lansweeper logo in the top left corner of the web console. Please show us the whole page.
- Output of the report below, preferably in Excel format. Replace "YourComputer" with the NetBIOS name of the machine you ran the File Scanning test on.

Select tblComputers.Computername, tblComputers.Domain, tblComputers.Computer,
tblComputers.Firstseen, tblComputers.Lastseen, tblComputers.Lasttried,
tblComputers.Lasttriggered, tblComputers.LastScheduled,
tblComputers.LastActiveScan, tblComputers.LastLsPush, tblComputers.Scanserver,
Web40OSName.OSname, Web40OSName.SP, Web40OSName.OScode, tblerrors.CFGname,
tblerrors.ErrorText, tblerrors.Lastchanged, tblFileVersions.Found,
tblFileVersions.FilePathfull, tblFileVersions.FileVersion,
tblFileVersions.CompanyName, tblFileVersions.Filesize,
tblFileVersions.CreationDate, tblFileVersions.LastAccessed,
tblFileVersions.LastModified, tblFileVersions.Lastchanged As Lastchanged1,
TsysLastscan.CFGcode, TsysWaittime.CFGname As CFGname1, TsysLastscan.Lasttime,
TsysLastscan.Scantime, TsysWaittime.Waitdays, TsysWaittime.Trackchanges,
TsysFiles.VersionID, TsysFiles.Searchfile, TsysFiles.Enabled
From tblComputers Left Join
Web40OSName On Web40OSName.Computername = tblComputers.Computername Left Join
tblerrors On tblComputers.Computername = tblerrors.Computername Left Join
tblFileVersions On tblComputers.Computername = tblFileVersions.Computername
Inner Join
TsysLastscan On tblComputers.Computername = TsysLastscan.Computername
Inner Join
TsysWaittime On TsysWaittime.CFGCode = TsysLastscan.CFGcode,
TsysFiles
Where tblComputers.Computer = 'YourComputer' And TsysWaittime.CFGname = 'FILES'
Order By tblComputers.ComputerUnique

To use the specified report, do the following:
• Open the Lansweeper configuration console and select Reports & Alerts\Report Builder. Hit the “New” button.
• Copy the SQL code provided and paste it at the bottom of the newly created report, replacing the default SQL code.
• Click somewhere near tblComputers so the new code applies.
• Give the report a “View name” and a “Report name” and hit the “Save” button.
• Double-click on the report in the report list to see its results and export options.