amidaware / rmmagent Goto Github PK

I am unable to install the new agent version on Windows 7. This was working in the previous release.

The error I am getting is Get "https://rmmapi.DOMAIN/api/v3/installer/": EOF

The setup.iss file references files that seem to be outside the repo. Should these be added to the repo?

The build instructions in the /README.md and /.github/workflows/ci.yml do not use the /build/setup.iss file as far as I can tell. This is likely why this was not apparent.

Need to test on more machines but it seems like at least on M1 ventura the trmm agent install task that install mesh times out before the installer has finished causing a failure in total installation

Any way to increase timeout?

When installing TRMM should request permission for full disk access for script running

After update agent to 2.0.1 in centos, wich have only 1hdd , shows multiple hdd entries.

Centos 7.9.2009 x86_64 3.10.0-1160.53.1.el7.x86_64 • Agent v2.0.1

When the "meshagent.exe" is removed by antivirus, the Mesh Agent service is also removed. Tactical's Recover Mesh feature does not re-add the service if it's missing. This would be a nice feature to have.

The alternative is to:

• Reinstall Mesh on the endpoint.
• Create the Mesh service manually.

Source:

I am having the same problem as in #5.

The error I am getting is Get "https://rmmapi.domain/api/v3/installer/": EOF.

Output of check_mesh:

Output installer:

Output chrome on agent:

Tried multiple times on multiple PC's using Generated powershell script

Here is some log output:

time="2023-06-08T13:34:23-05:00" level=info msg="Agent service started"
time="2023-06-08T13:34:34-05:00" level=error msg=EOF

hostname in TRMM GUI table shows : sarahs-imac.local

Some stuff from the mac CLI.

bash-3.2# hostname
sarahs-imac.local
bash-3.2# hostname -f
sarahs-imac.local
bash-3.2# hostname -s
sarahs-imac
bash-3.2#     

Hi,

after the Agent (v2.6.2) installation on 2 servers
1 x Windows Server 2019 RDS (Server61)
1 x Windows Server 2019 license service (Server15)

we sporadically get the license problem message in an RDS session (after 60 minutes the connection is disconnected)

the event log on the terminal server says the following:
Protocol name: Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager Date: 02/22/2024 16:55:56 Event ID: 50282 Task category: None Level: Warning Keywords: User: Network service Computer: Server61 Description: No Remote Desktop license server is specified for the Remote Desktop host server. Use the Remote Desktop Host Configuration Utility to specify a license server for the Remote Desktop host server. Event XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager" Guid="{c76baa63-ae81-421c-b425-340b4b24157f}" /> <EventID>50282</EventID> <Version>0</version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2024-02-22T15:55:56.026168900Z" /> <EventRecordID>507</EventRecordID> <Correlation /> <Execution ProcessID="1072" ThreadID="10860" /> <Channel>Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin</Channel> <Computer>Server61</Computer> <Security UserID="S-1-5-20" /> </System> <EventData> </EventData> </Event>

But everything is configured and worked fine until Agent installation.
After uninstallation the Agent from both Server, the message no longer appears. Perhaps something is being blocked?

I have the scenario where the installation of the agent is delegated to others (I document what to do; others execute the install on their servers). When something "doesn't work right", I've written a debug script the user can run to gather info (what is contents of config file, can it ping the mgmt console, etc... ) But it would be extremely helpful if the agent supported a CLI flag to do a health check. None of the "mode" options seemed right, as they didnt print results.

I could see a flag like "-testhealth" that would:

• Verify the agent can connect to the console API
• Verify through the console that it is registered, assigned to a client/site, and that it is "healthy"
• Output a Good/Bad result to CLI (extra bonus if it is script parsable and/or provides an exit code on success/failure)

Hi,
I'm testing the community beta Linux Agent for TRMM. I want to report that after a while Linux agent goes offline (status changed to offline), although the checks work fine. Also, it is possible to invoke remote commands, etc. so there is communication between agent and server. Could you verify on your side?

