We have a WMI File sensor that monitors the last write time of a file on another server. Since daylight savings, the sensor always reports the file is 1 hour behind. The probe server and the monitored server both have the same time. The probe has been restarted, and the monitored server has been restarted. We've even deleted and recreated the sensor.
How do we get this sensor to report the correct write time on the file?
Article Comments
Changing my timezone did reslove the issue, but now I'm wondering why this is necessary. My timezone is set to Pacific time, so I would expect PRTG to recognize the time change.
Before, PRTG's server, the target server, and the user timezone were all the same, Pacific. Now I have the user timezone set to Arizona, which is technically the wrong timezone, but it fixes the issue.
Am I expected to change the user's timezones every 6 months?
Mar, 2015 - Permalink
Is Windows on the client PC set to automatically handle daylight saving time?
Then you shouldn't need to do it, actually. Like in the following screenshot
from the time zone settings :
Mar, 2015 - Permalink
What timezone is configured for the user within PRTG in his account? It should be the same as on the PC used for accessing PRTG :)
Mar, 2015 - Permalink