Purpose of SCCM Last run datetime

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 02:00 PM
I need some help understanding how the 'Use last run datetime' option works within the SCCM 2012 v2 Computer Identity Data Source for SCCM imports.
We have the following values set:
Use last run datetime: enabled
Last run datetime: '2018-10-06 01:33:39.0' (NOTE: I am writing this at 2018-10-05 13:54)
Last run database field: LastHWScan
We have a device, that when the import is executed, is not getting picked up, but if we disable the Use last run datetime then it is picked up. The Value on the device for the LastHWScan field is 2018-10-01 10:31:25.000. We have had this import running every 3 hours for a month and it has never picked up this device.
So I want to know when should you have the last run datetime enabled? With it enabled, am I running the risk of not catching other devices? And finally, with it enabled, why is this one particular device getting missed?
Thanks in advance!
Donald

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2018 09:56 AM
Greetings Donald,
It is set when the data source is run, so large organizations can get their imports completed in a timely manner. Delta imports are important for large data imports. If the time getting set is not just a factor of time zone display values open a ticket with HI.
-Andrew Barnes

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2018 04:10 PM
Thank you Andrew. But does it make sense that the Last Run datetime is getting set 12 hours in the future? To me, I read this as if the last run datetime is after the date in the database field then capture that delta. But with the last run datetime being 12 hours in the future, it will never pick up those changes? Maybe I am just misunderstanding the whole concept of this and I don't even need it enabled..
-Donald

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2019 10:12 AM
Hi Donald,
Have you got the reason, same issue I have been facing, instead of setting today's date, it is setting 2019-05-31 17:53:23:0, which is not appropiate

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2019 10:26 AM
Hello!
I have not gotten any further answers. I ended up turning off the option to use Lastrun date. We have not noticed any hit on our performance, and have seen our assets getting regular updates. We do not have a large volume of assets though, so that may make a difference.