• Ubuntu 20.04 x86_64 5.4.0-104-generic • Agent v2.0.0

Temporary I'm running agent by invoking ./rmmagent -m svc

Best regards

Tactical V.0.12.4
Installation Docker

Thanks

On auto-update, the following is shown in the logs:

time="2022-11-05T19:35:07-04:00" level=info msg="Agent service started"
time="2022-11-05T20:35:00-04:00" level=info msg="Agent updating from 2.4.0 to 2.4.1"
time="2022-11-05T20:35:02-04:00" level=error msg="AgentUpdate() os.Rename(): rename /jKisjKRBDdfleEZalcAkgLMwlnuirFoTMFigmfsp /usr/local/bin/tacticalagent: invalid cross-device link"

cat /etc/os-release output:

NAME="Linux Mint"
VERSION="21 (Vanessa)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 21"
VERSION_ID="21"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=vanessa
UBUNTU_CODENAME=jammy

df -Th output:

Filesystem Type Size Used Avail Use% Mounted on
tmpfs tmpfs 3.2G 1.5M 3.2G 1% /run
rpool/ROOT/ubuntu_ppgh72 zfs 209G 9.5G 200G 5% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
rpool/USERDATA/oem_jq7qzg zfs 200G 128K 200G 1% /home/oem
rpool/ROOT/ubuntu_ppgh72/var/games zfs 200G 128K 200G 1% /var/games
rpool/ROOT/ubuntu_ppgh72/srv zfs 200G 128K 200G 1% /srv
rpool/ROOT/ubuntu_ppgh72/usr/local zfs 200G 5.7M 200G 1% /usr/local
rpool/ROOT/ubuntu_ppgh72/var/lib zfs 202G 2.4G 200G 2% /var/lib
rpool/USERDATA/root_jq7qzg zfs 200G 1.3M 200G 1% /root
rpool/ROOT/ubuntu_ppgh72/var/www zfs 200G 128K 200G 1% /var/www
rpool/ROOT/ubuntu_ppgh72/var/spool zfs 200G 128K 200G 1% /var/spool
rpool/ROOT/ubuntu_ppgh72/var/mail zfs 200G 128K 200G 1% /var/mail
rpool/ROOT/ubuntu_ppgh72/var/log zfs 200G 29M 200G 1% /var/log
rpool/ROOT/ubuntu_ppgh72/var/snap zfs 200G 128K 200G 1% /var/snap
rpool/ROOT/ubuntu_ppgh72/var/lib/AccountsService zfs 200G 128K 200G 1% /var/lib/AccountsService
rpool/ROOT/ubuntu_ppgh72/var/lib/apt zfs 200G 83M 200G 1% /var/lib/apt
rpool/ROOT/ubuntu_ppgh72/var/lib/NetworkManager zfs 200G 256K 200G 1% /var/lib/NetworkManager
rpool/ROOT/ubuntu_ppgh72/var/lib/dpkg zfs 200G 54M 200G 1% /var/lib/dpkg
bpool/BOOT/ubuntu_ppgh72 zfs 1.8G 500M 1.3G 28% /boot
/dev/sda1 vfat 511M 14M 498M 3% /boot/efi
tmpfs tmpfs 3.2G 7.6M 3.2G 1% /run/user/1000

Making a computer automatically less secure after installing the agent seems to me like a bad thing. Someone may install an agent and unknowingly not get updates leading to their computer being compromised.

This should be left up to the user to disable if they want to use the built in patch management system or build it into the patch management system.

I'm using Vs code to build the rmmagent using "go build" and it does create rmmagent.exe file in the same directory, but meanwhile if I download tacticalrmmagent.exe from releases of this repo, after execution it does create files in "ProgramFiles" but while building it locally it doesn't create any file in program files.

*Note: I'm new to development if there is any mistake please guide me.
*- I want to add some additional functionality to the agent, like it shouldn't delete mesh agent if tactical agent is deleted. any many more.

