No, I don't think you can either. What I did when the client was troublesome was set up an ftp server on my main machine, and a ftp script on each of my nodes running hourly that ftped the stats file (I think) to my server (renamed the existing one to bak first), then compared the two files. I had this running once a day (since I couldn't be bothered to check it more often with the number of nodes I had) and easily identified the stuck machines because the stats file wouldn't have changed over the 1 hour. I used the node number as the file (eg, in the ftp script I had something like this:
delete 12345.bak
rename 12345 12345.bak
put stats.prp 12345
Obviously, on each machine I did this, I needed to tinker just a bit with the ftp script. You can get ftp to use a script by calling
ftp -s scriptname <server-ip>
and put it in the Windows scheduler to run hourly 🙂
Geoff