---
title: "Upgrading from our Legacy Agents to Argon and Newer"
canonical: "https://docs.perspectium.com/space/earlierReleases/1442040/Upgrading%20from%20our%20Legacy%20Agents%20to%20Argon%20and%20Newer"
format: markdown
---
Security Changes Enhanced integration with various security options provided by our supported   OS   platforms may result in the user receiving additional prompts for Administrator or SUDO permission. Users   must   to perform the install steps “as an Administrator” (Windows) or with   sudo   on *nix platforms. Running the Agent Interactively For linux systems you may have been familiar with just executing: bin/agent start the Agent would start up and that was it. It is now named   agent.sh   and this is   no longer the recommended way   to run the Agent. This (along with windows) has been changed so running the Agent like so will run it “interactively” in the console. This is largely for quick demonstrations / tests. For extended use the recommended approach is to install it as a Windows Service or Linux Daemon. When running the agent interactively (through the agent.sh/agent.bat convenience scripts or runConsole.sh/runConsole.bat commands), users are advised to always terminate the Agent as documented below with control-c. This allows the interactive agent session to exit gracefully. Failure to do so may result in a lingering Java process which must be killed or terminated manually. Upgrading The steps to upgrade are: If any custom third party jars were previously used, take note of them and create a backup. These would be found in the “extlib” folder of the Agent. Following the installation of the Agent you can copy them back into the “extlib” folder Uninstall the legacy Agent by running the uninstaller, if you have installed it as a service it is recommended to uninstall the service first See here for Windows See here for Linux Install the new Agent package per the main instructions Windows Installation Linux Installation This is essentially verifying we are removing the legacy Agent's service prior to the fresh installation of the newer Agent. Installation as a Service As mentioned previously we want the Agent to run all the time, ie, as a service. This is detailed in the previous installation links. The following are direct links for how to do this: Windows Service Installation Linux Daemon Installation Service Changes If you are familiar with installing the Agent as a service this process should be familiar to you. The changes made between these two versions are primarily which files are executed: Windows Operation Legacy Version Argon and above Install Agent Service InstallAgent.bat installService.bat Remove Agent Service UninstallAgent.bat uninstallService.bat Starting Agent Service StartAgent.bat startService.bat Stopping Agent Service StopAgent.bat stopService.bat You   need to “Run as Administrator”   for the   installService.bat   as well as   uninstallService.bat   for the Replicator Agent to properly function as a service. You are still able to operate the Agent through the Windows service panel as you were previously (without administrator privileges). Linux Operation Legacy Version Argon and above Install Agent Service bin/agent install bin/installDaemon.sh Remove Agent Service bin/agent remove bin/uninstallDaemon.sh Starting Agent Service service ReplicatorAgent start bin/startDaemon.sh Stopping Agent Service service ReplicatorAgent stop bin/stopDaemon.sh