GuardPoint10 has a action called "Run external app" as part of its global reflex module.
This action is very useful as it can be used to trigger third party apps from a transaction event.
Examples would be:
Access Granted ---> send a command to a third party lift controller
start of alarm from input ---> open intercom software
start of alarm from input ---> send message to sms software
start of alarm from input ---> open cctv software
The "Run external app" command is executed on the server and there maybe situation you wish to execute software which is not located on the server computer.
Microsoft offers a program called PSExec which allows you to execute a program on a remote computer:
It can be downloaded from: https://docs.microsoft.com/en-us/sysinternals/downloads/psexec
Note:
The PSExec.exe or PSExec64.exe should be put into the windows/system32 folder it you do not wish to specify its location as part of the command line
an example of the PSExec command would be:
PsExec64 -i 1 -d \\DESKTOP-IHB8IIS -u dave -p password \\DESKTOP-IHB8IIS\Test\vms\VmsCommandline.exe
PsExec64 - is used we are using a 64 bit operating system
Flags:
-i 1 specifies the windows session ID on the remote computer (you can have many users logged into the same windows PC so you must specify the session)
you can find out the session ID in Task manager
-d do not wait for process to terminate
\\DESKTOP-IHB8IIS this is the workstation name or IP address
-u dave -p password username and password of a windows local admin on the workstation computer
\\DESKTOP-IHB8IIS\Test\vms\VmsCommandline.exe location and file name of the program to execute this folder must be shared
if you receive a access denied message and your sure the username and password is correct and the folder of the application is shared you may need to make a registry change:
- Open RegEdit on your workstation
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- Add a new DWORD value called LocalAccountTokenFilterPolicy
- Set its value to 1
- Reboot your workstation computer
If the command it taking too long to run try disabling windows defender firewall for the local network
Note:
always test the command first in command prompt before putting into GuardPoint10
Comments
0 comments
Please sign in to leave a comment.