Hi Raj,
If the computer CIs are deleted, the corresponding records created in sys_object_source for the computer records may not have been cleaned out. It will still exist with invalid target sysids. During Intune software processing, it does a lookup for the computer name based on the sys_object_source entry matching on the source native key for the computer/device. It probably picks up a target computer record with an invalid sysid(deleted computers). IRE team has a scheduled job to clean up the invalid sys_object_source entries so it does not exist in the first place. I think the window it keeps the record, even if it is invalid, is still 90 days. IRE made a change recently to remove the 90 days threshold for invalid records and it is fixed in SD or upcoming release I want to say. We are also fixing this issue in the Intune Integration.
Until then, do this as a work around:
Run this test script and see how many computer records that are currently invalid and you can easily modify this script to delete those invalid records from sys_object_source. Again, not sure how many you have and the volume of your sys_object_source. Highly recommend that you test this first in your dev/uat environment prior to implementing this in Prod.
------------------
// List a count of invalid sys_object_source records for a source/feed
var emptyRecords = 0;
start();
function start() {
var gr = new GlideRecord("sys_object_source");
gr.addQuery("name=SG-Intune^source_feed=SG-Intune Computers^last_scan<javascript:gs.endOfToday()");
gr.query();
while (gr.next()) {
var grTargetTable = new GlideRecord(gr.getValue("target_table"));
if (!grTargetTable.get(gr.getValue("target_sys_id"))) {
// Target Computer CI record does not exist. We need to delete this invalid sys_object_source record.
emptyRecords++;
//gs.info("Empty Sysid record = "+gr.sys_id);
}
}
}
gs.info('Empty Records: '+emptyRecords);
------------------
Do the same for SG-Intune Device feed if mobile devices were deleted as well. Basic idea is to clean up the sys_object_source entries that may have reference to an invalid target sys_id of a device/computer.
After the cleanup, run your software and see if it fixes your issue.
