Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.12.3 available

The official documentation can be found on https://wiki.ocsinventory-ng.org. Read it before asking your question.

Different accountinfo behavior on Win11 builds

Hello,

I have a question regarding duplicate detection and archived devices in OCS Inventory.

Environment:

  • OCS Agent version: 2.4.0.0

  • OCS Server version: Unknown

Here is the situation:

  1. A computer is archived from "All Computers".

  2. Windows 11 is clean-installed.

  3. The OCS agent is reinstalled on the same machine.

However, the behavior differs depending on the Windows build version.

For PCs with OS version "10.0.26200":

  • A completely new inventory entry is created in "All Computers".

  • Information such as last seen time, computer name, user, and operating system is newly generated.

  • User-defined account information (such as User, Department, Asset Number, TAG) is NOT inherited from the old archived record.

For PCs with OS version "10.0.26100":

  • The normal inventory information (last seen time, computer name, user, OS, etc.) does NOT inherit the previous data.

  • However, user-defined account information IS inherited from the old archived record.

I compared the hardware information, network information, and management data between the two systems, but I could not find any meaningful differences other than the Windows build version.

I found documentation related to:

  • "Managing duplicates computers"

  • "AUTO_DUPLICATE_LVL"

The documentation says that OCS can detect reinstalled or renamed computers automatically, and duplicate detection depends on matching values.

However, I am not sure whether this behavior is actually related to duplicate detection, because only the user-defined account information is inherited while the normal inventory information is not.

My questions are:

  • Could there be any known reason why this different behavior occurs depending on the Windows build version (10.0.26200 vs 10.0.26100)?

  • Is there any internal logic related to duplicate detection, archived devices, or accountinfo inheritance that could explain this behavior?

  • Could this behavior be related to hardware UUID, SID, registry values, or another identifier used internally by OCS Inventory?

Thank you.

ago in OCS Inventory NG agent for Windows by (120 points)

Please log in or register to answer this question.

 
Powered by Question2Answer
...