Hardware Model duplicates after publishing to the hardware catalog

[SleepingCoder]

Hi,

I'm using Tokyo release SG-SCCM to collect SCCM data and populate the CMDB with end user computing information.  We have a small number of models in the organisation so it's fairly simple to grab the latest and publish it to the hardware catalog.  This is my first time using the product catalog and so this maybe something straight forward to sort.

My first catalog item was a laptop.  I selected it from the "Product Catalog"->"Product Models"->"Hardware Models", filled in the unpopulated information that might be needed, then published it to the hardware catalog.  The laptop has successfully appeared in the hardware catalog and is available to do what we need.

The next day when I've gone in to do some finessing of the catalog item I found htat there was a new Hardware Model for the same model laptop and that any newly updated SCCM/AD objects had been put in to this hardware model.  

Is there any way to ensure that this duplication doesn't occur when I update and publish a Hardware Model to the Product Catalog?

Thanks in advance

[Houston Vargas]

Have you been able to figure this out? I am running into the same issue. I cleaned up all my hardware models but upon the next day after SG-SCCM import, there's so many duplicate items showing up again. I wonder if this is an issue with SNMP OIDs or perhaps even an issue with SCCM. Just trying to figure out the root cause issue. We have HAM/SAM pro on Tokyo and I know that we have the Asset < Content Service turned on for all options. I understand that's supposed to help with normalizing for the most part.

[SleepingCoder]

Hey,

No I haven't resolved it.  At this stage I'm working around it by creating a product catalog hardware model for the specific models we want to publish in the hardware catalog and leaving the SG-SCCM integration to do it's thing.  The duplication only occurs when I update that hardware model with extra details and activate it to the product catalog.  Duplication doesn't happen otherwise for me.  I don't have HAM Pro so am not surprised that we get duplications though am very surprised that you are experiencing them with these licenses.  

[Houston Vargas]

So just to provide an update. Best practice from what I keep seeing online seems like we need to use the product models (and their product catalog items) first to populate the devices. SCCM will later refer and update those existing devices. I think what may need to happen is an IRE rule to prevent duplicates from being created and reference those existing devices that have been scanned into stockrooms. I'm surprised that isn't a thing already in the HAM modules.. especially with SCCM connector involved. However, for me, I have issues doing that. I just attempted to scan items ahead of time, just to see what happens. Imaged a new device that was scanned in and saw that a duplicate was created.. maybe that's source of the issue there. Mind you this is all out of the box. I don't have any IRE rules setup for hardware devices. I'm going to switch the priority on the Correlation ID and make Serial Number first.. maybe that aught to fix the duplication issue from SCCM's side. Also, wondering if you found anything else new.. there's also an recent HAM update, that fixes "normalization" issues.. perhaps that might help you as well. I updated mine just to see if anything might change but hoping with some testing that this issue is put to rest finally.