Ah, yeah, I talked to Harlam (maker of HFM) about that. He said it's more an issue with the VMware than the monitoring programs, so there's nothing much to be done about it.
He said he posted in the VMware guide about it; I'll see if I can find it.
Yeah, here's what he said:
Originally Posted by Harlam357
This isn't necessarily an HFM bug. HFM is reading the Download Time as reported by the client running inside the VM. That client is running in a different time frame (i.e. it's date and time are not correct) than the machine running HFM. One can counter this issue by using either the:
- Client is on Virtual Machine option (which will make HFM interpret the timestamps in the logs as if they are local time and not UTC values)
- Client Time Offset (which can be used to manually adjust the time difference between the monitored client and the machine running HFM)
Because HFM uses the Download Time as a basis for calculating Bonus Credit and PPD, these values will be off as well. What I could do, in this situation where the client is running in a different time frame, is just use the frame time itself as a basis for the total time of completion for the unit. It would be less accurate than using the Download Time, but it would allow HFM to report a more sensible value in this situation.