@Russ yes it was down for about 2 hours yesterday, now work correctly 🙂

@Russ Ty.. works for me.. Now, I will try turn off this.. lol

@Adroit-Tester2, the background agent on Windows is meant to run commands that don't do anything with the GUI, like this reboot command:

shutdown /r /t 1

One benefit is the TRIGGERcmdAgent Windows service runs before you login, so you could reboot the PC even if it's not logged in.

Background commands run in the context of the TRIGGERcmdAgent Windows service that runs as Local System, which can be of benefit too because it has full access to your PC and it bypasses UAC.

Here's a test command you use try in background mode to verify it's working:

echo testing > c:\folder\log.txt

I just tried that and it produced the log.txt file when I ran it in background mode.

If you want to see the processes run, I suggest you leave them in foreground mode. You could still lock the PC after logging it on if you don't the developers to mess with them.

@tommy0981, the token is on the Instructions page and on your Profile page.

@Severus, please look for the "tray" icon. It looks like the square Triggercmd icon. You have to click the up arrow near the clock in the lower right corner of the screen to see your tray icons.

@Jeferson-Borges, have you found the GUI Command Editor?

You can use it to add your commands, like this:

a7b17bdd-a9ef-4adb-873d-82486d97e561-image.png

To open the GUI Command Editor, right click the TRIGGERcmd Agent's tray icon first:

20784eb0-6554-40e4-824a-450bb3dfe7e7-image.png