Hi This is not even attached to a monitor yet, and I was testing by running the "test" gui, although I also tried it out against a disk space monitor. Eventually I'd like to trigger it from another script based monitor that alerts on a performance counter value, once I can get past this functionality issue. The script is simply (for now, I have a much more lengthy script I'd eventually like to use, which I have proven works/doesn't work in the same fashion) > "test content" |out-file > c:\temp\log.log c:\\temp\\log.log -Append I've done alot of testing and this is my first effort at seeking support. My issue is that this script only works when I run the test 'against' certain servers. - Why would this be the case? - Is it perhaps that PAmon tries to "do something" to these servers I am testing against prior to running the script? - Is there a way to turn on more verbose action script logging? - Is this something we can troubleshoot more effectively over a more formal support session? thanks

Hi This is not even attached to a monitor yet, and I was testing by running the "test" gui, although I also tried it out against a disk space monitor. Eventually I'd like to trigger it from another script based monitor that alerts on a performance counter value, once I can get past this functionality issue. The script is simply (for now, I have a much more lengthy script I'd eventually like to use, which I have proven works/doesn't work in the same fashion) > "test content" |out-file > c:\temp\log.log -Append I've done alot of testing and this is my first effort at seeking support. My issue is that this script only works when I run the test 'against' certain servers. - Why would this be the case? - Is it perhaps that PAmon tries to "do something" to these servers I am testing against prior to running the script? - Is there a way to turn on more verbose action script logging? - Is this something we can troubleshoot more effectively over a more formal support session? thanks