Summary
This article describes a known issue that results in inventory devices records for computers running Windows operating systems appearing with an Operating System field value that contains the OS name followed by the installation partition path of the operating system.
Symptoms
- Inventory devices appear with an Operating System that contains the OS name plus installed partition path separated by a pipe. For example: Microsoft Windows 10 Enterprise|C:\WINDOWS|\Device\Harddisk0\Partition3
- The following query against inventory database shows PropertyValue field values that contains the operating system name and installation partition path together:
SELECT PropertyValue FROM ImportedWMIEvidence WHERE ClassName = 'Win32_OperatingSystem' AND PropertyName='Name' AND PropertyValue LIKE '%|%'
Cause
This behavior can be caused when the FlexNet inventory agent is installed on the FlexNet Manager Suite inventory server. This can result in a misconfiguration of a registry setting which results in operating system details in inventory data not being processed correctly.
In particular, operating system details in inventory are processed according to some rules contained in the following file on the inventory server: C:\Program Files (x86)\Flexera Software\Flexnet Manager Platform\Reporter\OSNameMap.txt
This file is located based on the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\InstallDir
If the FlexNet inventory agent is installed then this registry entry may be set to point to the installation directory of the agent software rather than the inventory server software.
Resolution
Modify the following registry entry on the inventory server to point to the installation directory of the inventory server software: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\InstallDir
The installation directory of the inventory server software will commonly be a path like the following: *C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform*
Related Articles
Inventory NDI files fail to import and are saved in BadLogs folder on the inventory server if SoftwareFile_MT.SoftwareFile… 12Number of Views How to configure replication to collect a uploaded agent files on the FlexNet Manager Suite inventory server 46Number of Views SoftwareOccurrence_MT database table identity values may run out, preventing inventory NDI file imports from completing su… 8Number of Views The ndi files that fail to import via the inventory import task 15Number of Views Remove stale agent and beacon version packages from the Beacon server 146Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago