SCCM not updating Asset records properly ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2016 01:48 AM
Hi All,
We are using the OOB SCCM Integration for loading CMDB and Asset data.But we have found that it is not loading the Asset data correctly in our system.
The data source which is used for identifying CI's and Asset is "SCCM 2012 computer identity". When we run this it finds around 20,000 workstations, but it only inserts around 2000 assets.
So we are not able to find/debug like why it is not inserting assets for all workstations.
We were expecting that it will create around 20,000 asset records, but it was only creating 2000 assets. So does anyone knows, the reason behind this ?
Or if someone can guide us on any approach which we can follow to debug this ?
Thanks and Regards,
Gaurav Kumar
- Labels:
-
Scripting and Coding
-
Team Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2016 03:11 AM
Hi Gaurav,
I'm not an expert on this but I've been testing some things with the SCCM integration lately and I've found myself with some similar errors, so here's my recent experience, it may help you.
First of all, make sure all these registries are correctly imported into the intermediate tables where data is stored before being transformed into the destination table (something like imp_sccm2012v2_computer_id). If the table doesn't have all the registries you expected to be imported, review the datasource of the scheduled import, there may be some incorrect qualification that is leaving out some of the assets. Or maybe you have the 'Last run datetime' populated, which is supposed to be the condition used by the query to collect only the registries on the DB that have been modified after that date.
On the other hand, if the 20,000 records have been imported, you may have some issues with the transform map, ranging from incorrect format (be very careful with the format for the date-type fields) to incorrect selection of the coalesce fields along with some scripting code to ignore new registries (if (action == "insert") { ignore = true; }). You can also review your Identifiers (ci_identifier table) to assure the default asset identification rules included when activating the SCCM plugin still apply if you have any custom configuration.
Hope this helps.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-06-2016 11:35 PM
Has SCCM crreated all 20000 workstations as CI's?
If yes then look at model categories for those CI's that do not have a linked asset. If the field "Enforce CI verification" is set to true NO assets will be created. The CI will have the flag "Requires verification" set to true.