Skipped device - in SyncHardwareAssets log

Omar_Al-Omari

We noticed that many servers and workstations are not synchronized to Cireson Hardware Assets.

when we checked the Hardware Synchronization log we found the following entries for each missed device.

Skipped device "HQ-XX" - it has no associated Hardware Asset but it is not the newest Windows Computer with the same SID

 please advise. thanks in advance.

Geoff_Ross

Hi Omar,

There's a setting in the Hardware Asset sync settings about how to handle multiple computer with the same SID. You must have that set to 'ignore all but the newest record' which is useful if you rename a PC as you get a new computer record with the same SID as the old one. You don't want to create a Hardware Asset for both - only the latest.

You will need to investigate why you have multiple records with the same SID. A common case of this is multiple records with a blank SID due to data not flowing properly from AD / ConfigMan.

Geoff

Omar_Al-Omari

Hi,

Sorry for the late response. I want to add one important point, we have investigated the issue again and fixed many of these issues, however, all the remaining skipped machines are belonging to another AD forest.
we enabled AD forest discovery in SCCM to manage another forest in the production environment (no trusts available). so the source data for these servers and workstations is SCCM only. we have no AD connector to that forest in SCSM.

is there any limitation to import these servers and workstations for this scenario?

Brett_Moffett

Hi @Omar_Al-Omari,
If your ConfigMgr connector is bringing in the Computer CI information it will not bring in the AD SID. This will always be blank.
The SID is published to the computer CI using an AD Connector. This SID is useful like @Geoff_Ross said as it can be used to identify 2 computers that are the same but have different names (Due to someone renaming the computer)
This can cause all sorts of issues, like the one described here: https://community.cireson.com/discussion/comment/5479/

In your scenario you are wanting the computer CI's to create a new Hardware Asset to sync it to. This is done via the setting within the Cireson AM Settings that identifies what value is the key value for linking CI's.

This property ensures that a "Hardware Asset will only be created.... if the property value exists on the relevant class...  and the value will be used for Hardware Asset ID"

If this is set to SID, and you do not have the SID published from AD to SCSM, then it will skip creating this new asset.

I hope this answers your question.

Geoff_Ross

@Omar_Al-Omari  @Brett_Moffett
There's another setting that will also cause this, even if using another property than SID for the HWAId.



If you have that checked, and have CIs with missing SIDs they will all be skipped (except the newest) and they are 'the same SID' as each other.