I've been working this issue for a few days, even had our Windows Sysadmin at our company take a look. Windows is somehow preventing OME from launching an application (i.e. calling a batch script) in response to an alert. I can run the script manually on the command line and it works. However when I provide the full path of the script to OME to run the script as an "Alert Application Launch" it does not work. It appears on the surface that something in Windows is blocking the OME application from running this script.
If there's a known remedy for this issue please somebody point me in the right direction. I've reconfigured the user ownership on the script, I've altered the OME applications (DSM*) to run under a local account with admin privileges as opposed to the default - running under the System account. I normally work with Linux so I'm not a Windows expert but as mentioned I received help from our Windows admin and he could not figure it out.
Description:
running batch file manually on command line: works fine, all expected results
providing full path of batch file to OME as an Alert Application Launch and testing : no results, only indications in the Windows Event Viewer under Application Logs of the following - "A device or program has requested your attention. Device or application: C:\Windows\system32\cmd.exe." Of course no further details are provided (lovely, Microsoft).
Thanks,
Dan