Deploy the FSO Agent on a Windows or Linux server, verify that it’s reporting to Applications Manager, and resolve any installation errors.

| Requirement | Windows | Linux |
|---|---|---|
| Applications Manager build | v175500 or later | v175500 or later |
| Supported OS versions | See FSO Agent system requirements | See FSO Agent system requirements |
| Run the install command as | PowerShell opened as Administrator | Root, or a user with sudo (sudo must be installed) |
| Tools needed | PowerShell script execution allowed | wget (required), curl (for live status on the FSO Agent page) |
| Network access | HTTPS to Applications Manager (default port 10099) | HTTPS to Applications Manager (default port 10099) |
10099, update Host or Port under Agent Bundle & Capabilities → Applications Manager address and save.The install command runs in five steps. The first line, FSO agent registration - https://<host>:<port>, shows the address it connects to. Select a step to go to its fix.
On Linux, when you reinstall, the existing agent is removed between Step 3 and Step 4 (Uninstalling existing FSO agent).
When a step fails, it shows FAILED and an ERROR: message. A failed run always ends with a support line that includes the log file path, if a log was kept (see Collect diagnostic logs).
When all five steps show OK, you’ll see The FSO Agent is installed. It appears in View Agents once it registers with Applications Manager. Open View Agents in Applications Manager to check that the agent is listed.


ERROR: message or any unexpected output in the terminal? Look it up in Quick error lookup.| Stage | What you see | Go to |
|---|---|---|
| Before Step 1 | running scripts is disabled on this system (Windows) | PowerShell blocks the script (Windows) |
| Before Step 1 | A license key is required… | License key not provided |
| Step 1 | [1/5] … FAILED | Step 1 of 5 · Privilege check failed |
| Step 2 | [2/5] … ALREADY INSTALLED | Step 2 of 5 · Agent already installed |
| Step 3 | [3/5] … FAILED | Step 3 of 5 · Connectivity check failed |
| After Step 3 (Linux reinstall) | Uninstalling existing FSO agent … FAILED (Linux) | Reinstall blocked: existing agent not removed (Linux) |
| Step 4 | [4/5] … FAILED | Step 4 of 5 · Installer download failed |
| Step 5 | [5/5] … FAILED | Step 5 of 5 · Installation failed |
| After Step 5 (Windows) | Restart this machine to complete the setup (Windows) | Not an error. See Step 5 of 5 · Installation failed (Windows) |
| Any step | WARNING: Could not send '<stage>' status… | Status update warning (no action needed) |
| Any step | The install command stops at a step and shows no result | Check the connection items in Step 3 of 5 · Connectivity check failed, then the download items in Step 4 of 5 · Installer download failed |
Each section matches a message from the install command, in the order the install command runs. When a message says See <log>, open fso_agent_register.log. Its full path is shown in the install script’s output (see Collect diagnostic logs).
Error: … cannot be loaded because running scripts is disabled on this system.
Cause: The PowerShell execution policy blocks scripts.
Fix:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

-Scope Process applies only to the current PowerShell window, and the setting is discarded when you close it.
Prompt: Enter the Applications Manager license key
Error: A license key is required. Copy the install command again from Applications Manager.
Cause: The command was run without its key. This usually means it was copied only partly, or the script file was run on its own.
Fix: Copy the complete install command from the FSO Agent page and run it again. Don’t run register.sh or register.ps1 by themselves.
Error: Run this script from an elevated PowerShell (Run as Administrator).
Fix: Open PowerShell with Run as Administrator and run the install command as described in Deploy the FSO Agent.
Error: No sudo access. Run 'sudo -v' to authenticate, then re-run this script.
Cause: The script checks sudo without prompting for a password, so the check fails if your sudo session has expired.
Fix: Run sudo -v, enter your password, then run the install command right away.

sudo -v && <install command>Error: sudo is required but not installed on this machine.
Cause: sudo is not installed. The install command needs it even when you’re logged in as root.
Fix: Install sudo (yum install sudo or apt-get install sudo), then run the install command again.
Message: [2/5] Checking for an existing agent ... ALREADY INSTALLED, followed by The FSO Agent is already installed on this server. No changes were made.
If the existing agent is working, no action is needed. To reinstall:
At the prompt Uninstall the existing FSO agent and reinstall? [y/N]:, answer y. The script removes the old agent only after the connection check in Step 3 passes.

