If you own SolarWinds Engineers Toolset (ETS), and any SolarWinds products shipped with Orion platform you can leverage the functionality of Toolset directly from Orion platform based products. For more on Orion Integration with Engineer’s Toolset refer to Craig’s blog.


You may have ETS installed on a laptop, helpdesk agent system or any system on your network and happen to use the integration functionality to Orion. If that's so, then you are familiar with the tool you call by right clicking on a node. The tool runs on the local machine therefore the traffic is sourced from your local machine and not the server. The below diagram gives a visual representation of the deployment where Engineers Toolset resides outside of the Orion server. Using the Engineers Toolset - Orion integration function by right clicked a node (switch-32-01), the source traffic originates from the system running Engineers Toolset ( and the reply is send to the same system, while the local machine displays the output.



Why do I, need to source the tool from my Orion server and How do I achieve it?


You may have restrictions with in your organization, that does not allow your ETS machine to access some of your network and want to call simple tools from your Orion server without buying another ETS license. In this case, you would want some mechanism to perform this functionality. Lets see, how to achieve calling PING tool from an Orion server.

  1. Download and install PsTools from Microsoft, specifically you will need PsExec. Install this on your Orion server. PsExec allows you to run commands on your remote machine.
  2. Create a batch script (*bat) and save it into the same local folder where PsTools was installed. Batch files are useful for storing set of DOS commands that are executed by calling its name.

Here's a sample batch script.


echo off

cmd /K <path>\psexec.exe \\%1 <remote cmd> %2

To break down the batch script parameters,

- echo off:  Will turn off the command you put in a batch file from showing itself,

- /K: Carries out the command specified by string and continues (in my case carries out cmd.exe and continues to the installation folder of psexec.exe),

- <path>: Is the local (Orion server) folder where psexec.exe is installed, %1 carries out the first command line argument (IP Address of the Orion server),

- <remote cmd>: Is any DOS commands which will be executed from the source machine/Orion server, and

- %2:  carries out the second command line argument (which is the IP Address of the remote device, you PING)


This script executes PING on the Orion server and displays the resulting output locally (in this case Orion server)


echo off
cmd /K C:\Tools\psexec.exe \\%1 ping %2


and the below for TRACEROUTE


echo off
cmd /K C:\Tools\psexec.exe \\%1 tracert %2


  3. Next, on your ETS system. Go to Engineer’s Toolset Integration tray icon and update the right click menu to include your remotely executed command.



   4. Go to Menu Items tab and click “Create, delete and edit menu items”


   5. Input Target path and Command-Line Arguments into Item Details page (as shown below)



6. Transfer the new menu items from the Available field box into the selected Menu field.


7. Open Orion web Console and use the Engineer’s Toolset Integration Menu. The new menu items should appear and can be used to execute the remote command to targeted nodes.


If you're an Orion customer and you haven't tried the Engineer's Toolset, you can learn more about it here.