SAM Script Polling Local on Monitored Windows Server

Mike_Lomax

I have to admit that I am not sure how to search the forums for this one.  While the answer might be out there, I have not found it.

My background is more as a UNIX System Administrator and most of my polling at this point has been of UNIX servers using SAM with Perl scripts in "Linux/Unix Script Monitor" Component Monitors.  Let me also explain that I work for a software manufacturer and the nodes I am monitoring are, for the most part, owned by our customers.  While I have ventured into some monitoring on a few Windows Servers in the past I am really just starting to get involved in diving deeper.

With the UNIX script monitors I have created, I load up a Perl script and during the poll of the monitored server, the script is downloaded to the server and run locally on that monitored, UNIX server.  From what I am figuring out with setting up monitor scripts for Windows Servers, the scripts are run on the Orion server, pulling the data back from the monitored Windows Server across the network.  To do this requires the use of equally credentialed user accounts on both servers.  Because we don't own these monitored servers, setting up these matching accounts on both is not an option in most cases.

My preference would be to run these scripts on the monitored server and return the data to SAM from the monitored server.  I do have administrator access to all of these monitored Windows Servers so the accessibility for this is in place.  I am just not figuring how to set up the monitor itself.

Am I missing something or is there another way to do this?

aLTeReGo

Based on your description of the problem it sounds as though you are looking at using the Windows Script Monitor, which does in fact run locally on the Orion server itself. There is really no way without an agent running on those hosts to execute Perl or VBscript in the same way you do Linux/Unix hosts via SSH. Not all hope is lost though. You can instead use WinRM to execute PowerShell remotely in a similar fashion to Linux/Unix hosts. While it doesn't use SSH, it instead uses Windows Remote Management (WinRM) to establish the connection with the remote host and execute the script. To leverage this functionality you would use SAM's Windows PowerShell Monitor.