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

bill_blaney · ‎08-06-2018

Hi Rish. What attributes are being updated? Keep in mind that the SCCM import uses several data sources (SCCM 2012 v2 Computer Identity, SCCM 2012 v2 Operating System, SCCM 2012 v2 Processor, SCCM 2012 v2 Disk, SCCM 2012 v2 Network, SCCM 2012 v2 Software, etc.). If your requirement is to prevent any and all updates to non-Workstation CIs, you'd need to introduce similar "ignore" logic to all the related maps.

(*edited data source list above to properly name the computer identity one)

Kumar38 · ‎08-06-2018

Modified SQL Query to let SCCM Import only Workstations.

I think this should fix the Issue !

bill_blaney · ‎08-06-2018

That works, too! The only thing to keep in mind is the ServiceNow upgrade process. By altering the SQL (Data Source record), you run the risk of having issues when upgrading (i.e. missing out on a change that ServiceNow makes to the same record). However, my experience has been that these records are stable and ServiceNow releases new versions of the SCCM plugin when making changes, so I think you should be fine.

I always like the idea of altering behavior by adding additional records (like you did with the additional onBefore Transform Script) because that protects you a bit more when it comes to updates/upgrades.

Kumar38 · ‎08-06-2018

Is it like Only Data Source "SCCM 2012 v2 Computer Identity" will create Windows Server ?

I modified SQL for "SCCM 2012 v2 Computer Identity" and tested in SQL and it worked fine.

But after finishing executing of "SCCM 2012 v2 Computer Identity" and child "SCCM 2012 Network " is running.

I see Windows Server records are getting created. Any Idea ?

bill_blaney · ‎08-06-2018

What does the updated SQL (in the related ServiceNow data source) look like now? Also, are you using the "Use last run datetime" flag?

Are there processed records in the "SCCM 2012 v2 Computer Identity" import set table (for the import set id tied to your latest import run) that correspond to these servers you feel should not get created?