Page 1 of 1

Replacement Package MeshCentral

Published: April 11, 2025 - 12:07 PM
by Emmanuel64
Hello,
Previously, using the WAPT Discovery version, I deployed a Mesh Central server in parallel to manage my machines. I manually created a package to deploy the agent to the workstations.
So far, so good...
I'm now upgrading to the Enterprise version, and I'd like to be able to access the machines directly through the WAPT interface. I've therefore downloaded the meshagent-template package, which is much more complete than my basic one (and had an incorrect version increment in the registry as a bonus).
Is there a way to replace my old package with the new one (the agent's .exe file is the same), perhaps using a command in the setup?

Thank you in advance for your help,

Emmanuel

Re: MeshCentral Package Replacement

Published: May 20, 2025 - 09:44
by blemoigne
Good morning,
Sorry for the late reply. Were you able to resolve the issue or are you still looking for a solution?
The meshagent-template package is used by first running the update_package() function (from the WAPT console, right-click on the package > run update_package). If the package currently installed on the machines has a different name, it should be omitted: add the following line to the beginning of the install() function of the new package:

Code: Select all

WAPT.forget_packages('prefix-oldpackagename')