Snapin History - Duration is wrong.
- FOG Version: 1.3.0 RC-16 pulled minutes ago
- OS: CentOS 7
- Service Version: 0.11.5
- OS: Win10
Snapin history duration is not right. These snapins were created with RC-14. Their duration lists they have been going for 2016 years.
I’m solving and moving though, this is not a bug. The snapin never completed, and all I care about is if the start time is within the “scope” you’re searching for.
@Quazz That is exactly the case.
The default insert time for any “DATETIME/TIMESTAMP” is typically 0000-00-00 00:00:00
Being as today is: 2016-10-27 09:58:46 You take the start time (which may or may not be set yet) and it see’s it as literally the Year 0, Month 0, day 0, at midnight.
In your case @Wayne-Workman The snapin never completed, so it’s showing it accurately.
It says the snapin is still queued, which means it has no completion time.
I’m guessing the formula for duration is
completion time - start time
So, most likely it simply doesn’t have a completion time yet.