Integrate TRMM with Existing customized MeshCentral Server

[Mfinadmin]

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.

[dinger1986]

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

[JSuenram]

+1

[VINISHVV]

+1 Awaiting for the same

[dinger1986]

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.

[forti42]

+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".