Please help me out.

The Linux Level-1 CIS benchmarks set the noexec flag on /tmp. This prevents the agent from being able to execute any scripts (fork/exec /tmp/trmm12345: permission denied)

The createTmpFile of utils.go is passing a blank string for the dir path to CreateTemp that is causing the function to use the path as returned by TempDir. https://pkg.go.dev/os#CreateTemp

If the value for this path was a variable (Custom Field) defined at the site or agent level that was an empty string by default, then it would continue to use the default TempDir path, but allow for overrides in circumstances where a different path is needed...

trmm-new-main-workstation-amd64.exe:

This version of \trmm-new-main-workstation-amd64.exe is not compatible with the version of Windows you're running . Check your computer's system information and then contact the software publisher.

Windows Version:

Version 1607 (OS Build 14393.6252)
© 2016 Microsoft Corporation. All rights reserved.
The Windows 10 Enterprise 2016 LTSB operating system

One server was offline and after researching the cause, I discovered there was an event log stating "A timeout was reached (30000 milliseconds) while waiting for the tacticalrmm service to connect.". It would be nice if the service (all OS's) was configured to stay running as best it can. For connectivity issues, retry logic is preferable over exiting after an initial failure to connect. If there's a domain configured, doing a fresh DNS lookup (can the agent clear the DNS cache?) and ping'ing the API until it's able to connect would be nice. If there's no domain configured, or if the agent configuration is corrupt, of course generate a friendly error message and exit.

Note: It's possible this could happen if the agent was restarted (computer rebooted) while the server was being updated and the API unavailable.

Log Name:      System
Source:        Service Control Manager
Date:          1/10/2023 5:22:50 PM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Win-Server04.****.****
Description:
A timeout was reached (30000 milliseconds) while waiting for the tacticalrmm service to connect.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7009</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2023-01-11T01:22:50.657621300Z" />
    <EventRecordID>136367</EventRecordID>
    <Correlation />
    <Execution ProcessID="552" ThreadID="2404" />
    <Channel>System</Channel>
    <Computer>Win-Server04.****.****</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">30000</Data>
    <Data Name="param2">tacticalrmm</Data>
    <Binary>74006100630074006900630061006C0072006D006D000000</Binary>
  </EventData>
</Event>

I think there is an upstream feature request for the go package on this. I researched it a few weeks ago and just brushed it off but last night I found WaveBrowser.

Maybe you can put pressure on them? I found WaveBrowser installed. I would have found it months or years ago if users were included.

EDIT. Is this it? iamacarpet/go-win64api#60

Hi,

I recently updated to 0.12.0 via the provided update.sh script and have discovered that any attempt to install the TacticalRMM agent on a new computer fails during the Mesh Agent installation.

Brief overview of my current setup:

• Server is running Ubuntu 20.04 and followed the standard install procedure in the documentation.
• Guest OS is Windows 10 1909 (multiple machines tested)
• TacticalRMM server is running v0.12.0 (recently upgraded from v0.11.3)
• A/V exclusions are in place per the documentation

The meshagent.exe file is downloaded on the affected system however it is a 1KB file. I've included the error message presented by the TacticalRMM installer (Switching between installation methods makes no difference). There only seems to be an issue with agent install, the rest of the functionality provided by TacticalRMM is fine for existing agents.

Downloading agent...
Extracting files...
Installation starting.
time="2022-03-23T13:36:49-04:00" level=info msg="Downloading mesh agent..."
time="2022-03-23T13:36:49-04:00" level=info msg="Installing mesh agent..."

fork/exec C:\Program Files\TacticalAgent\meshagent.exe: The file or directory is corrupted and unreadable.:
[ ]
time="2022-03-23T13:36:55-04:00" level=error msg="exec: "C:\\Program Files\\Mesh Agent\\MeshAgent.exe": file does not exist: "
time="2022-03-23T13:37:00-04:00" level=error msg="exec: "C:\\Program Files\\Mesh Agent\\MeshAgent.exe": file does not exist: "

What I've tried:

• Verified the SSL certificate is valid
• Ran the update.sh script with the --force option
• Rebooted the server

Any ideas you may have to correct this would be much appreciated!

Hi

Since this project is now converted to GO and a Linux agent is possible. Would it be possible to compile this for a Windows XP agent? A simple api connection with remote desktop capabilities would be already amazing. In my opinion, it would be nice to have 'a' solution for this, it does not need to include all the features.

I know this isn't easy but I think a lot of systems include older operating systems. A wider OS support would be a requirement for a lot of companies to switch over to Tactical RMM.

Thank you for your time.

I'm trying to install the linux agent, using the command line:
./rmmagent -m install -api=http://api.mylocaldomain.lokal -cert ./MY-CA-CERT.pem -client-id 1 -site-id 1 -auth XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX -nomesh
It fails, saying:
Get "https://api.mylocaldomain.lokal/api/v3/installer/": x509: certificate signed by unknown authority
even though I have provided the CA-cert.
Is this a bug or am I using it wrong?

https://github.com/amidaware/rmmagent/blob/db17e3e28ec0351597c02c7049255f90c85c9e7a/agent/utils.go#L342:L365

NixOS is a Linux distribution built on top of the Nix package manager. Its declarative configuration allows reliable system upgrades via several official channels. One of the features it has is the location where all the binaries are stored are a read-only filesystem.

I am able to successfully build and use the rmmagent on NixOS, except my scripts fail to run due to them trying to run in the same directory where the executable is located. Would the maintainers be open to a pull request adding a runtime feature flag allowing the tmp directory to be changed to a specific location (like --tmpdir /opt/trmm/scripts)? This would not change the default functionality, and could be easily specified in the systemd unit file that my nix package creates.

For example on a dell tactical reports: /77NDZ12/CN70163475007C/
dmidecode reports : 77NDZ12

On a vmware guest trmm reports: None
dmidecode : VMware-56 4d fa 72 69 7a 39 13-aa 0e 17 06 9b 09 42 c8

Also note, windows guests on vmware also report the serial number dmidecode reports.

The Windows Update API supports to search for driver updates:

https://learn.microsoft.com/en-us/windows/win32/api/wuapi/nf-wuapi-iupdatesearcher-search

Can you add this to the update search?
Maybe with a new category, "Drivers"?
Maybe this is helpful:
https://heinz-otto.blogspot.com/2018/10/powershell-und-windows-update.html

When do you think it might be possible to include FreeBSD 12 and 13 in the list of supported OS's. Golang is supposed to support FreeBSD but it seems the DEVs of container os-sysinfo is giving a fuss over adding support for it. I was really hoping this might be coming soon as would like to manage several open source firewalls with clients. If it needs payment to move it forward how much are you thinking?

The RMM agent crashes on startup sometimes. This can be found in the logs:

Agent version: v2.4.3

time="2023-01-18T14:48:32+01:00" level=info msg="Agent service started"
time="2023-01-18T14:18:21+01:00" level=info msg="Agent service started"
time="2023-01-20T16:19:30+01:00" level=info msg="Agent service started"
time="2023-02-01T08:46:15+01:00" level=info msg="Agent service started"
time="2023-02-01T08:52:24+01:00" level=info msg="Agent service started"
time="2023-02-01T10:05:43+01:00" level=info msg="Agent service started"
time="2023-02-01T10:06:27+01:00" level=error msg="error calling GetWUAUpdateCollection with query \"IsInstalled=1 or IsInstalled=0 and Type='Software' and IsHidden=0\": error calling method Search on IUpdateSearcher: Exception occurred. (<nil>)"

The agent doesn't clean up the temporary files in C:\Program Files\TacticalAgent\. I believe these are the updater downloaded on line 599. When the update fails, the temporary file is left behind.

These files were left behind in rmmagent v2.4.0 and I won't be able to test 2.4.1 until the next update is out.

• Version: 2.4.0

PS C:\Program Files\TacticalAgent> dir


    Directory: C:\Program Files\TacticalAgent


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----          7/8/2021  10:32 AM                py38-x64
-a----         11/6/2022   1:51 PM         355074 agent.log
-a----         11/4/2022   9:35 PM        3182653 is-0A2A9.tmp
-a----         11/4/2022   1:35 AM        3182653 is-0A8GN.tmp
-a----         9/25/2022  10:35 PM        3182653 is-0FQGR.tmp
-a----         11/5/2022   4:35 PM        3182653 is-131S5.tmp
-a----         11/1/2022   1:35 PM        3182653 is-1575G.tmp
-a----         11/3/2022   1:35 AM        3182653 is-1KDFE.tmp
-a----         11/5/2022   2:35 AM        3182653 is-1QVVB.tmp
-a----         9/26/2022   6:35 AM        3182653 is-1S4R4.tmp
-a----         11/4/2022  11:35 PM        3182653 is-2RQT5.tmp
-a----         9/25/2022  10:30 PM        3182653 is-3RD0V.tmp
-a----         11/2/2022   2:35 PM        3182653 is-3S56S.tmp
-a----         11/6/2022   1:35 AM        3182653 is-3S6QT.tmp
-a----         11/3/2022   5:35 PM        3182653 is-4OBS6.tmp
-a----         11/2/2022   3:35 PM        3182653 is-4UANV.tmp
-a----         11/4/2022   5:35 PM        3182653 is-52KCD.tmp
-a----         11/1/2022   6:35 PM        3182653 is-5376H.tmp
-a----         11/2/2022   8:35 PM        3182653 is-54IDR.tmp
-a----         11/1/2022   3:35 PM        3182653 is-57NSU.tmp
-a----         11/1/2022   5:35 PM        3182653 is-5CQS5.tmp
-a----         11/5/2022  10:35 PM        3182653 is-60BRT.tmp
-a----         11/3/2022  10:35 AM        3182653 is-6N6NQ.tmp
-a----         11/5/2022  11:35 AM        3182653 is-6OIRN.tmp
-a----         11/1/2022   8:35 AM        3182653 is-6P3B7.tmp
-a----         11/2/2022  11:35 AM        3182653 is-7E0HM.tmp
-a----         11/1/2022   7:35 AM        3182653 is-823BJ.tmp
-a----         11/3/2022  12:35 PM        3182653 is-85VGK.tmp
-a----         9/26/2022   2:35 AM        3182653 is-8QVEE.tmp
-a----         11/4/2022   3:35 PM        3182653 is-9149V.tmp
-a----         11/2/2022   7:35 PM        3182653 is-915UQ.tmp
-a----         11/1/2022  12:35 AM        3182653 is-923JH.tmp
-a----         11/1/2022  12:35 PM        3182653 is-94S90.tmp
-a----         11/2/2022   5:35 AM        3182653 is-9LMGJ.tmp
-a----         11/4/2022   3:35 AM        3182653 is-9URH2.tmp
-a----        10/31/2022  11:35 PM        3182653 is-A88R2.tmp
-a----         11/3/2022   9:35 AM        3182653 is-AHFT1.tmp
-a----         11/2/2022   3:35 AM        3182653 is-APRVN.tmp
-a----         11/2/2022   1:35 AM        3182653 is-AVI7J.tmp
-a----         11/5/2022   9:35 AM        3182653 is-BCLKB.tmp
-a----         11/2/2022   5:35 PM        3182653 is-BEBB8.tmp
-a----         11/1/2022   2:35 PM        3182653 is-BOK53.tmp
-a----         11/5/2022   1:35 PM        3182653 is-BQP3A.tmp
-a----         11/5/2022   6:35 AM        3182653 is-BTTDD.tmp
-a----         9/25/2022  11:35 PM        3182653 is-C765T.tmp
-a----         11/5/2022   7:35 PM        3182653 is-CFORB.tmp
-a----         11/6/2022  10:35 AM        3182653 is-CM8JA.tmp
-a----         11/5/2022   6:35 PM        3182653 is-CQC6J.tmp
-a----         11/5/2022   2:35 PM        3182653 is-D5U09.tmp
-a----         11/1/2022   8:35 PM        3182653 is-D7OA3.tmp
-a----         11/4/2022   5:35 AM        3182653 is-DAI3K.tmp
-a----         11/1/2022  11:35 AM        3182653 is-DJ0NE.tmp
-a----         9/26/2022   9:35 AM        3182653 is-DM6JS.tmp
-a----         11/6/2022   7:35 AM        3182653 is-DPHIB.tmp
-a----         11/2/2022   6:35 AM        3182653 is-E25DG.tmp
-a----         11/4/2022   6:35 PM        3182653 is-E45CV.tmp
-a----         11/6/2022   3:35 AM        3182653 is-E4B0R.tmp
-a----         11/2/2022   9:35 AM        3182653 is-E767M.tmp
-a----         11/1/2022   2:35 AM        3182653 is-E8TOR.tmp
-a----         11/4/2022   4:35 AM        3182653 is-E9G6K.tmp
-a----         11/5/2022   8:35 AM        3182653 is-EISD0.tmp
-a----         11/6/2022   6:35 AM        3182653 is-EJ0EQ.tmp
-a----         9/26/2022  10:30 AM        3182653 is-EJ2LF.tmp
-a----         11/4/2022   7:35 PM        3182653 is-ENTHO.tmp
-a----         11/4/2022   7:35 AM        3182653 is-F04BL.tmp
-a----         11/3/2022  10:35 PM        3182653 is-F1G8L.tmp
-a----         11/1/2022   1:35 AM        3182653 is-F3G04.tmp
-a----         11/2/2022   4:35 PM        3182653 is-F6S5P.tmp
-a----         11/4/2022   4:35 PM        3182653 is-FARUK.tmp
-a----         11/6/2022   5:35 AM        3182653 is-FLSHH.tmp
-a----         11/4/2022  10:35 AM        3182653 is-FPT4E.tmp
-a----         11/2/2022   7:35 AM        3182653 is-FUI8N.tmp
-a----         11/3/2022  11:35 AM        3182653 is-G6DG6.tmp
-a----         11/2/2022  10:35 AM        3182653 is-GB7EG.tmp
-a----         11/1/2022   4:35 PM        3182653 is-GFOO8.tmp
-a----         11/1/2022  10:35 PM        3182653 is-GIAJT.tmp
-a----         11/3/2022   7:35 PM        3182653 is-GUH33.tmp
-a----         11/6/2022   4:35 AM        3182653 is-H6Q56.tmp
-a----         11/4/2022   8:35 AM        3182653 is-H73I5.tmp
-a----         11/5/2022  10:35 AM        3182653 is-HANFH.tmp
-a----         11/6/2022  11:35 AM        3182653 is-HANIU.tmp
-a----         11/3/2022   5:35 AM        3182653 is-HBSIG.tmp
-a----         11/5/2022   3:35 AM        3182653 is-HEB3J.tmp
-a----         11/3/2022   6:35 AM        3182653 is-HEFLU.tmp
-a----         11/1/2022   6:35 AM        3182653 is-HOUNF.tmp
-a----         9/26/2022   1:35 AM        3182653 is-I5IDR.tmp
-a----         11/4/2022   8:35 PM        3182653 is-I78L4.tmp
-a----         11/2/2022   1:35 PM        3182653 is-IA8RQ.tmp
-a----         11/3/2022  12:35 AM        3182653 is-IJOG3.tmp
-a----         11/3/2022   8:35 PM        3182653 is-ILSQ2.tmp
-a----         11/2/2022   9:35 PM        3182653 is-J35A3.tmp
-a----         11/1/2022   3:35 AM        3182653 is-J6JDP.tmp
-a----         11/3/2022   3:35 AM        3182653 is-JI0E3.tmp
-a----         11/5/2022   3:35 PM        3182653 is-JL3B8.tmp
-a----         11/3/2022  11:35 PM        3182653 is-JTQ96.tmp
-a----         11/5/2022  12:35 AM        3182653 is-KCF49.tmp
-a----         9/26/2022   4:35 AM        3182653 is-KK916.tmp
-a----         11/3/2022   4:35 AM        3182653 is-KM46K.tmp
-a----         11/5/2022   1:35 AM        3182653 is-KTJ1S.tmp
-a----         9/26/2022  10:06 AM        3182653 is-KU13C.tmp
-a----         11/4/2022  10:35 PM        3182653 is-L6Q1I.tmp
-a----         11/6/2022   8:35 AM        3182653 is-LA8QB.tmp
-a----         11/5/2022   9:35 PM        3182653 is-LIGCI.tmp
-a----         11/5/2022   5:35 PM        3182653 is-M7N7S.tmp
-a----         11/3/2022   6:35 PM        3182653 is-MALV7.tmp
-a----         11/2/2022  11:35 PM        3182653 is-MFAN0.tmp
-a----         11/4/2022  12:35 AM        3182653 is-MGDAU.tmp
-a----         11/6/2022   1:35 AM        3182653 is-MJ1KE.tmp
-a----         9/26/2022   5:35 AM        3182653 is-MJIKE.tmp
-a----         11/4/2022  11:35 AM        3182653 is-MN0I3.tmp
-a----         11/3/2022   8:35 AM        3182653 is-MOV29.tmp
-a----         11/2/2022  10:35 PM        3182653 is-NB028.tmp
-a----         11/4/2022  12:35 PM        3182653 is-NCFTU.tmp
-a----         11/1/2022   5:35 AM        3182653 is-NEHNV.tmp
-a----         11/4/2022   6:35 AM        3182653 is-NJF43.tmp
-a----         9/26/2022  12:35 PM        3182653 is-NR0JV.tmp
-a----         11/2/2022  12:35 PM        3182653 is-O9H7L.tmp
-a----         9/26/2022  11:35 AM        3182653 is-OH545.tmp
-a----         11/2/2022  12:35 AM        3182653 is-OQO0Q.tmp
-a----         11/4/2022   1:35 PM        3182653 is-OSECP.tmp
-a----         11/3/2022   2:35 AM        3182653 is-P00LJ.tmp
-a----         9/26/2022  10:35 AM        3182653 is-P3IML.tmp
-a----         11/3/2022   1:35 PM        3182653 is-PGNSN.tmp
-a----         11/2/2022   2:35 AM        3182653 is-PQ5MV.tmp
-a----         11/2/2022   6:35 PM        3182653 is-PT2RU.tmp
-a----         11/1/2022  10:35 AM        3182653 is-QCC7H.tmp
-a----         11/4/2022   2:35 PM        3182653 is-QDR4T.tmp
-a----        10/31/2022  10:35 PM        3182653 is-QIHGM.tmp
-a----         11/6/2022   9:35 AM        3182653 is-QLB4L.tmp
-a----         11/5/2022   8:35 PM        3182653 is-QLGUI.tmp
-a----         11/6/2022   2:35 AM        3182653 is-QMD5S.tmp
-a----         9/26/2022   3:35 AM        3182653 is-QMOVP.tmp
-a----         11/1/2022  11:35 PM        3182653 is-QT19H.tmp
-a----         11/3/2022   7:35 AM        3182653 is-RDU7V.tmp
-a----         11/2/2022   4:35 AM        3182653 is-ROU03.tmp
-a----         11/3/2022   4:35 PM        3182653 is-RVMAU.tmp
-a----         11/5/2022  11:35 PM        3182653 is-S0RQ6.tmp
-a----         11/3/2022   9:35 PM        3182653 is-S53BV.tmp
-a----         11/3/2022   3:35 PM        3182653 is-TDDTV.tmp
-a----         11/4/2022   9:35 AM        3182653 is-TIULQ.tmp
-a----         11/4/2022   2:35 AM        3182653 is-TM75J.tmp
-a----         9/26/2022   8:35 AM        3182653 is-TPUQA.tmp
-a----         11/5/2022   4:35 AM        3182653 is-TVGNK.tmp
-a----         11/5/2022   7:35 AM        3182653 is-U14C0.tmp
-a----         11/1/2022   7:35 PM        3182653 is-U1F2T.tmp
-a----         9/26/2022  12:35 AM        3182653 is-UBBCE.tmp
-a----         11/1/2022   9:35 PM        3182653 is-UE9CK.tmp
-a----         11/5/2022   5:35 AM        3182653 is-UFPFG.tmp
-a----         9/26/2022   7:35 AM        3182653 is-UH0FO.tmp
-a----         11/6/2022  12:35 PM        3182653 is-UJP3H.tmp
-a----         11/6/2022  12:35 AM        3182653 is-UP82R.tmp
-a----         9/25/2022  10:45 PM        3182653 is-UTAV3.tmp
-a----         11/5/2022  12:35 PM        3182653 is-V5C64.tmp
-a----         11/6/2022   1:35 PM        3182653 is-V7OJ0.tmp
-a----         11/1/2022   9:35 AM        3182653 is-VBA6O.tmp
-a----        10/31/2022   9:58 PM        3182653 is-VFGV2.tmp
-a----         11/1/2022   4:35 AM        3182653 is-VGAEL.tmp
-a----         11/2/2022   8:35 AM        3182653 is-VHV2J.tmp
-a----         11/3/2022   2:35 PM        3182653 is-VMIQE.tmp
-a----          7/8/2021  10:31 AM        3034248 meshagent.exe
-a----         11/6/2022   1:48 PM            150 runasdebug.bat
-a----        10/25/2022   3:52 PM        8904520 tacticalrmm.exe
-a----         11/6/2022   1:51 PM            245 undodebug.bat
-a----         11/6/2022   1:49 PM          53896 unins000.dat
-a----         11/6/2022   1:48 PM        3182653 unins000.exe


PS C:\Program Files\TacticalAgent>

linux update uses os.rename which only works if src and dest are on same filesystem

Hi

On Windows 7 system i cannot install rmm agent. After click to automatically generated exe it show the "Downloading agent" and then quit whitout any error message.

Defender and any AV turned out.

Can you help with this?

Thanks"
BR.,
Z

For all of our Linux servers, they all show "Reboot Required". Running the command on the machine "needs-restarting" returns code 0, so machine does not require a reboot.

The source code looks for the file needs-restarting and returns true if the file exists. If the file does exist, the command should be called, and if the return code is not zero, then it requires reboot.

Add Event Viewer > Application logs for agent install/uninstall

Event ID: 11707

https://learn.microsoft.com/en-us/windows/win32/msi/event-logging

I see that some agents are not online but mesh agent is running on the agent. I think the TacticalRmm service crashes. And the timestamp of the last update corresponds to this log:

time="" level=info msg="Agent updating from 2.4.2 to 2.4.4"
time="" level=error msg="Get "https://github.com/amidaware/rmmagent/releases/download/v2.4.4/tacticalagent-v2.4.4-windows-amd64.exe\": dial tcp: lookup github.com: getaddrinfow: The requested name is valid, but no data of the requested type was found."

Since it has not internet connection, it can not do the update but it shouldn't crash the service.

I have this issue open on GitHub: amidaware/tacticalrmm#1228
A task to solve this has been created.

The fact that the agent does not auto-update without internet is not so bad but the fact that it may crash the service, is rather inconvenient.

Any ideas on what I can do?

[Creating this issue as recommended on Discord]