SCCM Integration Not updating the existing Ci created manually

[satyavar12]

Hi All,

Good Morning.

We have a requirement where some of the Workstations are manually created in CMDB and stored in cmdb for 15 days stock period until

its deployed in SCCM. Post the sccm deployment the customer wants the data to updated with all information coming from sccm But We are having difficulty as we have the name to be the unique Colesce factor.

Whenever we run a sync the corelation id does not get updated for the manually created ci in sys_object_source as we have SCCM id identifier activated.

Without the corelation id the further jobs will not update the disk and software information.

Can anyone help on how to proceed further can we deactivate the sccm id identifier as we have only name to be the unique factor in our environment.

Regards

Satya

[peterh_smith]

You should enable identifiers to match on correlation id first, and serial number later.   Your manual creation process needs to include correct entry of the serial number.   If your assets have barcodes or QR codes, enable the barcode reader on the serial number field and scan to create stubs with just the serial number filled out.   Then add columns on a list filtered for recently created records.   Of course, you can get fancier than that...

[satyavar12]

HI Peter,

We just have computer name information and some of the Business Unit information available in manually created Ci's.

Will creating an identifier to match the name of the Ci first will it help as sccm identifier is up in the order can i make the name and class name identifier move to the higher order and will this problem be fixed i need the help on this query.

Regards

Satya

[peterh_smith]

You want to keep the SCCM identifier ahead of the Name identifier.

The first time through, it won't find a match.

Then the Name identifier will find a match.

When the CI is populated, the correlation ID will be set.

The next time through, the match will be on correlation ID.

In Discovery Definition > CI Identification > Identifiers, make sure the Generic Name identifier is enabled.   If you filter on Applies to=cmdb_ci_hardware and sort by Order, you can see the precedence of the identifiers.   Generic Name is after more reliable identifiers.   Check to be sure it is active.

In System Properties > Discovery there is a checkbox for CI Identification debugging.   You can see more of the identification process by enabling it.   Remember to disable it when you are done because it bogs down the instance.

If you have a training budget, I highly recommend the Discovery training.   You might want to wait until it gets upgraded for Jakarta.   They'll walk through the probe, classify, identify, explore process and how to debug/customize.