Windows agent not updating triggers on triggercmd.com, ST smartapp?

batteryxsnare

Hello - I just installed the Windows Agent on a Windows 10 VM and created a couple of triggers to test which work fine when run locally.

At first new triggers were appearing on triggercmd.com and only 1 showed in the ST smartapp (which makes sense as I read that a subscription is required for more than 1 trigger), but now they're not. I tried deleting the smartapp, triggers, and the agent and starting again but I'm still stuck - trigger runs locally but won't show at triggercmd.com or in smartapp.

Please help!

Thanks!

Jon

Russ

@batteryxsnare, it seems to me your computer is somehow now associated with your TRIGGERcmd account. Maybe you created two accounts, and it's associated with your other account?

Anyway, to make sure your computer is associated with your account, you can delete your c:\users(your user).TRIGGERcmdData folder, then close and re-open the TRIGGERcmd agent. It will re-prompt for a token, and you can paste in the token from the Instructions page in your TRIGGERcmd account.

I think that might solve it.

batteryxsnare

@russ as far as I know I only have one account, and I did just delete it from my account in the web interface as another attempt to fix it maybe 10 or 15 minutes ago...but I'll try deleting that directory and restarting to try again...thanks for the reply !

batteryxsnare

@russ OK - so I deleted the computer from triggercmd.com, uninstalled the agent, deleted c:\users\user.TRIGGERcmdData, re-installed, and created a trigger. Same result - trigger works locally but computer is listed on triggercmd.com with no triggers.

Russ

@batteryxsnare, here's another idea - are you creating your command as a background command? Background commands will only show up if you're running the background service.

Also, does Notepad and Calculator show up? Those are the default commands and they're foreground commands.

batteryxsnare

@russ I did create them as background because admittedly I didnt read the documentation and assumed that would allow them to run with a service (which i also assumed was installed) instead of in the foreground. So, I right-clicked the agent trayicon, clicked install background service, and verified it was running- but still no triggers showing in the cloud.

Notepad, calc, etc. showed up when I deleted the user files and reinstalled but I deleted them since I dont need them.

Russ

@batteryxsnare, sorry for the late reply. I almost missed your reply.

It seems your issue is just that your background service isn't working, so your background commands aren't getting created.

Can you check your Windows services to confirm the TRIGGERcmdAgent service started ok?

batteryxsnare

@russ when I checked it wasn't started...I tried uninstalling and re-installing but it still wasn't started after installation...that said, it has no problem starting when I manually start it. Once I manually start it, it starts back up fine automatically with reboots. Still no commands in the web interface though...

Russ

@batteryxsnare, do foreground commands show up in the web gui? I know you don't need them, but it would to know that as a troubleshooting step.

If foreground commands don't show up, then you should delete your c:\users(youruser).TRIGGERcmdData folder, and re-run the TRIGGERcmd Agent, and put your token in again.

Do you have more than one TRIGGERcmd account? This sort of thing can happen if you associated your computer with a different account from the one you're logged into the web gui as.

Another thing to check is your debug.log for clues.

batteryxsnare

I tried changing my command to a foreground command but that didn't show up either.

I tried deleting the user data folder but I've done that again, restarted the agent, and put the token in. I left the default sample commands there (notepad and calculator foreground and the reboot pc command background command). I see the computer listed in the web interface with the two foreground commands, but the background command doesn't show up. Is that expected?

If so, should I just use foreground commands?

Russ

@batteryxsnare, that is expected. You'll only get foreground commands until you install the background service. The background service installs and runs the background commands.

So apparently deleting the .TRIGGERcmdData folder fixed it.

batteryxsnare

Well, now I've installed the background service and started it, but the sample reboot command which is a background command still listed in the web interface...is that expected?

Russ

@batteryxsnare, do you mean it's still not listed? If not, can you confirm the Triggercmd agent service is running?

batteryxsnare

Yes, the background command is still not listed, and the background service was running.

I rebooted the PC and on reboot, the service didnt start on it's own but I manually started it and background command still isnt listed.

Russ

@batteryxsnare, ok, apparently there's something wrong with the background service if it's not staying started during boot. You could try "Remove Background Service" then "Install Background Service". If you have antivirus software, especially Avast, then I suggest temporarily disabling that while you do the remove/install. Sorry for all the trouble. If you tend to leave your computer logged in, you could just use foreground commands, but the background service should work. I use it on some of my Windows boxes, like my media center box because I don't keep myself logged in.

batteryxsnare

Only AV on the machine is Windows Defender...disabled real-time protection, uninstalled/re-installed background service but still not starting on reboot. Oh well, guess I'll just set the machine to auto-login and run foreground commands since they do seem to be working now.

Thanks for your help

Russ

@batteryxsnare, sorry man. I don't get it. I hate giving up, but I understand if you're done. The debug.log file might have a clue if you want to send me that.

batteryxsnare

here it is:

Checking if the 5c68c8523b309f00167a1439 computer exists.
This computer exists in your account.
Tokenfile: C:\Users\Jon Isaacson.TRIGGERcmdData\token.tkn
ComputerIDfile: C:\Users\Jon Isaacson.TRIGGERcmdData\computerid.cfg
Logging in with saved token to run foreground tasks.
Write backup completed.

|> Now connected to https://www.triggercmd.com.
___/ For help, see: http://bit.ly/2q0QDpf
(using sails.io.js node SDK @v1.2.1)
Connected at: Mon Feb 18 2019 07:13:20 GMT-0800 (Pacific Standard Time)

Initiated command removals
Initiated command adds
{ message: 'Subscribed to 5c68c8523b309f00167a1439!' }
{ message: 'Subscribed to 5c68c8523b309f00167a1439!' }

|> Now connected to https://www.triggercmd.com.
___/ For help, see: http://bit.ly/2q0QDpf
(using sails.io.js node SDK @v1.2.1)
Connected at: Mon Feb 18 2019 07:16:41 GMT-0800 (Pacific Standard Time)

{ message: 'Subscribed to 5c68c8523b309f00167a1439!' }
Opening GUI editor
Downloading example commands
Write backup completed.
Initiated command adds
Initiated command removals
Write backup completed.
Initiated command removals
Initiated command adds
Added TriggerCMD RifleSafe
{ trigger: 'TriggerCMD RifleSafe',
id: '5c6acd71592b050016ee4fa1' }
Running trigger: TriggerCMD RifleSafe Command: c:\ivbind\IvSendEvent -l 192.168.88.173 -n 100 10.69.1.111 -a Vibration
Reported: Command Ran
Write backup completed.
Initiated command adds
Initiated command removals
Deleted Notepad
Write backup completed.
Initiated command adds
Initiated command removals
Deleted Calculator
Write backup completed.
Initiated command removals
Initiated command adds
Added TriggerCMD PistolSafe

|> Now connected to https://www.triggercmd.com.
___/ For help, see: http://bit.ly/2q0QDpf
(using sails.io.js node SDK @v1.2.1)
Connected at: Mon Feb 18 2019 08:25:52 GMT-0800 (Pacific Standard Time)