Meshcentral: Agent Customization - Request and.. bug?

[yomono]

Hi!
I find amazing the Agent Customization options recently added. It's something that we was waiting for long time.
But I have this weird bug (or maybe it isn't).
My config file looks something like this:

"agentCustomization": {
                "displayName": "ExampleName",
                "description": "ExampleName Description",
                "companyName": "ExampleName",
                "serviceName": "ExampleName",
                "fileName": "ExampleName"
            }

Now, when I Install it, it duplicates the folder tree structure.
This means, the installed files are located at: "C:Program FilesExampleNameExampleName"
Did I do something wrong?

--

Finally, as a request, I think it would be great to add a few features:

• Change the file names (The folder is now "ExampleName", but the files inside are still being named "Meshagent.*"
• Have different customization according to languages (The most obvious right now is the "description". The service will have just one possible description, no matter what language I chose on the MeshCentral admin web).

[Ylianst]

Can you try this and see in what path the agent is installed? I think when you customize, it will install under "compagnyName/serviceName" but not sure.

"agentCustomization": {
  "displayName": "ExampleName1",
  "description": "ExampleName2 Description",
  "companyName": "ExampleName3",
  "serviceName": "ExampleName4",
  "fileName": "ExampleName5"
}

Bryan who works on the agent will have to take a look.

[krayon007]

Hi!
I find amazing the Agent Customization options recently added. It's something that we was waiting for long time.
But I have this weird bug (or maybe it isn't).
My config file looks something like this:

"agentCustomization": {
              "displayName": "ExampleName",
              "description": "ExampleName Description",
              "companyName": "ExampleName",
              "serviceName": "ExampleName",
              "fileName": "ExampleName"
          }

Now, when I Install it, it duplicates the folder tree structure.
This means, the installed files are located at: "C:Program FilesExampleNameExampleName"
Did I do something wrong?

The agent is installed into "%PROGRAMFILES%\companyName\serviceName\MeshAgent.exe"
I don't think "fileName" is associated to anything, I'll have to ask @ylian what field that sets... But there is already a "target" field that will change the file name of the agent, but it's not set by anything in the installer at the moment, so I can try to associate that to whatever field is set by "fileName"...

[yomono]

I just tried and, as you say, that's how it works:

So not a bug, just a misunderstanding from me

@krayon007 , about the "fileName" option, it is actually associated with something: Is the name of the installer. In this case, for example, it will be: "ExampleName564-Groupdevicename.exe"

[vitko-bg]

Agent customisation is amazing!
May the "fileName" be an actual filename.exe in Program Files?
So the result of installation to look like "%PROGRAMFILES%companyNameserviceNamefileName.exe" ?

[datapharmer]

Does adding agent customization to existing config perform cleanup on existing agents as they check in (remove old agent file paths, service, etc) after installing new agent path and service) or do we need to do a manual full install?

[Ylianst]

@vitko-bg I will talk to Bryan about this. Agreed, that would be nice to have the agent filename also be customized.
@datapharmer So no, once you put in customization, the new customized agent looks like different software and will only install/uninstall it's own serviceid. So, if you customize and run the agent on a machine that already has an agent, it will say it's not installed and will install itself along side the existing agent. So you will have two agents.