I have problem with "execute" function. It works on the older version Dude ver 4.0 beta3 but doesn't work on the last version 6.37rc5. Below is my example with the batch file (test.bat) where is @echo 3. Is it a bug or my mistake?


------

I'm running 4b3 in production and have been testing new Dude releases on a CHM.  My migrated probes using "execute local" do not work on latest Dude; notifications do, but probes do not.

  I figure the cause is CHM (Dude Server) can't execute windows-based scripts as a probe function.  Dude 4b3 runs on Windows; hence, there's a cmd interpreter that 4b3 can execute against.  Not so in the later versions of Dude - at least not in my testing.  Notifications using execute locally, on the other hand, seem to work when the Windows Dude client is connected to the Dude server.  It's worth noting that when two Dude clients are connected, notifications that call "execute local" will execute two notification actions - one for each running client.