Will SCCM recreate deleted Personal Computer or Windows server records from CMDB ?

Kumar38 · ‎07-31-2018

Deleted few Personal Computer records and Windows server records.

Clicked on Execute Now and didn't see any thing happening.

So Manually Transformed Import sets and didn't see deleted records getting created.

Tried deleting recently discovered devices from SCCM , even they aren't getting created again.

What could be the issue ?

bill_blaney · ‎07-31-2018

Hi Rish. There are a few things to consider that could be affecting the import behavior:

By design, the SCCM-to-ServiceNow import is incremental. If you look at the related data sources you'll probably see their "Use last run datetime" box checked and a "Last run datetime". This means that the next run of the SCCM import is only going to process any SCCM records that have been updated since that "Last run datetime". If I'm understanding the issue correctly, you deleted these items from ServiceNow. Nothing guarantees, however, that those items will be picked up by the next run of the import. It depends on whether or not they were updated in SCCM since the "Last run datetime".

I'm definitely not an SCCM expert, but if part of your troubleshooting was to delete items from SCCM, you may need to wait for those items to get recreated in SCCM (via the SCCM client on that machine and related policy). I believe there is a way to "force" that to happen from the client machine, but I'm not sure how to do that.

Does that help?

View solution in original post

Kumar38 · ‎08-06-2018

Updated SQL Just on "SCCM 2012 v2 Computer Identity" , Unchecked Last run date time on all Data Sources.

After "SCCM 2012 v2 Computer Identity" finished processing and the other Datasource is running that is when I saw a Windows Server record being Updated .

I assumed only ""SCCM 2012 v2 Computer Identity" " creates Personal Computers and Windows Server.

sachin_namjoshi · ‎07-31-2018

It depends on coalesce set for your SCCM transform map.

Please make sure that SCCM identifier script for colease sys_id is returning correct value.you will find root cause of your issue in this SCCM identifier coalesce script

Regards,

Sachin