- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-27-2022 06:45 AM
Hi All,
I have observed that the SG-SCCM (Service Graph Connector for SCCM) is not updating the windows server second time.
As highlighted in above screenshot, I ran the job "SG-SCCM Computer Identity" first time at (2022-06-27 09:20:00) and the fields are getting updated as per entity field mapping from robust transformer "SG-SCCM Computer Identity",
I cleared out the updated fields manually and ran the job again after few minutes (2022-06-27 09:28:00) and observed that the fields are not getting updated.
On the first run the "IRE Output Aggregate Stats" shows the windows server is updated = 1, but it shows unchanged = 1 on second run.
Reconciliation rules are configured to update the required fields
Please let me know if anyone observed the same behavior and help me with the workaround or fix.
Thanks,
JAS
Solved! Go to Solution.
- Labels:
-
Service Graph Connector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2022 09:30 AM
A record will not be updated if the scan date is the same or prior to the laast scan date. The IRE will check this value in the sys_object_source table and ignore records that aren't newly scanned. I'm guessing that your scan date from SCCM is the same so this is happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2022 11:07 PM
Hi JAS
I got the same problem here. Have any solution yet?
Thanks,
Saran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-28-2022 11:49 PM
No, i haven't find the root cause and fix yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2022 09:30 AM
A record will not be updated if the scan date is the same or prior to the laast scan date. The IRE will check this value in the sys_object_source table and ignore records that aren't newly scanned. I'm guessing that your scan date from SCCM is the same so this is happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-04-2022 08:04 AM
Thank you, Its working now