You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GLPI Agent report incorrect SN for some HP LaserJet Printers. It adds "00" to beginning, rest of SN follows correctly, but this is enough for SN not to be matched, thus creating duplicate printers.
So far seen for HP LaserJet P2015d and HP LaserJet P2055dn.
To reproduce
Run GLPI Agent.
Compare SNs of detected HP LJ printers to their real SNs.
Expected behavior
GLPI should adjust the SN internally in order to report correct SN. The correct SN for HP is exactly 10 letters long.
Operating system
Windows
GLPI Agent version
1.7.3
GLPI version
10.0.14
GLPIInventory plugin or other plugin version
Not applicable
Additional context
No response
The text was updated successfully, but these errors were encountered:
in the case you're talking about printers inventories via network (netdiscovery & netinventory tasks) can you provide a snmpwalk output in the expected format for each concerned models ?
If you're talking about printers reported in a computer inventory, can you share the "printers" section of the computer inventory ?
Bug reporting acknowledgment
Yes, I read it
Professional support
None
Describe the bug
GLPI Agent report incorrect SN for some HP LaserJet Printers. It adds "00" to beginning, rest of SN follows correctly, but this is enough for SN not to be matched, thus creating duplicate printers.
So far seen for HP LaserJet P2015d and HP LaserJet P2055dn.
To reproduce
Run GLPI Agent.
Compare SNs of detected HP LJ printers to their real SNs.
Expected behavior
GLPI should adjust the SN internally in order to report correct SN. The correct SN for HP is exactly 10 letters long.
Operating system
Windows
GLPI Agent version
1.7.3
GLPI version
10.0.14
GLPIInventory plugin or other plugin version
Not applicable
Additional context
No response
The text was updated successfully, but these errors were encountered: