8 Replies Latest reply on Mar 27, 2011 10:43 AM by AndyCoates

    Request: Remote Windows Script Monitor



      This has been driving me nuts and it's not available any any version of APM.

      Can we please have a 'Remote' Windows Script Monitor that is basically exactly the same as 'Windows Script Monitor', but is always run locally and the Credential selected is used for ${USER} and ${PASSWORD}.

      Right now for any Windows Script Monitor the Credential field is essentially useless as it always runs locally.  This means we have to hard-code (either in the code or as parameters) any customer credentials, which is bonkers when the APM credential library already stores their credentials.

      It could even be a toggle button on the current Windows Script Monitor that says like 'Remote Script', and ticking that launches it locally but populates ${USER} and ${PASSWORD} from the selected Credential.



        • Re: Request: Remote Windows Script Monitor

          Ok, I must be missing something here because the Credential for Monitoring is definitely passed to the ${USER} and ${PASSWORD} variables. Can you provide an example of the trouble you're running into?

            • Re: Request: Remote Windows Script Monitor

              It is passed, but for a Windows Script Monitor the Credential also seems to be used to actually launch the script locally on the machine, so the only credentials you can pick to launch the script are either <None> or the credentials for the local machine user - anything else results in an 'undefined' error.

              I always thought it was odd, so either we've been totally missing something obvious or it is like how I described it.

              As an example, you want to write a script that uses WMI on a remote machine for which the data returned needs parsing.  In the vbscript you'd want to pass the remote IP and the credentials to login to that remote machine - something you'd want SolarWinds to pass, so for the Windows Script Monitor arguments you put in ${IP} ${USER} ${PASSWORD} and select the relevant credentials for that remote machine you currently monitor.

              That makes total sense and is how I expected it to work, but it doesn't appear to work like that.  The script will not run with anything other than <None> or the credentials of the local machine, and of course by doing that you can't select the actual credentials you want to pass for the remote machine.