• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
TRIGGERcmd
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

don't run triggercmdagent service

General Discussion
5
20
1.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    Russ
    last edited by Feb 20, 2021, 12:25 AM

    @Wayne-Arthurton, I didn't realize 20H2 was an Insiders Windows 10 build. I'll try to get a copy of that soon and see if I can reproduce these problems.

    Russell VanderMey

    1 Reply Last reply Reply Quote 0
    • K
      kellanist
      last edited by kellanist Mar 1, 2021, 10:09 PM Mar 1, 2021, 3:04 PM

      Seems 20H2 broke shit.

      Now I can't even get commands to work by clicking on the play button in the UI. Reinstalled as well.

      The background service installer doesn't seem to make an entry for Node.js anymore from what I see in Programs and Features so it may not even be installing it anymore.

      @Russ

      R 1 Reply Last reply Mar 2, 2021, 1:08 PM Reply Quote 0
      • R
        Russ @kellanist
        last edited by Mar 2, 2021, 1:08 PM

        @kellanist and @Wayne-Arthurton, I'm finally downloading the dev build 21286 now. That's the newest build I could find. Hopefully that's the same as 20H2. I'm sorry about this - I should have prioritized this sooner. I'll work on reproducing the problem tonight.

        Russell VanderMey

        K 1 Reply Last reply Mar 2, 2021, 1:59 PM Reply Quote 0
        • K
          kellanist @Russ
          last edited by Mar 2, 2021, 1:59 PM

          @Russ If you need anyone to test or reproduce the issue, I'm happy to help. I can provide logs or anything else you need.

          Edition Windows 10 Enterprise
          Version 20H2
          Installed on ‎2020-‎10-‎04
          OS build 19042.844
          Experience Windows Feature Experience Pack 120.2212.551.0

          Do you also test on the newest builds of server 2016 and 2019? Currently working fine on 2019 - 1809 but now I'm terrified to update.

          1 Reply Last reply Reply Quote 0
          • X
            Xander @Russ
            last edited by Mar 2, 2021, 3:49 PM

            @Russ said in don't run triggercmdagent service:

            If you know of a way to download that, let me know.

            https://go.microsoft.com/fwlink/?LinkID=799445
            Direct download for the 20H2 installer. I've been using it on client's PCs to get them to upgrade.

            R 1 Reply Last reply Mar 3, 2021, 12:38 AM Reply Quote 0
            • R
              Russ @Xander
              last edited by Russ Mar 3, 2021, 12:38 AM Mar 3, 2021, 12:38 AM

              @Xander, I'll try your installer you linked above to update my PC. So far I've tried this version from the Windows Insider Program and it worked fine for me.

              0b136237-4e84-4c9c-9910-250ed0258b5c-image.png

              Russell VanderMey

              1 Reply Last reply Reply Quote 0
              • X
                Xander
                last edited by Mar 3, 2021, 2:29 AM

                I found the link on a tech forum and, with my remote support software, have sent it into a folder on their PCs and then run it in a silent install. So far, no problems on about 8 boxes, including one that wouldn't take the update via Windows Update.

                R 1 Reply Last reply Mar 3, 2021, 2:37 AM Reply Quote 0
                • R
                  Russ @Xander
                  last edited by Mar 3, 2021, 2:37 AM

                  @Xander, I upgraded my PC to 20H2. Unfortunately though the TRIGGERcmd agent is working fine, including the background agent.

                  cbcd4a0f-eb60-4259-a44a-81fb703d75b3-image.png

                  Have you seen a problem?

                  Russell VanderMey

                  1 Reply Last reply Reply Quote 0
                  • X
                    Xander
                    last edited by Xander Mar 3, 2021, 2:42 AM Mar 3, 2021, 2:41 AM

                    Nope. I got 20H2 a few months ago and not noticed any issues (but I'm a relatively light user compared to some, I think).

                    Just double-checked and the service is running and set to Automatic. I rebooted earlier today.

                    Your earlier stamp was 21286 -- was that a Preview build? 2004 (regular) was 19041.

                    R 1 Reply Last reply Mar 3, 2021, 11:43 PM Reply Quote 0
                    • R
                      Russ @Xander
                      last edited by Mar 3, 2021, 11:43 PM

                      @Xander, that 21286 build is the current Dev build from the Windows Insider Program.

                      Russell VanderMey

                      1 Reply Last reply Reply Quote 0
                      • K
                        kellanist
                        last edited by Mar 5, 2021, 3:02 PM

                        @Russ

                        Reinstalled as admin. Service is confirmed running. I clicked the option to install the background agent but I don't see node.js in the installed app list like I see it on all my other machines.

                        After seeing this in Event Viewer -> Application should there be an additional entry stating that it started successfully?

                        Starting C:\Users\kadamson\AppData\Local\TRIGGERcmdAgent\app-1.0.25\resources\app\src\service.js

                        This is what I'm seeing when I try to run a command in the GUI from the developer tools:

                        C:\triggercmdDev\github\TRIGGERcmd-Agent\process\js\fake_d10b99db.js:197 Running c:\scripts\StartWork.bat
                        C:\triggercmdDev\github\TRIGGERcmd-Agent\process\js\fake_d10b99db.js:62 Neither add nor edit box visible, so updating file
                        15C:\triggercmdDev\github\TRIGGERcmd-Agent\process\js\fake_d10b99db.js:197 Running c:\scripts\StartWork.bat

                        Failed to parse SourceMap: file:///C:/Users/kadamson/AppData/Local/TRIGGERcmdAgent/app-1.0.25/resources/app/app/css/bootstrap.css.map * this one only shows up once.

                        Still not running the command. Not sure what could be happening. Is there anything that I can grab for you?

                        R 1 Reply Last reply Mar 6, 2021, 1:05 AM Reply Quote 0
                        • R
                          Russ @kellanist
                          last edited by Russ Mar 6, 2021, 1:12 AM Mar 6, 2021, 1:05 AM

                          @kellanist, did you install the agent as admin the first time? To make sure I'm clear, I don't mean while logged on as a member of the local admins group. Did you right-click the installer and click "Run as administrator"? I'll try that myself, but I worry that might actually cause a problem - maybe the problem you're seeing. I'll give it a try and post again.

                          EDIT: @kellanist found it worked after a reboot.

                          Russell VanderMey

                          J K 2 Replies Last reply Mar 8, 2021, 1:32 AM Reply Quote 0
                          • J
                            JIMMY GUTIERREZ NINAHUAMAN @Russ
                            last edited by Mar 8, 2021, 1:32 AM

                            @Russ the service still don't run bro! is not there solution?

                            R 1 Reply Last reply Mar 9, 2021, 12:05 AM Reply Quote 0
                            • K
                              kellanist @Russ
                              last edited by Mar 8, 2021, 5:47 PM

                              @Russ Installer worked to reinstall the agent but the agent still fails to run the commands. I believe I ran the installer by right-clicking -> Run as Admin. I usually do that when installing any program as a CYA anyways.

                              The post above was on what I am seeing in the developer console in the GUI when I attempt to run my StartWork,bat script. All the script does is opens Outlook and Teams. Doesn't matter if I run it from the GUI, through Alexa, or from the website, it does not run on the local machine.

                              The other post was me hitting the same thing as the other user when trying to troubleshoot the commands not working issue.

                              This all started happening after updating Win10 to 20H2.

                              R 1 Reply Last reply Mar 8, 2021, 11:59 PM Reply Quote 0
                              • R
                                Russ @kellanist
                                last edited by Russ Mar 9, 2021, 12:00 AM Mar 8, 2021, 11:59 PM

                                @kellanist, running the installer "As administrator" doesn't seem to be a problem. I just tried it myself and it worked fine. The agent runs commands via the foreground agent and the background service.

                                You said your StartWork.bat doesn't even work from the GUI. That narrows it down. Does Calculator or Notepad run via the GUI? If so, then please paste your StartWork.bat script here.

                                Russell VanderMey

                                K 1 Reply Last reply Mar 11, 2021, 5:23 PM Reply Quote 0
                                • R
                                  Russ @JIMMY GUTIERREZ NINAHUAMAN
                                  last edited by Russ Mar 9, 2021, 12:20 AM Mar 9, 2021, 12:05 AM

                                  @JIMMY-GUTIERREZ-NINAHUAMAN, I'm sorry it's difficult to troubleshoot this problem because I haven't seen it myself yet. My background service stays started on all of my computers, and on the new Windows 10 VM's I created with the latest dev build and the 20H2 version.

                                  I'm curious. Why do you want to use the background service? Do you want to run commands while you're logged off?

                                  Russell VanderMey

                                  1 Reply Last reply Reply Quote 0
                                  • K
                                    kellanist @Russ
                                    last edited by Mar 11, 2021, 5:23 PM

                                    @Russ

                                    So it looks like it is kinda working. The issue now is that when I run the batch file manually as an admin, it works fine. If I run it using a foreground command, it only runs the first command and then sits there. Not sure why it wont progress to open all the programs. Is it running the commands as an admin?

                                    "C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE"
                                    start %localappdata%\Microsoft\Teams\Update.exe --processStart "Teams.exe"
                                    "C:\Users\kadamson\AppData\Local\GoToMeeting\19228\g2mstart.exe"
                                    "C:\Program Files (x86)\Auto Mouse Mover\AutoMouseMover.exe" :silent

                                    That is the entire script. Stored in my local user documents folder.

                                    R 1 Reply Last reply Mar 12, 2021, 12:09 AM Reply Quote 0
                                    • R
                                      Russ @kellanist
                                      last edited by Mar 12, 2021, 12:09 AM

                                      @kellanist, does that script only work if you right-click and run it as administrator? If so, you could try running the TRIGGERcmd agent as administrator.

                                      By default, the TRIGGERcmd agent will not run your commands as admin, but if you run the agent as admin, then the commands it runs would run with the elevated tokens too.

                                      You could also turn off UAC, but of course that has security implications.

                                      Russell VanderMey

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post