System Monitor in Empower 2

[aquaregia]

Hey all. I'm new to this forum. Has anyone had any trouble with this functionality in Empower 2? I support Empower at my company and I use this to check active/running systems prior to rebooting LAC/Es. However, I have seen numerous times a system saying it is running but have called the user to find their run has finished. Any ideas what might be causing this? I know you get an warning msg when rebooting the LAC/E but would be nice if this was accurate. We often have e-sat/in boxes which are monitoring but not acquiring data which can be a pain without the system monitor.

Thanks

[DR]

If the LAC/Es are not close enough for you to stroll over and have a look at the LCs connected to them, call the users to be sure if there's any indication that a LC is running. Even if they're monitoring, they'll appreciate hearing that they shouldn't start a run for a few minutes rather than having to call you asking why their systems went offline.

[aquaregia]

I do call them to ask or send a mail where possible. We have LAC/Es scattered all over the place in 10 Labs so its not possible to check them all everytime. I suppose the question I was asking is have any of you seen or noticed the system monitor functionality not working properly and if so any ideas why. It seems to freeze in time and then kick in again later.

[DR]

I think you can manually update it if you've left it open for a while. It doesn't update itself often...

If someone is monitoring, I take that to mean they intend to run very soon (so I call before remote-rebooting).

Next thing to consider - why are you having to reboot LAC/Es?
Ours are setup to do receive any Windows/AV software etc. etc. at 4AM on Monday morning, when few, if any runs are still going. This way, I just open a remote desktop session to each one when I arrive on Monday (this is WAY faster than bringing up properties via Empower). I do not even have to login to the LAC/E. If it pops up asking for a user ID/Password, it's OK, I hit escape and alter teh number in the dialog box to ping the next one. If not, I know it will have to be rebooted. As it is prior to anyone having started any runs for the new week, I just make a list of LAC/Es that need resetting, then run through the labs with the list and a paper clip.

[vofelyp]

Hi
Run c:\empower\bin\sysmon.exe