No checking of existing serial when importing monitors in database

[Neutro]

Hey guys,

OCS server version: 2.1.2 (unix)
OCS client version: 2.1.1.1 (windows 7)

I noticed that when a monitor get imported in the ocsweb database, there is no test to check if that monitor serial already exist in the "monitors" database.

So if you unplug a monitor and plug it to another computer, instead of just changing the hardware_id reference of the existing database entry for that monitor, it creates a duplicate entry.

This bug also create problems for GLPI users because as GLPI does check for existing serial in database, this duplicate entry won't be imported into GLPI database, preventing the computer/monitor link to be properly updated.

The only solution i found until now to deal with this problem is to manually delete oldest duplicate entries using mysql queries before importing ocs inventory datas to GLPI.

Thanks for your help!

Best regards,

Kevin.

[Skyleeder (skyleeder)]

OCS server version: 2.0.5.0
OCS client version: 2.0.5.0

I noticed that when a monitor get imported in the ocsweb database, there is no test to check if that monitor serial already exist in the "monitors" database.

So if you unplug a monitor and plug it to another computer, instead of just changing the hardware_id reference of the existing database entry for that monitor, it creates a duplicate entry.

This bug also create problems for GLPI users because as GLPI does check for existing serial in database, this duplicate entry won't be imported into GLPI database, preventing the computer/monitor link to be properly updated.

The only solution i found until now to deal with this problem is to manually delete oldest duplicate entries using mysql queries before importing ocs inventory datas to GLPI.

Thanks for your help!
Best regards