Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > SAM Script Monitors 'LocalHost' vs Remote Host Execution Explained

SAM Script Monitors 'LocalHost' vs Remote Host Execution Explained

Table of contents
Created by Shane Horgan, last modified by Melanie Boyd on Nov 09, 2017

Views: 109 Votes: 1 Revisions: 3

Updated November 9, 2017


This article explains the difference between SAM's Script monitors Execution Mode. 




  • SAM, all versions


In Local execution mode, the script is run "on" the Orion server itself.

  • The code that executes might query remote resources, but the code is running locally on the Orion server.


In Remote Execution mode:

  • The code is executed "on" the remote computer itself.
  • This mode of operation requires properly configuring WinRM on both the Orion server, as well as the remote host.


Note: You can achieve the same results as remote execution mode without the need to configure WinRM by installing the Orion Agent on the remote host and using local execution mode.


Suggested Tags:  SAM, Script, Monitors, Linux, Unix, Pearl, Bash,PowershellLolcah


Reason for Rework or Feedback from Technical Content Review:



Last modified