Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong serial number #253

Open
Joao-Rocha-ISTEC opened this issue Jun 17, 2022 · 7 comments
Open

Wrong serial number #253

Joao-Rocha-ISTEC opened this issue Jun 17, 2022 · 7 comments

Comments

@Joao-Rocha-ISTEC
Copy link

It's hard to solve a problem when important details are missing, that why we added this template, to help you and us.

General information

Operating system : Windows 10 21H2

OCS Inventory information

Windows agent version : 2.7
Version OCSReports: 2.7

Problem's description

Agent is reporting to the server the wrong serialnumber (103C_5336AN). When I click on Inventory Informations, the serial number is the correct one.

Inventory log file ( optional )

OCSInventory.log

@arslanyaqoob7
Copy link

Facing the same Issue, in some scenarios, the serial number is the model number of that device.

@Kiks67
Copy link

Kiks67 commented Nov 25, 2023

OCS Inventory information

Windows agent version : 2.9.0.0, 2.10.1.0
Version OCSReports: 2.12.1

Hello,

We have the same issue here.
Other information like "Operating system" are filled in "Windows 8" instead of "Windows 10" or "Windows 11", etc. (same problem in #278)

image

@arslanyaqoob7
Copy link

@Kiks67 can you please verify the OCS windows agent version? Previously the windows' agent was reading Bios info from DMI first which has been deprecated in the Agent Windows 2.8.0.1-RC.

@Kiks67
Copy link

Kiks67 commented Nov 27, 2023

In my case, as shared in the screenshot, this issue is present on 2.9.0.0 and 2.10.1.0 Windows OCS agents

@StrokoFF
Copy link

Agent 2.10.1.0, the problem is relevant.

@cirvent
Copy link

cirvent commented Jul 25, 2024

Hello,
I have exactly the same problem with server OS, what is strange is that it is not systematic, on 629 servers in Windows server 2022, I only have the problem on three machines.
image2
I tested the following agents :
2.8.0.0 x64
2.9.0.0 x64
2.9.2.0 x64
2.10.1.0 x64

@cirvent
Copy link

cirvent commented Jul 25, 2024

Hello
I have just identified the problem !
It is a wmi problem which is corrupt, to fix the problem:
stop service "Windows Management Instrumentation"
move folder %SystemRoot%\System32\Wbem\Repository
run command:
cd C:\WINDOWS\system32\wbem
for /f %s in (‘dir /b *.dll’) do regsvr32 /s %s
reboot the machine.

Regards,
Cirvent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants