OK, fair enough, the PRTG document describes the issue nicely. I accept there is a valid reason for excluding Windows Server from using this value if it's going to wrap around so quickly. Might be worth putting a comment in the code as to why "Windows" devices are excluded and then will prevent other people reporting this "bug" again. I guess we have to live with the fact Microsoft won't support Open Standards and does things it's own proprietary way. I guess there many be something in WMI that resolves this, but that's another new "can of worms". Regards Chris Macneill Web: www.cmit.nz _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium