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

Kumar38
Kilo Sage

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 ?

1 ACCEPTED SOLUTION

bill_blaney
Kilo Expert

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

11 REPLIES 11

sachin_namjoshi
Kilo Patron
Kilo Patron

Hi, 

 

The SCCM integration takes information from the SCCM database and updates existing or creates new Computer Records in the Service Now CMDB.

 

A computer that has been deleted from SCCM is simply a Computer Record in the CMDB that was not updated. The LastHwardwareScan date will help you identify Computers that have not updated from SCCM, however you risk deactivating Computers if you action this field - you will need to validate that the device has been removed, most likely via other hardware asset management processes.

 

Regards,

Sachin

 

Thanks for response. I posted question Wrongly. Just  Updated

bill_blaney
Kilo Expert

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?

I wrote a OnBefore Transform Script on Table Transform Script "SCCM 2012 Computer Identity" .


if (source.u_systemrole != "Workstation"){
ignore=true;
}

It is stopping Windows Servers from Creation but Old records are getting Updated. Need help with this Issue.

Please Let me Know , what further changes need to be made.