starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 06:55:52 +03:00

[GH-ISSUE #1142] Integrate TRMM with Existing customized MeshCentral Server #702

New issue

Open

opened 2026-03-02 02:18:23 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 02:18:23 +03:00

Owner

Originally created by @Mfinadmin on GitHub (May 17, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1142

Hi Team,

This is regarding the discussion related to #1131.

We are running meshcentral using customized agent. This means the default Installation location and default service name ( Meshagent.exe) we have modified in our current setup. Since i am handling a big organization and there are approximate 9K+ agents are currently connected with existing meshcentral server. I tried to integrate TRMM with existing MC server. But it failed to detect my customized meshagent. So i am stuck with the integration. The current possibility is either we need to remove the agent customization and do fresh install on all PC's. But installing 9K agent is too difficult.

To overcome the above issue, either we need an option to define the customized Meshagent service name during Tactical RMM configuartion. can you please enable such facility in TRMM upcoming versions.

Originally created by @Mfinadmin on GitHub (May 17, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1142 Hi Team, This is regarding the discussion related to #1131. We are running meshcentral using customized agent. This means the default Installation location and default service name ( Meshagent.exe) we have modified in our current setup. Since i am handling a big organization and there are approximate 9K+ agents are currently connected with existing meshcentral server. I tried to integrate TRMM with existing MC server. But it failed to detect my customized meshagent. So i am stuck with the integration. The current possibility is either we need to remove the agent customization and do fresh install on all PC's. But installing 9K agent is too difficult. To overcome the above issue, either we need an option to define the customized Meshagent service name during Tactical RMM configuartion. can you please enable such facility in TRMM upcoming versions.

kerem added the

enhancement

label

2026-03-02 02:18:23 +03:00

kerem commented

2026-03-02 02:18:23 +03:00

Author

Owner

@dinger1986 commented on GitHub (May 17, 2022):

A flag/argument for the agent install would work for this as well

@dinger1986 commented on GitHub (May 17, 2022): A flag/argument for the agent install would work for this as well

kerem commented

2026-03-02 02:18:23 +03:00

Author

Owner

@JSuenram commented on GitHub (May 25, 2022):

@JSuenram commented on GitHub (May 25, 2022): +1

kerem commented

2026-03-02 02:18:24 +03:00

Author

Owner

@VINISHVV commented on GitHub (May 25, 2022):

+1
Awaiting for the same

@VINISHVV commented on GitHub (May 25, 2022): +1 Awaiting for the same

kerem commented

2026-03-02 02:18:24 +03:00

Author

Owner

@dinger1986 commented on GitHub (Sep 8, 2022):

I had a look at this there, its actually fairly complex as potentially need 3 variables for this to work, and they would need to be entered exactly the same as in mesh otherwise it wouldnt work eg:

        "agentCustomization": {
        "displayname": "CompanyName Support",
        "description": "CompanyName Remote Agent",
        "companyName": "CompanyName",
        "serviceName": "CompanyName Remote"
        }

So with the above example the path (instead of default C:\Program Files\Mesh Agent) would be C:\Program Files\CompanyName\CompanyName Support. The Service is then called CompanyName Remote.

@dinger1986 commented on GitHub (Sep 8, 2022): I had a look at this there, its actually fairly complex as potentially need 3 variables for this to work, and they would need to be entered exactly the same as in mesh otherwise it wouldnt work eg: ``` "agentCustomization": { "displayname": "CompanyName Support", "description": "CompanyName Remote Agent", "companyName": "CompanyName", "serviceName": "CompanyName Remote" } ``` So with the above example the path (instead of default C:\Program Files\Mesh Agent\) would be C:\Program Files\CompanyName\CompanyName Support\. The Service is then called CompanyName Remote.

kerem commented

2026-03-02 02:18:24 +03:00

Author

Owner

@forti42 commented on GitHub (Nov 17, 2022):

+1
Currently all of my clients have two agents: TRMM native and separate customized \company\CompanyAgent.exe. I need the customized MC to let local admins see what this folder is about...

For the time being, I´d be happy with an option per SITE: "Path to custom MCAgent.exe".

@forti42 commented on GitHub (Nov 17, 2022): +1 Currently all of my clients have two agents: TRMM native and separate customized \company\CompanyAgent.exe. I need the customized MC to let local admins see what this folder is about... For the time being, I´d be happy with an option per SITE: "Path to custom MCAgent.exe".

kerem referenced this issue

2026-03-14 03:43:24 +03:00

[GH-ISSUE #657] Dropdown for Variables in scripts #2364

kerem referenced this issue

2026-03-14 03:49:41 +03:00

[GH-ISSUE #702] Expose script parameters in Run dialogs #2391