‎06-25-2019 12:58 PM
‎06-28-2019 10:35 AM
In general when testing and creating custom actions, we recommend starting with a command that works in CMD, which you then replace with the action-specific parameters such as {actionpath}, {ipaddress}, etc.
The below should work, if ShellRunAs.exe is in your actions folder and your action path is correct under Configuration\Asset Pages.
"{actionpath}ShellRunAs.exe" /netonly /accepteula services.msc /computer:{ipaddress}
If there is an issue though, try placing the command in CMD, replacing {actionpath} with your action path, and {ipaddress} with the IP address of one of your remote computers.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now