Installation
AMS.Eclipse is installed using a Setup executable that handles everything: the application itself, the Windows service, all required runtime prerequisites, firewall rules, and HTTP URL reservations. There is no need to install prerequisites separately.
Interactive Installation
- Download the latest
AMS.Eclipse.x.x.x.Setup.exefrom the AMS Portal - Run the installer as an administrator
- Follow the on-screen wizard
- When installation completes, the installer offers to open the AMS.Eclipse web interface at
http://localhost:58080/
The AMS.Eclipse Supervisor service starts automatically after installation and on every system boot.
Enterprise Deployment with Microsoft Intune
The Setup.exe can be deployed silently through Microsoft Intune as a Win32 app. The installer automatically handles all prerequisite installation — no separate prerequisite packages are needed.
Step 1: Prepare the Package
- Download the latest
AMS.Eclipse.x.x.x.Setup.exefrom the AMS Portal - Download the Microsoft Win32 Content Prep Tool
- Place the Setup.exe in its own folder (e.g.,
C:\IntunePackages\AMS.Eclipse\) - Run the content prep tool to create the
.intunewinpackage:
IntuneWinAppUtil.exe -c "C:\IntunePackages\AMS.Eclipse" -s "AMS.Eclipse.5.29.21.Setup.exe" -o "C:\IntunePackages\Output"
Replace the filename with the actual version you are deploying.
Step 2: Add as Win32 App in Intune
In the Microsoft Intune admin center:
- Navigate to Apps > All apps > Add
- Select Windows app (Win32) as the app type
App Information
| Field | Value |
|---|---|
| Name | AMS.Eclipse |
| Description | AMS Eclipse Supervisor Service |
| Publisher | AMS Controls |
Program
| Field | Value |
|---|---|
| Install command | AMS.Eclipse.5.29.21.Setup.exe /quiet /norestart |
| Uninstall command | msiexec /x {12345678-1234-1234-1234-123456789012} /quiet /norestart |
| Install behavior | System |
| Device restart behavior | Determine behavior based on return codes |
The uninstall command uses the MSI product UpgradeCode, which is stable across versions. This will correctly uninstall any version of AMS.Eclipse.
Return Codes
Use the default return codes:
| Return code | Code type |
|---|---|
| 0 | Success |
| 1707 | Success |
| 3010 | Soft reboot |
| 1641 | Hard reboot |
| 1618 | Retry |
Requirements
| Field | Value |
|---|---|
| Operating system architecture | 64-bit |
| Minimum operating system | Windows 10 1903 or later |
No additional RAM or disk space requirements beyond Intune defaults.
Detection Rules
Use a file-based detection rule:
| Field | Value |
|---|---|
| Rule type | File |
| Path | C:\Program Files\AMS Controls\AMS.Eclipse |
| File or folder | AMS.Eclipse.exe |
| Detection method | File or folder exists |
Assignments
Assign the app to the appropriate device groups for the machines where AMS.Eclipse should be installed.
Assign to device groups rather than user groups, since AMS.Eclipse runs as a system service regardless of which user is signed in.
Step 3: Verify Deployment
After Intune deploys the package:
- Confirm the AMS.Eclipse Windows service is running:
- Open Services (
services.msc) and look for "AMS Eclipse Supervisor" - Or run:
sc query AMS.Eclipse
- Open Services (
- Open a browser and navigate to
http://localhost:58080/ - The onboarding wizard should appear on first access
Upgrades
To deploy a newer version, repeat Steps 1 and 2 with the updated Setup.exe. The installer automatically:
- Upgrades all prerequisites to the versions required by the new release
- Stops the existing AMS.Eclipse service
- Upgrades the application files
- Restarts the service
There is no need to uninstall the previous version first.
What Gets Installed
Application Files
All files are installed to:
C:\Program Files\AMS Controls\AMS.Eclipse\
Windows Service
| Property | Value |
|---|---|
| Service name | AMS.Eclipse |
| Display name | AMS Eclipse Supervisor |
| Startup type | Automatic |
| Log on as | Local System |
| Description | AMS Eclipse Supervisor Service manages Eclipse Agent and Server workloads |
Prerequisites (installed automatically)
The Setup.exe installer automatically installs these if they are not already present:
- Microsoft .NET Runtime 9.x (x64)
- Microsoft ASP.NET Core Runtime 9.x (x64)
- Microsoft Visual C++ 2015-2022 Redistributable (x64)
Firewall Rules
The installer creates Windows Firewall rules for the following ports:
| Port | Protocol | Purpose |
|---|---|---|
| 58080 | TCP | AMS.Eclipse Supervisor web interface and API |
| 58085 | TCP | RavenDB database |
| 8080 | TCP | Eclipse Server API |
| 8081 | TCP | Eclipse Agent API |
These firewall rules are created automatically by the installer. If your organization manages firewall policy centrally (e.g., via Group Policy), ensure these ports are allowed for inbound TCP traffic on the target machines.
HTTP URL Reservations
The installer registers HTTP URL ACL reservations so the services can listen on their respective ports without requiring administrator privileges at runtime:
http://*:58080/http://*:58085/http://*:8080/http://*:8081/
Post-Installation
After installation, the AMS.Eclipse Supervisor service starts automatically. Open a browser and navigate to:
http://localhost:58080/
On first access, the onboarding wizard guides you through initial configuration. The supervisor automatically detects any existing Eclipse services already running on the machine.
Troubleshooting
Service is not running
Check the Windows Event Log for errors:
Get-EventLog -LogName Application -Source "AMS.Eclipse" -Newest 10
Also check the application logs at C:\ProgramData\AMS Controls\ for detailed error information.
Port conflicts
If another application is using one of the required ports, the service may fail to start. Check for port conflicts:
netstat -ano | findstr "58080 58085 8080 8081"
Verifying prerequisites
To confirm the required runtimes are installed:
# Check .NET runtimes
dotnet --list-runtimes
# Check VC++ Redistributable
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64" -ErrorAction SilentlyContinue | Select-Object Version