Got “No changes were made” without answering? Pressing Enter counts as No, and so does running the install command without an interactive terminal (for example, from an automation tool). Run it from a terminal and answer y, or uninstall first:
sudo /opt/applicationsmanager/monagent/bin/uninstall
Error: Cannot reach Applications Manager at <host>:<port>. Check the host name and port, and make sure a firewall is not blocking the connection.
Cause: One of these:
Fix:
1. Test the connection from the target server:
Test-NetConnection <host> -Port <port>
The port is reachable if the output shows TcpTestSucceeded : True.
timeout 5 bash -c "</dev/tcp/<host>/<port>" && echo open || echo closed
The port is reachable if the output is open.
2. Fix what the test shows:
This appears only when you answered y in Step 2.
Error:
Uninstall failed. See <log>Uninstall did not remove the existing FSO agent. See <log>Fix:
fso_agent_register.log and check the Uninstall: section.sudo /opt/applicationsmanager/monagent/bin/uninstall
/opt/applicationsmanager/monagent/bin/uninstall no longer exists, then run the install command again.Error: Download failed from <url>: <reason>
| Reason contains | What to do |
|---|---|
(404) Not Found | Upload the latest FSO Agent bundle under Agent Bundle & Capabilities and retry. |
Unable to connect, connection was closed, SSL/TLS secure channel | Allow HTTPS downloads from Applications Manager (check the proxy and firewall), and make sure TLS 1.2 is enabled. |
Error: Installer not found at <path> after download.
Fix: Make sure the current folder is writable and that antivirus isn’t removing the downloaded .msi file.
Check the installer URL manually: from the target server, open https://<host>:<port>/resources/FSO/latest/server/windows/installer/ApplicationsManager_Windows_Installer.msi in a browser or with Invoke-WebRequest. If it doesn’t download, the problem is the network path or the uploaded bundle, not the install command.
Error: Download failed (wget exit code <n>). See <log> (find the log)
| wget exit code | Meaning | What to do |
|---|---|---|
| 127 | wget is not installed | Install it (yum install wget or apt-get install wget) and retry. |
| 4 | Network failure | Check proxy and firewall rules for HTTPS between the two servers, and make sure TLS 1.2 is enabled. |
| 8 | Applications Manager returned an error, usually 404 Not Found | Upload the latest FSO Agent bundle under Agent Bundle & Capabilities and retry. |
For any other code, check the Download: section of the log.
Error: Downloaded installer is empty: <url>
Fix: The installer file on Applications Manager is empty or incomplete. Upload the FSO Agent bundle again and retry.
Check the installer URL manually: from the target server, open https://<host>:<port>/resources/FSO/latest/server/linux/installer/ApplicationsManagerFullStackAgent_LinuxIns.sh in a browser or with wget. If it doesn’t download, the problem is the network path or the uploaded bundle, not the install command.
Error: Installation failed (msiexec exit code <n>). See <log> (find the log)
| Exit code | Meaning | What to do |
|---|---|---|
| 1603 | General install error | In the log, search for Return value 3 and read the lines just above it. The cause is often permissions or antivirus. |
| 1618 | Another installation is in progress | Wait for it to finish, or restart the server, then retry. |
| 1625 | Blocked by system policy | Contact your system administrator. |

Restart this machine to complete the setup. Restart the server when convenient.Error: Installation failed (installer exit code <n>). See <log> (find the log)
Fix: Check the Install: section of the log for the reason.
Error: Installer finished, but no FSO agent was found at /opt/applicationsmanager/monagent/bin/monagent. See <log> (find the log)
Cause: The installer can finish without reporting an error even when nothing was installed. Check the Install: section of the log. Common causes:
uname -m; the output must be x86_64.Message: WARNING: Could not send '<stage>' status to AppManager (…)

(server unreachable) can also mean curl isn’t installed.Still failing? Collect diagnostic logs and contact support.
fso_agent_register.log is kept when installation fails and deleted when it succeeds. Its full path is shown in the install script’s output (register.ps1 on Windows, register.sh on Linux), in the support line at the end of a failed run.
register.ps1 output.Download:, Uninstall: and Install:.register.sh output.Email appmanager-support@manageengine.com or submit a ticket with:
fso_agent_register.log, if it exists, from the path shown in the install script’s outputStart-Transcript -Path C:\Temp\fso_install_console.txt. When it finishes, run Stop-Transcript and attach the file.